I noticed on Jan 7 at 3am reboot there was a hard crash on ALWAYS5. It looks like the client crashed (dropping socket to Java). I am guessing that the client crashed due to some network connectivity problem vis a vis Hangout?
A hint is that the creation date on Dropbox.com for the log file is 12:51pm on Jan 7, which suggests that is when the internet connection came back on.
I was surprised, however, not to see an automatic restart after that. I would expect that the client batch file loop would just hang, but Java should have kept restarting. Maybe the whole machine got powered off (power failure?).
Btw, I tried turning off Wifi and booting the system, which worked fine (of course, the blue light did not come on temporarily for Hangout as it would usually). Maybe there is some other trickier timing condition?
@lring @candysidner
I noticed on Jan 7 at 3am reboot there was a hard crash on ALWAYS5. It looks like the client crashed (dropping socket to Java). I am guessing that the client crashed due to some network connectivity problem vis a vis Hangout?
A hint is that the creation date on Dropbox.com for the log file is 12:51pm on Jan 7, which suggests that is when the internet connection came back on.
I was surprised, however, not to see an automatic restart after that. I would expect that the client batch file loop would just hang, but Java should have kept restarting. Maybe the whole machine got powered off (power failure?).
Btw, I tried turning off Wifi and booting the system, which worked fine (of course, the blue light did not come on temporarily for Hangout as it would usually). Maybe there is some other trickier timing condition?
Do you have any further information or insights?
-CR