Re: [atlas-sw-probes] SW Probe offline after reinstall & SSH KEY change
Hi team, it seems it still does not work correctly. I had to change my probe 1000078 hosting server. The situation with SSH KEY is the same as described below. Furthermore on https://atlas.ripe.net/probes/1000078/#!tab-network I can see its new IP addresses, what is weird, since it still shows Offline, but the new IPv4 and IPv6 are there. Cheers Jiri _________________________________________________________________________________ Johan ter Beest jterbeest at ripe.net Fri Jan 17 19:36:53 CET 2020 Hi Jiri,
On 17 Jan 2020, at 14:51, <ripe at brite.cz> <ripe at brite.cz> wrote:
Hi team, I have SW probe 1000069 running on router Turris Omnia. I had to commit factory reset and reinstall all software. All went good, I have the SW Probe running, got new SSH KEY [command "/etc/init.d/atlas get_key"] and pasted the new key to web > Update SSH Key. First it accepted, but the probe never managed to connect. I restarted the probe process and even whole router, also tried to get the key from the probe again and when pasting to Update SSH Key field it says "A probe with this key already exists. Please enter a unique key". So the new key is sure recorded correctly.
For some reason the new key was not copied to the probe. I have now done this manually so it should be able to connect now
Probe log: root at turris:~# /etc/init.d/atlas log 01/17/20 12:36:02 ctrl-init 01/17/20 13:39:02 net-try 01/17/20 13:39:05 net-ok 01/17/20 12:39:05 ctrl-init 01/17/20 13:42:06 net-try 01/17/20 13:42:09 net-ok 01/17/20 12:42:09 ctrl-init 01/17/20 13:45:09 net-try 01/17/20 13:45:12 net-ok 01/17/20 12:45:12 ctrl-init
From https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html I read "We'll add a means to replace this key for an existing probe, in case you need to reinstall and lose the original key material." Does it mean it is not implemented yet?
It should be implemented… I will check on Monday why it failed to copy the new key to the probe. Cheers and have a good weekend :) Johan
Thank you
Jiri
Some logs, if it helps: /var/atlas-probe/status/reg_init_reply.txt: OK REGSERVER_TIMESTAMP 1579623247 2020.01.21-16:14:07 CONTROLLER ctr-fsn01.atlas.ripe.net 443 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAA.....................Zc0HyYeiI5vZS3l8xi0IBd2U5 REREGISTER 3600 DHCPV4 True DHCPV6 True PROBE_ID 1000078 /var/atlas-probe/status/ssh_err.txt: RSA host key for IP address '2a01:4f8:110:40b2::2' not in list of known hosts. Permission denied (publickey). ______________________________________________________________
Od: ripe@brite.cz Komu: atlas-sw-probes@ripe.net Datum: 21.01.2020 17:58 Předmět: Re: [atlas-sw-probes] SW Probe offline after reinstall & SSH KEY change
Hi team, it seems it still does not work correctly. I had to change my probe 1000078 hosting server. The situation with SSH KEY is the same as described below. Furthermore on https://atlas.ripe.net/probes/1000078/#!tab-network I can see its new IP addresses, what is weird, since it still shows Offline, but the new IPv4 and IPv6 are there.
Cheers Jiri
_________________________________________________________________________________ Johan ter Beest jterbeest at ripe.net Fri Jan 17 19:36:53 CET 2020 Hi Jiri,
On 17 Jan 2020, at 14:51, <ripe at brite.cz> <ripe at brite.cz> wrote:
Hi team, I have SW probe 1000069 running on router Turris Omnia. I had to commit factory reset and reinstall all software. All went good, I have the SW Probe running, got new SSH KEY [command "/etc/init.d/atlas get_key"] and pasted the new key to web > Update SSH Key. First it accepted, but the probe never managed to connect. I restarted the probe process and even whole router, also tried to get the key from the probe again and when pasting to Update SSH Key field it says "A probe with this key already exists. Please enter a unique key". So the new key is sure recorded correctly.
For some reason the new key was not copied to the probe. I have now done this manually so it should be able to connect now
Probe log: root at turris:~# /etc/init.d/atlas log 01/17/20 12:36:02 ctrl-init 01/17/20 13:39:02 net-try 01/17/20 13:39:05 net-ok 01/17/20 12:39:05 ctrl-init 01/17/20 13:42:06 net-try 01/17/20 13:42:09 net-ok 01/17/20 12:42:09 ctrl-init 01/17/20 13:45:09 net-try 01/17/20 13:45:12 net-ok 01/17/20 12:45:12 ctrl-init
From https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html I read "We'll add a means to replace this key for an existing probe, in case you need to reinstall and lose the original key material." Does it mean it is not implemented yet?
It should be implemented… I will check on Monday why it failed to copy the new key to the probe.
Cheers and have a good weekend :)
Johan
Thank you
Jiri
Hi, This could have been a race condition: the probe is too fast and tries to connect to the controller before the controller gets notified about it coming. It happens. The sw should retry and succeed eventually. I see this probe as connected now. Cheers, Robert On 2020-01-21 18:05, ripe@brite.cz wrote:
Some logs, if it helps:
/var/atlas-probe/status/reg_init_reply.txt: OK REGSERVER_TIMESTAMP 1579623247 2020.01.21-16:14:07 CONTROLLER ctr-fsn01.atlas.ripe.net 443 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAA.....................Zc0HyYeiI5vZS3l8xi0IBd2U5 REREGISTER 3600 DHCPV4 True DHCPV6 True PROBE_ID 1000078
/var/atlas-probe/status/ssh_err.txt: RSA host key for IP address '2a01:4f8:110:40b2::2' not in list of known hosts. Permission denied (publickey).
______________________________________________________________
Od: ripe@brite.cz Komu: atlas-sw-probes@ripe.net Datum: 21.01.2020 17:58 Předmět: Re: [atlas-sw-probes] SW Probe offline after reinstall & SSH KEY change
Hi team, it seems it still does not work correctly. I had to change my probe 1000078 hosting server. The situation with SSH KEY is the same as described below. Furthermore on https://atlas.ripe.net/probes/1000078/#!tab-network I can see its new IP addresses, what is weird, since it still shows Offline, but the new IPv4 and IPv6 are there.
Cheers Jiri
_________________________________________________________________________________ Johan ter Beest jterbeest at ripe.net Fri Jan 17 19:36:53 CET 2020 Hi Jiri,
On 17 Jan 2020, at 14:51, <ripe at brite.cz> <ripe at brite.cz> wrote:
Hi team, I have SW probe 1000069 running on router Turris Omnia. I had to commit factory reset and reinstall all software. All went good, I have the SW Probe running, got new SSH KEY [command "/etc/init.d/atlas get_key"] and pasted the new key to web > Update SSH Key. First it accepted, but the probe never managed to connect. I restarted the probe process and even whole router, also tried to get the key from the probe again and when pasting to Update SSH Key field it says "A probe with this key already exists. Please enter a unique key". So the new key is sure recorded correctly.
For some reason the new key was not copied to the probe. I have now done this manually so it should be able to connect now
Probe log: root at turris:~# /etc/init.d/atlas log 01/17/20 12:36:02 ctrl-init 01/17/20 13:39:02 net-try 01/17/20 13:39:05 net-ok 01/17/20 12:39:05 ctrl-init 01/17/20 13:42:06 net-try 01/17/20 13:42:09 net-ok 01/17/20 12:42:09 ctrl-init 01/17/20 13:45:09 net-try 01/17/20 13:45:12 net-ok 01/17/20 12:45:12 ctrl-init
From https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html I read "We'll add a means to replace this key for an existing probe, in case you need to reinstall and lose the original key material." Does it mean it is not implemented yet?
It should be implemented… I will check on Monday why it failed to copy the new key to the probe.
Cheers and have a good weekend :)
Johan
Thank you
Jiri
participants (2)
-
ripe＠brite.cz -
Robert Kisteleki