[atlas-sw-probes] New release v5020
- Previous message (by thread): [atlas-sw-probes] New release v5020
- Next message (by thread): [atlas-sw-probes] New release v5020
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
hvjunk
hvjunk at gmail.com
Mon May 4 00:19:09 CEST 2020
> On 01 May 2020, at 14:12 , Philip Homburg <philip.homburg at ripe.net> wrote: > > > We made a change to have software probes send the hash of the probe's > public key instead. With this change the network tab of the probe page > shows the 'SOS History'. Interesting “side effect” when using LXC containers that get their |uptime” from the running host: Resolver Time (UTC) Query Type Power-up Time Info 216.66.87.134 2020-05-03 21:59:43 AAAA 25d 0h 10m 216.66.87.134 2020-05-03 21:29:45 AAAA 0h 4m Between those I transferred (backup & restored) the container to a different host. Thus the first SOS at 21:29:45 was on the old host, that I just booted up, while the 21:59:43 was the new destination host that had been up for ~25 days :) Perhaps you could consider to include a “daemon start up timestamp” together with a “host” uptime, as it might give indications or restarted daemons too? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: </ripe/mail/archives/atlas-sw-probes/attachments/20200504/c48369d9/attachment.sig>
- Previous message (by thread): [atlas-sw-probes] New release v5020
- Next message (by thread): [atlas-sw-probes] New release v5020
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]