ISY hangs up - need help reading error log and log file

[baabm]

Can someone help me decipher the Log File and Error log to help identify the following problem. MY ISY occasionally (almost every day) hangs up and stops responding to KPL button pushes, ALEXA commands, and mobilinc control. Background: I have an ISY994 running the latest released firmware. I have  variables called home (both Integer and State), that are normally set by one of 3 methods 1) if I enter or leave a mobilinc geofence, 2) if I hit one of 3 KPL switches in different parts of the house that are in a scene called HOME.  3) If I issue a voice command to ALEXA to set HOME. All 3 of these conditions run a program when the S.Home variable changes and it does a bunch of stuff. (There is also a corresponding AWAY program.)

 

Most of the time this works very well, using all 3 of the techniques. But sometimes mostly in the afternoon, the system seems to hang up. It happens in both leaving and arriving mode: When it's NOT working - if I am home, and I tell Alexa I am leaving I can see that the HOME button on the KPL backlight doesn’t go out as it should, the functions that are supposed to occur also do not occur. If I then hit the KPL, the light goes out, but still nothing happens. The reverse also occurs, If I am away and I come home, sometimes the Geofence doesn’t set the HOME switch, telling Alexa I am home doesn’t set the HOME switch and then hitting the HOME switch turns on its backlight, but nothing happens that should happen. In all these hangup cases, I cannot access the ISY via mobilinc - it is just hung up trying to connect. If I try to start the Admin console, it just hangs up and never gets through the ISY finder, and lastly, when looking at the ISY, the only light it is the power light (no apparent error being detected by the ISY itself).  Also in all cases, I must pull the power on the ISY and restart it. After that, everything seems to work OK until the next time. Thinking that the ISY was getting into some weird state, I bought a timer and had it cycle power on the ISY once a week in the middle of the night. When that didn’t help, I set it cycle the power EVERY night at 2:45am, and that didn’t help either. I have looked at the log and the error log and 1) can’t see anything in the LOG file that throws any light on the problem and 2) can’t decipher the ERROR log at all.

 

Today the system was working well at about 1:40pm when I left the house, but sometime between then and about 4:40pm when I arrived home, the system hung up. At 5:01 I finally restarted the system and it worked after that. I am enclosing part of the error log for today, and ALL of the regular LOG for today. I have annotated where I came and went throughout the day in the log file (last column). I apologize for the size of the log file (over 500 lines long, but I didn’t know what was important and what wasn’t. To help search through it, I have put an XX: in the comment field wherever I annotated something.

 

I am not sure how to approach troubleshooting this so any help would be appreciated. 

 

Thanks,

bob M

 

Error Log:

 

Fri 2017/12/15 02:17:12 PM System -100 [DHCP] state=RENEW

Fri 2017/12/15 02:47:14 PM System -100 [DHCP] state=RENEW

Fri 2017/12/15 03:17:20 PM System -100 [DHCP] state=RENEW

Fri 2017/12/15 03:47:25 PM System -100 [DHCP] state=RENEW

Fri 2017/12/15 04:17:30 PM System -100 [DHCP] state=RENEW

Fri 2017/12/15 04:51:05 PM System -100 [DHCP] state=RENEW

Fri 2017/12/15 04:51:12 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55

Fri 2017/12/15 04:51:21 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55

Fri 2017/12/15 04:51:22 PM System -170001 [uDSockets] SMTP:30 error:6

Fri 2017/12/15 04:51:32 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 137

Fri 2017/12/15 04:51:32 PM System -170001 [uDSockets] SMTP:30 error:6

Fri 2017/12/15 04:51:38 PM System -170001 [uDSockets] SMTP:30 error:6

Fri 2017/12/15 04:51:48 PM System -170001 [uDSockets] SMTP:30 error:6

Fri 2017/12/15 05:00:41 PM System -5 Start

Fri 2017/12/15 05:00:43 PM System -110022 /CONF/INSTENG.OPT

Fri 2017/12/15 05:00:43 PM System -110012 /CONF/INSTENG.OPT

 

 

The LOG FILE is an attachment.

ISY log file 20171215.pdf

[stusviews]

The tiny writing is nice, but difficult to read, so some, like me won't spend the effort to read lengthy, tiny text. Others, like you, are OK with tiny text, but I'll bet you want to reach out to all.

[oberkc]

I am not going to be much help with the logs, but it appears to me that it logged events all the way through 5:01.  This suggests to me that something, at least, was still working.

 

Do you know the LAN IP address of your ISY?  Is it a static address?  Have you tried accessing the ISY via the IP address from a web browser during these moments?  If you can, perhaps that would give access to other troubleshooting options, including looking at whether there is some program in a loop.

[baabm]

Thanks Stu, I didn't realize that the print was so small, I enlarged it.

 

Thanks Oberkc, The messages you see at 5:01 are after I did the reboot, so at that point everything was working again. The suggestion to log in via the IP address is a good one and I'll see if I can do that.

[oberkc]

 

 

Thanks Oberkc, The messages you see at 5:01 are after I did the reboot, so at that point everything was working again. The suggestion to log in via the IP address is a good one and I'll see if I can do that.

Yes, but it showed consistent activity up to that point of trying to log in.  This suggests to me that it was doing something, at least, up until that point when you tried to log in at 4:53.

[Michel Kohanim]

Hi baabm,

 

If you are still having problems, please submit a ticket and we'd be delighted to help you with troubleshooting.

 

With kind regards,

Michel