Hi, I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working. I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again. Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e Is there anything else I can do? Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe? Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed! Cheers, Cassiano Aquino - EI5HPB
Hi, After sitting there for a long time with an USB drive the probe returned to live, it has been online for the past 7 hours and 30 minutes. Is it possible that this was somehow related to some server side issue? I'm seeing other similar reports from at least one other probe. Thanks! On 8/24/2024 8:29 PM, Cassiano Aquino via ripe-atlas wrote:
Hi,
I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working.
I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again.
Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e
Is there anything else I can do?
Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe?
Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed!
Cheers, Cassiano Aquino - EI5HPB
----- To unsubscribe from this mailing list or change your subscription options, please visit:https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at:https://www.ripe.net/membership/mail/mailman-3-migration/
Cassiano, There has been an incident with controllers, see: https://status.ripe.net/incidents/cxp20fvs62mc Regards, Ernst
On 25 Aug 2024, at 19:58, Cassiano Aquino via ripe-atlas <ripe-atlas@ripe.net> wrote:
Hi,
After sitting there for a long time with an USB drive the probe returned to live, it has been online for the past 7 hours and 30 minutes.
Is it possible that this was somehow related to some server side issue? I'm seeing other similar reports from at least one other probe.
Thanks!
On 8/24/2024 8:29 PM, Cassiano Aquino via ripe-atlas wrote:
Hi,
I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working.
I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again.
Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e
Is there anything else I can do?
Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe?
Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed!
Cheers, Cassiano Aquino - EI5HPB
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
After sitting there for a long time with an USB drive the probe returned to live, it has been online for the past 7 hours and 30 minutes.
Is it possible that this was somehow related to some server side issue? I'm seeing other similar reports from at least one other probe.
This typically happens when a probe cannot reach its controller or if the controller has a problem. The probe gets told by the registration server what firmware it needs to have. If the probe is currently running a lower version, it tries to get that from a controller using SSH. Unfortunately, there are error conditions that are not properly recognized by the probe when it tries to download firmware. Typically the probe then tries to use an empty file as the new firmware. The empty file doesn't match the checksum sent by the registration server and the upgrade is aborted. There may also be issues on the probe, for example if something is wrong with the USB stick.
participants (3)
-
Cassiano Aquino -
Ernst J. Oud -
Philip Homburg