<div dir="ltr"><div dir="ltr">Il giorno mer 12 feb 2020 alle ore 10:53 Philip Homburg <<a href="mailto:philip.homburg@ripe.net">philip.homburg@ripe.net</a>> ha scritto:<br></div><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">For more details, see our new article on RIPE Labs:<br> <br> <a href="https://labs.ripe.net/Members/alun_davies/ripe-atlas-software-probes" rel="noreferrer" target="_blank">https://labs.ripe.net/Members/alun_davies/ripe-atlas-software-probes</a></blockquote><div><br></div><div>What about upgrading a software probe? </div><div><br></div><div>I just do a "git pull", make a new .deb and "dpkg -i atlasswprobe-5010-2.deb", but something went wrong. </div><div><br></div><div>My probe is now disconnected (<a href="https://atlas.ripe.net/probes/1000163/#!tab-network">https://atlas.ripe.net/probes/1000163/#!tab-network</a>)</div><div><br></div><div><font face="monospace"><b>systemctl status atlas</b></font></div><div><font face="monospace"><br>● atlas.service - Atlas Probe<br> Loaded: loaded (/etc/systemd/system/atlas.service; enabled; vendor preset: enabled)<br> Active: active (running) since Mon 2020-03-02 12:39:16 CET; 8min ago<br> Main PID: 13550 (ATLAS)<br> Tasks: 7 (limit: 2299)<br> Memory: 3.1M<br> CGroup: /system.slice/atlas.service<br> ├─13550 /bin/sh /usr/local/atlas/bin/ATLAS<br> ├─13596 /usr/local/atlas/bb-13.3/usr/sbin/telnetd -b 127.0.0.1 -p 2023 -P /var/atlas-probe/run/telnetd-port2023-pid.vol<br> ├─13617 /usr/local/atlas/bb-13.3/bin/perd -c /var/atlas-probe/crons/main -A 9801 -P /var/atlas-probe/run/perd-main.pid.vol<br> ├─13619 /usr/local/atlas/bb-13.3/bin/eperd -c /var/atlas-probe/crons/7 -A 9807 -P /var/atlas-probe/run/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7<br> ├─13620 /bin/sh /usr/local/atlas/bin/ATLAS<br> ├─13622 /usr/local/atlas/bb-13.3/bin/eooqd /var/atlas-probe/crons/oneoff -A 9809 -P /var/atlas-probe/run/eooqd.pid.vol -i 9<br> └─19503 sleep 180<br><br>Mar 02 12:45:27 ... ATLAS[13550]: Ping works<br>Mar 02 12:45:27 ... ATLAS[13550]: start reg<br>Mar 02 12:45:27 ... ATLAS[13550]: ATLAS registeration starting<br>Mar 02 12:45:27 ... ATLAS[13550]: REASON_FOR_REGISTRATION NEW NO previous state files<br>Mar 02 12:45:27 ... ATLAS[13550]: REGHOSTS <a href="http://reg03.atlas.ripe.net">reg03.atlas.ripe.net</a> 193.0.19.246 2001:67c:2e8:11::c100:13f6 <a href="http://reg04.atlas.ripe.net">reg04.atlas.ripe.net</a> 193.0.19.247 2001:67c:2e8:11::c100:13f7<br>Mar 02 12:45:27 ... ATLAS[13550]: ssh -i /var/atlas-probe/etc/probe_key -p 443 <a href="mailto:atlas@193.0.19.247">atlas@193.0.19.247</a> INIT<br>Mar 02 12:45:27 ... ATLAS[13550]: 255 REGINIT exit with error<br>Mar 02 12:45:27 ... ATLAS[13550]: RESULT { "id": "9001", "time": 1583149527, "macaddr": "fa163e790ec7", "uptime": 1830743, "buddyinfo": [ 1, 0, 0, 1, 2, 1, 1, 0, 1, 1,<br>Mar 02 12:45:27 ... ATLAS[13550]: condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists<br>Mar 02 12:45:27 ... ATLAS[13550]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists<br></font></div></div><div><br></div><div>I think that "dpkg -i ..." generates a <u>new ssh key pair</u>:</div><div><br></div><div>ls -l /var/atlas-probe/etc/<br>total 8<br>-rw------- 1 atlas nogroup 1811 <b>Mar 2 12:36</b> probe_key<br>-rw-r--r-- 1 atlas nogroup 387 <b>Mar 2 12:36</b> probe_key.pub<br></div><div><br></div><div>Questions:</div><div><br></div><div>1) It's possible to upload the new pub key without re-register my probe?</div><div>2) it's possibile to preserve the keys during upgrade (mark as conf file in .deb? ) or I need to make a backup before upgrading?</div><div><br></div><div>E.</div>-- <br><div dir="ltr" class="gmail_signature">| ENRICO ARDIZZONI<br>| Responsabile Ufficio Reti e Sistemi<br>| Università degli Studi di Ferrara</div></div>