Re: [atlas] ripe-atlas Digest, Vol 62, Issue 14
On Wed, Oct 19, 2016 at 12:00 PM, <ripe-atlas-request@ripe.net> wrote:
Date: Tue, 18 Oct 2016 12:24:25 +0200 From: Philip Homburg <philip.homburg@ripe.net> To: ripe-atlas@ripe.net Subject: Re: [atlas] probe offline - troubleshooting requested Message-ID: <3af3a709-9198-06d7-19a1-ae367d03a58e@ripe.net> Content-Type: text/plain; charset=utf-8
On 2016/10/18 7:46 , Andre Heinrichs wrote:
Any ideas what I could try to get the probe reconnected?
Just to be complete: Here are the last lines of the SOS history: 62.109.121.35 2016-10-18 05:43:27 A 3h 59m 62.109.121.35 2016-10-18 05:43:27 AAAA 3h 59m
The best thing to try is to reflash the USB stick (i.e. connect the probe without USB stick, wait for a out 10 minutes and insert the USB stick).
Unfortunately, corruption of the filesystem on the USB stick can result in weird behavior, like your probe is showing. SOS works fine but it doesn't connect.
Just for the record: the probe works again after I did the USB fix Philip described. I'm guessing the status tab only showed the hint about Firewall trouble because that would have been another possible cause for the symptoms. Thanks, Andre
Just for the record: the probe works again after I did the USB fix Philip described. I'm guessing the status tab only showed the hint about Firewall trouble because that would have been another possible cause for the symptoms.
The status tab is trying to be helpful in providing the "best guess" of what's wrong, based on the observable symptoms at the infrastructure end. This works most of the time, as long as the problems are caused by network (mis)configuration. But as the example shows it's not always accurate in other cases. We'll most likely cover more failure cases as we discover and understand them. Regards, Robert
participants (2)
-
Andre Heinrichs -
Robert Kisteleki