nielsreijers
commented
10 years ago Just to record it on github, although we need to sort things out more thoroughly and probably split it into several issues, we saw the nodes break down in 4 different ways:
1) The node says "PANIC 100", which means the Zwave initialisation code has failed 2) The node doesn't say anything at all, not even after reprogramming. We have several boards in this state. I'm not sure how the ended up this way, or if they will "magically recover" as some seem to have done. 3) The node runs for a bit, then the output on the screen freezes. Sometimes it actually still seems to work, just without output. Sometimes it seems to have really crashed. 4) The VM throws an exception in Java. I have never seen this happen once in all the time we've been using Darjeeling. It may be a software bug, but since we've only seen it on a node that was showing all the other problems on and off again as well, it may also be some hardware related issue.
There were different ways of "fixing" each: 1) It often worked after one (or more) reboots 2) It seems these boards didn't recover, even after reprogramming 3/4) Reboot often revived the node, but more often than not they would crash before to long (mostly in the same way)
On Fri, Nov 15, 2013 at 10:20 AM, catlikethief notifications@github.comwrote:
During this demo, it's very often to see this situation, From the experience, we can upload the vm or reboot the node again to avoid this problem. But for now, we have no idea how it happens.
— Reply to this email directly or view it on GitHubhttps://github.com/wukong-m2m/wukong-darjeeling/issues/110 .
_
During this demo, it's very often to see this situation, From the experience, we can upload the vm or reboot the node again to avoid this problem. But for now, we have no idea how it happens.