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/[email protected]/
[atlas] Updating software probe version (with .deb package)
- Previous message (by thread): [atlas] Updating software probe version (with .deb package)
- Next message (by thread): [atlas] V3 Probe: USB Flash Drive Filesystem Corrupted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
netravnen+ripelist at gmail.com
netravnen+ripelist at gmail.com
Sat Dec 31 15:44:45 CET 2022
👋 On Fri, 30 Dec 2022 at 22:00, Seth David Schoen <schoen at loyalty.org> wrote: > The documentation doesn't specifically mention how to upgrade; can I > assume that making a new .deb from current sources, and then installing > that with dpkg on a machine where an older .deb is installed, will > maintain the credentials and identity of my existing probe? It won't > wipe everything out and require me to re-register as a new software > probe, right? Compile the updated version from source as per usual and install the application from the DEB package. Take note of the SSH key. https://atlas.ripe.net/docs/howtos/software-probes.html Found in /var/atlas-probe/etc The probe identifies itself using the SSH key. Unless the key is regenerated during the upgrade. The probe will continue to chug along. :) *If* the SSH key is regenerated. You can always go to the RIPE Atlas Portal. Log in to manage your probe. And update the probe with the new ssh public key. = No need to register a new one. Either backup up the SSH key, or update the probe settings with the new ssh public key
- Previous message (by thread): [atlas] Updating software probe version (with .deb package)
- Next message (by thread): [atlas] V3 Probe: USB Flash Drive Filesystem Corrupted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]