On 2013/12/17 13:05 , Ondřej Caletka wrote:
My probe had perfect network connectivity, however it somehow turned its status into „disconnected“ and then „abandoned“, although it still responded to ICMP(v6) ping. Visiting it personally, I found nothing wrong, except the LEDs was blinking in the pattern „running from internal memory“. Long story short, after few round trips with Atlas support, I found out that the probe may be repaired by unplugging the USB flash drive, overwritting it with zeros and plugging it back in.
It would be really nice if this state of probe was displayed somewhere, because the probe was certainly able to talk to the controller. Personally, I would prefer simple status webpage on the probe itself. Read-only access without authentication would suit this purpose perfectly without much extra complexity or security issues.
In this case, you should have had a couple of emails from the Atlas system that your probe was not connected. I think the first one is sent when the probe is not connected for two weeks. This is a situation where the user interface has to be updated. The probe did report that it could not find its USB stick. But that information is not shown to the probe host. Unfortunately, in situations with marginal USB power supplies, probe behavior can become weird. Like overwriting the USB stick is not supposed to have any effect. But in this case it did. Philip