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] Probe #1000165 showed as down in tab#status
- Previous message (by thread): [atlas] Probe #1000165 showed as down in tab#status
- Next message (by thread): [atlas] Probe #1000165 showed as down in tab#status
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Tue Mar 2 12:46:05 CET 2021
Hi Jacques, Thank you for reporting! There was a network maintenance in Hetzner last night. Few days before the ctr-fsn01 was reinstalled. Due to minor network misconfiguration the controller's IPv6 connectivity was not restored. Now the problem is solved. Best regards /vty On 3/2/21 11:17 AM, Jacques Lavignotte wrote: > Dear RIPE NCC crew, > > Some diag below : > > # systemctl status atlas > > mars 02 11:12:43 melusine.eu.org ATLAS[32011]: Do a controller INIT > mars 02 11:12:43 melusine.eu.org ATLAS[32011]: Controller init -p 443 > atlas at ctr-fsn01.atlas.ripe.net INIT > mars 02 11:12:43 melusine.eu.org ATLAS[32011]: 255 controller INIT > exit with error > > Probe seems down since scheduled machine reboot this night. > > Help for fixing welcome, > > Merci, Jacques >
- Previous message (by thread): [atlas] Probe #1000165 showed as down in tab#status
- Next message (by thread): [atlas] Probe #1000165 showed as down in tab#status
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]