Happy New Year to all!
Hey Mark, something weird happened early this morning...we had a power failure
. Unfortunately, HS3 (3.0.0.143) crashed and judging from the log excerpt below I think it happened when the Insteon PI could not recover.
The power failure occurs at 2:13:15 and at 2:13:17 Insteon reports a failure; it then tries to restart the port and interface until it fails at 2:16:00 and the PI is shutdown. The log is silent until 6:30:46 which is when I opened the HS3 PC console to see a message saying something about HS3 not being able to restart because a socket was already opened. I've seen this error before occasionally when I stop and restart HS3 without rebooting the PC.
Now the power came back at around 2:40 and BLShutdown should have been triggered by an event using APCUPSD which normally reboots the system...only this time the system was already hanging.
Other info: My Insteon Serial interface is hooked up to a USB to 4 port serial box all of which is powered by the HS3 PC and all of that is kept alive by the UPS. I also generated a (Insteon) support log file but it shows nothing for the time period concerned.
I also have not had the time to write an event that would stop the PI...I'll look at that in a few minutes.
Anyways, my question here is... did HS3 crash because of the Insteon PI?
Thanks!
Hey Mark, something weird happened early this morning...we had a power failure
. Unfortunately, HS3 (3.0.0.143) crashed and judging from the log excerpt below I think it happened when the Insteon PI could not recover.The power failure occurs at 2:13:15 and at 2:13:17 Insteon reports a failure; it then tries to restart the port and interface until it fails at 2:16:00 and the PI is shutdown. The log is silent until 6:30:46 which is when I opened the HS3 PC console to see a message saying something about HS3 not being able to restart because a socket was already opened. I've seen this error before occasionally when I stop and restart HS3 without rebooting the PC.
Now the power came back at around 2:40 and BLShutdown should have been triggered by an event using APCUPSD which normally reboots the system...only this time the system was already hanging.
Other info: My Insteon Serial interface is hooked up to a USB to 4 port serial box all of which is powered by the HS3 PC and all of that is kept alive by the UPS. I also generated a (Insteon) support log file but it shows nothing for the time period concerned.
I also have not had the time to write an event that would stop the PI...I'll look at that in a few minutes.
Anyways, my question here is... did HS3 crash because of the Insteon PI?
Thanks!
Attached Files
Comment