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] 3d downtime reported - why?
- Previous message (by thread): [atlas] 3d downtime reported - why?
- Next message (by thread): [atlas] 3d downtime reported - why?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Nov 2 10:33:25 CET 2011
On 11/2/11 9:15 , Michael Procter wrote: > If the probe sent a connection count since boot when making a > connection, then I would be able to see which disconnects I can ignore > and which need investigation. Michael With the current firmware, probes report their uptime on a regular basis. However that information is currently not processed by the back-end system. Probes also continue doing measurements if there is no network connectivity. However that doesn't show up in the graphs. It should however show up in the logs. If you see missing packets in the log files then there was probably some kind of network problem otherwise, it is probably a probe problem. Philip Homburg
- Previous message (by thread): [atlas] 3d downtime reported - why?
- Next message (by thread): [atlas] 3d downtime reported - why?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]