hart2hart Posted August 14, 2010 Share Posted August 14, 2010 A couple weeks ago I found that my ISY was locked up. It had not been rebooted in a long time so I restarted it and it worked fine. In last few days, the same problem has occured 5 times. The ISY will not respond to admin console requests, web server requests, or to the HomeSeer plugin. It just locked up and before I could plug in a serial cable to view via RS232 interface we had a power outage .. it restarted and looks okay. What should I look at now or after it locks up again? The error message in the HomeSeer log follows: 8/14/2010 5:40:18 PM ISY Insteon COMM: ISY network communication failed to read message data: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Link to comment
hart2hart Posted August 14, 2010 Author Share Posted August 14, 2010 Following is from HyperTerminal when restarting ISY Starting the Device Starting Device Communications Services Initializing the Driver PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module Waiting 2sec to start 'A' to abort Configured IP = 0.0.0.0 Configured Mask = 0.0.0.0 MAC Address= 00:21:b9:01:01:64 --- Product : (1050) ISY 99i 1024 IR --- Max Nodes & Scenes: 1024 Starting ISY Configuring the File System Loading System Configuration Refreshing Device Configurations Loading Nodes Configuration Starting the Logger Service Starting the Time Services Initializing SSL Services SSL Key Size: 512 SERIAL:Connect: port=0 baud=19200 stop=1 data=8 parity=0 : synch=true pd=3 Starting the Alarms & Notifications Service Retrieving Nodes Starting the Logical Device Updater Service Binding the UPnP Device Starting the Security System Starting the Sheü Please Log in Username: Starting the Device Starting Device Communications Services Initializing the Driver PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-10103 : H_ERROR:-10011 : LOGGER:-10103 : n=[null] c=[null] a=[null] LOGGER:-10011 : n=[null] c=[null] a=[null] Waiting 2sec to start 'A' to abort Configured IP = 0.0.0.0 Configured Mask = 0.0.0.0 MAC Address= 00:21:b9:01:01:64 --- Product : (1050) ISY 99i 1024 IR --- Max Nodes & Scenes: 1024 Starting ISY Configuring the File System Loading System Configuration Refreshing Device Configurations Loading Nodes Configuration Starting the Logger Service Starting the Time Services Initializing SSL Services SSL Key Size: 512 SERIAL:Connect: port=0 baud=19200 stop=1 data=8 parity=0 : synch=true pd=3 Starting the Alarms & Notifications Service Retrieving Nodes Starting the Logical Device Updater Service Binding the UPnP Device Starting the Security System Starting the Sheü Please Log in Username: Starting the Device Starting Device Communications Services Initializing the Driver H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module LOGGER: -2 : n=[13 48 FB 1] c=[ ] a=[ ] H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-140005 : Net Module Rule: 14 LOGGER:-140005 : n=[null] c=[Net Mod] a=[null] Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-110022 : /CONF/A34B9.REC H_ERROR:-110012 : /CONF/A34B9.REC LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] Log file open failed /LOG/A.LOG H_ERROR:-100002 : LOGGER:-100002 : n=[null] c=[null] a=[null] LOGGER:-100002 : n=[null] c=[null] a=[null] H_ERROR: -2 : [uNKNOWN ] 02 E1 LOGGER: -2 : n=[null] c=[[uNKNOW] a=[null] Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] H_ERROR:-140005 : Net Module Rule: 1 LOGGER:-140005 : n=[null] c=[Net Mod] a=[null] Password: Authentication failed Please Log in Username: Password: Authentication failed Please Log in Username: Password:Waiting 2sec to start 'A' to abort Configured IP = 0.0.0.0 Configured Mask = 0.0.0.0 MAC Address= 00:21:b9:01:01:64 --- Product : (1050) ISY 99i 1024 IR --- Max Nodes & Scenes: 1024 Starting ISY Configuring the File System Loading System Configuration Refreshing Device Configurations Loading Nodes Configuration Starting the Logger Service Starting the Time Services Initializing SSL Services SSL Key Size: 512 SERIAL:Connect: port=0 baud=19200 stop=1 data=8 parity=0 : synch=true pd=3 Starting the Alarms & Notifications Service Retrieving Nodes Starting the Logical Device Updater Service Binding the UPnP Device Starting the Security System Starting the Sheü Please Log in Username: Starting the Device Starting Device Communications Services Initializing the Driver H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices H_ERROR:-5012 : LOGGER:-5012 : n=[null] c=[null] a=[null] H_ERROR:-5012 : LOGGER:-5012 : n=[null] c=[null] a=[null] UDQPOST: Queue Full: LD H_ERROR:-5012 : H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 . . Many of same repeats removed . H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 LOGGER:-5012 : n=[null] c=[null] a=[null] H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 LOGGER:-5011 : n=[null] c=[uuid] a=[null] . . Many of same repeats removed . LOGGER:-5011 : n=[null] c=[uuid] a=[null] H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] Link to comment
Michel Kohanim Posted August 15, 2010 Share Posted August 15, 2010 Hello hart2hart, Is ISY rebooting by itself or are you rebooting it? With kind regards, Michel Link to comment
hart2hart Posted August 15, 2010 Author Share Posted August 15, 2010 Michel: I am rebooting it by removing power when I find it locked. Not certain if it has rebooted itself at other times that I did not notice. Thanks, Paul Link to comment
Michel Kohanim Posted August 15, 2010 Share Posted August 15, 2010 Hello hart2hart, Please upgrade to 2.8.1. Also, please do let me know the PLM firmware version number. We have had reported lockup issues with PLM version 72 and upon reboot. If you also have device communication errors, I do suspect the PLM to be the issue. But, again, before anything else, please try upgrading to 2.81.. With kind regards, Michel Link to comment
hart2hart Posted August 15, 2010 Author Share Posted August 15, 2010 Michel: The PLM is v72. Do the 5011 and 110022 codes listed in above post suggest more about this issue or is this just normal startup behavior? Paul Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.