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]Inaccurate uptime tracking?
- Previous message (by thread): [atlas]Inaccurate uptime tracking?
- Next message (by thread): [atlas]DNS records for the probes' internet address
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard L. Barnes
rbarnes at bbn.com
Thu Dec 2 14:45:00 CET 2010
I see, looks good now. Thanks! --Richard On Dec 2, 2010, at 3:45 AM, Andreas Strikos wrote: > Hi Richard, > > The reason you saw this inconsistency is because the history stats are updated every 3 hours or so. > So if you see your history table now there is one more line there that makes the total uptime consistent. > Anyhow, if you see anything else that seems inconsistent just let us know. > > /Andreas > > On Dec 2, 2010, at 4:36 AM, Richard L. Barnes wrote: > >> Hey guys, >> >> I'm seeing an inconsistency between the reported uptime and the actual measurements from probe #394. On the one hand, the probe info page reports only a little over an hour of uptime: >> >> Total Uptime: 0d, 1h, 1m >> Connect at: Disconnect at: >> 2010-12-02 02:38:06 UTC (still connected) >> 2010-12-01 04:22:43 UTC 2010-12-01 04:28:42 UTC >> >> But the graphs for the last 8 hours show only a brief down-time; roughly: >> Disconnect: 2010-12-02 02:27:00 UTC >> Reconnect: 2010-12-02 02:35:00 UTC >> >> This wouldn't bother me much if uptime weren't tied to chances to win an iPad :) >> >> --Richard >> >
- Previous message (by thread): [atlas]Inaccurate uptime tracking?
- Next message (by thread): [atlas]DNS records for the probes' internet address
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]