This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] meaning of error message in Ping measurements
- Previous message (by thread): [atlas] meaning of error message in Ping measurements
- Next message (by thread): [atlas] New on RIPE Labs: Using RIPE Atlas to Monitor Game Service Connectivity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wenqin SHAO
wenqin.shao at telecom-paristech.fr
Tue Sep 13 14:31:14 CEST 2016
Hi Philip, Thanks a lot for the explanation. In deed, these error messages rarely appears. My current script just logged their presence and thus is not able to tell which probe is responsible for them at what moment. If the case is of interest to you, I can look into it later. Again, many thanks. Regards, wenqin > On 13 Sep 2016, at 10:48, Philip Homburg <philip.homburg at ripe.net> wrote: > > Hi, > >> Could someone please help me figure out what these error messages in result field of ping measurement mean? >> - error: sendto failed: Invalid argument (related to name resolve?) >> - error: sendto failed: Bad file descriptor > > These are errors returned by the sendto system call on the probe. > > The sendto(2) manual page on Linux gives a description of when sendto > returns those errors. > > By and large I would say that these errors are not supposed to happen. > So this is probably a bug in the probe code. > > Philip >
- Previous message (by thread): [atlas] meaning of error message in Ping measurements
- Next message (by thread): [atlas] New on RIPE Labs: Using RIPE Atlas to Monitor Game Service Connectivity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]