Hello,

 

Every once in a while (maybe once a month or so) my ISY will experience a "lock-up" where it will stop running programs and is no longer accessible on the network until I do a power-cycle. It just happened a few minutes ago, and before power-cycling I checked the following:

 

- Power LED is on; all others off

- Network LEDs lit (at the RJ-45 connector)

- Unable to ping the device

 

After power-cycling, the ISY came back online and is running normally. Neither the regular log nor the error log show anything abnormal - however the last entry in both is at around 0845 (time of lock-up) and resume again at 1015 (time of power-cycle) with a start-up message.

 

Any thoughts on what could cause this, or how to troubleshoot?

 

P.S. FW is 3.1.11

 

Thanks!

 

- Brian

Hi Brian, sincere apologies for tardy reply.

 

1st, please do upgrade to 3.1.13.

 

2nd, please take a look at your Error Log and check for network connection issues and let me know.

 

With kind regards,

Michel

Hi Michel,

 

I have upgraded to FW 3.1.13, and attached the last few entries from the error log prior to the system lockup. Also - I do use network resources extensively and the -140008 errors are quite common. The resources work fine though.

 

Any thoughts would be greatly appreciated.

 

 

Thanks,

 

 

- Brian

 

 

 

---- ERROR LOG ----

 

Tue 2011/12/06 07:23:24 AM System -140008 Net Module Rule: 33:204

Tue 2011/12/06 07:25:02 AM System -140008 Net Module Rule: 32:204

Tue 2011/12/06 08:01:03 AM System -140008 Net Module Rule: 33:204

Tue 2011/12/06 08:01:37 AM System -140008 Net Module Rule: 32:204

Tue 2011/12/06 08:04:06 AM System -140008 Net Module Rule: 33:204

Tue 2011/12/06 08:04:20 AM System -140008 Net Module Rule: 33:204

Tue 2011/12/06 08:13:48 AM System -140008 Net Module Rule: 33:204

Tue 2011/12/06 08:14:27 AM System -140008 Net Module Rule: 33:204

Tue 2011/12/06 10:17:36 AM System -170001 UDQ:Queue Full: LOG

Tue 2011/12/06 10:17:09 AM System -5 Start

Tue 2011/12/06 10:17:19 AM System -170001 [Network] Established

The only time I experienced an ISY lockup seemed associated with my t-stat adapter. But, unlike yours, my error log indicated the last entry was a mode change in the t-stat. Since then, I've installed a new v2.2r adapter so hopefully, issues with the t-stat are a thing of the past.

I've had a number of ISY lockups like that since V3.x. No response from the ISY and a hard power-cycle required to get it going again.

 

Most occurred either during or right after removing or replacing a device, though a couple were just random with nothing special happening. Doing device/link stuff with an EZX10RF device seems to be especially susceptible to this.

 

I haven't seen any ISY lockups since 3.1.13, but it's recent and I haven't done much device adding/replacing in this version.

Prior to 3.x, I hadn't experienced a single lock-up like the few I've seen recently. Also, no unusual Insteon activity was present when it occurred - only network resource usage.

 

Maybe it would be worth it to consider some type of watchdog timer to auto-reset in cases like this? I suppose if it's just a few people experiencing it every once in a while, it's probably not worth it...just a thought.

Anybody seen this under 3.1.13? I tried to query a device and this message popped up.

 

I often put my laptop in hibernation after I use it by closing the lid. Later, I pick it up, log on and start using it where I left off. It seems the Admin Console is less stable (if that's the right word) under the most recent release. What I find is some things work normally, but some things, like state updates and Queries, may not work at all or their state is out-of-sync.

 

Usually, closing the console and restarting it clears things up. But I don't recall having this issue so much with earlier releases.

sanders2222,

 

ISY expires sessions when it cannot communicate with subscribers (including Admin Console). So, when your computer goes to sleep or hibernate mode, ISY will expire the session. The message you see is that the Admin Console, now awake, thinks that it still has a subscription but of course we know that ISY already expired it because AC decided to sleep.

 

With kind regards,

Michel