Flex Posted November 10, 2012 Share Posted November 10, 2012 I am a newer user to the ISY 994i firmware version 3.2.4 and UI version 3.2.6 and first post. I just added a keypadlinc 6 button dimmer button to a scene. All looked good so I went to test the operation of a new program using that scene. When I got back to the computer I found the system busy dialog bar looping. The prompt says "Please do not power off/unplug the system or make adjustments to linked/attached devices." The progress bar will reach up to 99% complete before restarting again. This can last hours if not days. My system consists of the ISY, two keypadlincs, two Icon switch dimmers, one 2430 controLinc, a couple of lamplincs, and a few x10 devices. This is about the third time this has happened. I have about 20 programs Is there anything one can do to regain the ISY's attention? What would happen if I were to try and reset it, that is power it down and restart. I would like to know why updating a small setup like mine takes so long? Link to comment
LeeG Posted November 10, 2012 Share Posted November 10, 2012 First the system has a bad mismatch. The post says the ISY firmware is at 3.2.4 and the UI Admin Console is at 3.2.6. Don't know if that is the problem but the ISY and UI must always be the same. Suggest updating the ISY to 3.2.6. Clear the Jave cache and start the Admin Console. Link to comment
Flex Posted November 10, 2012 Author Share Posted November 10, 2012 Thank you for your response. I tried clearing the cache. I also have rebooted from the user interface and then when that didn't work also powered down and restarted after about 30 seconds. I still have system busy message. Makes it to 99% complete then starts over it has been like this for over an hour now. It won't let me update till the ISY frees up. A portion of the error log reads, Sat 2012/11/10 02:23:46 PM System -170001 UDQ:Queue Full: PWRIT Sat 2012/11/10 02:23:56 PM System -170001 UDQ:Queue Full: PWRIT Sat 2012/11/10 02:24:06 PM System -170001 UDQ:Queue Full: PWRIT and so forth over and over about every ten seconds Sat 2012/11/10 04:25:38 PM System -170001 UDQ:Queue Full: PWRIT till the last entry, complete with out of place time stamp, which is, Sat 2012/11/10 04:11:29 PM System -5 Start Link to comment
Flex Posted November 11, 2012 Author Share Posted November 11, 2012 In order to install the update I had to do a factory reset on the ISY, then restore the backup. I then made the addition to the scene and the update occured in good time and most importantly, finished. Again thanks, LeeG for your help. Link to comment
Michel Kohanim Posted November 11, 2012 Share Posted November 11, 2012 Hello Flex, PWRIT is the queue in charge of communications with PLM. The only way it would get full is if the PLM is not responding. I do not think factory reset ISY and upgrade actually fixed anything except that perhaps, for one reason or another, the PLM started communicating again (possible loose connection?). So, please do keep an eye ... if you see the same message again in your error log, then it would be best to replace the PLM. With kind regards, Michel Link to comment
Flex Posted November 12, 2012 Author Share Posted November 12, 2012 Michel, I checked the error log again and I am not recieving that error, at least not for now. I will mention that even though the error was occuring the ISY was able to perform its tasks. That is, the programs ran according to schedule, at least some of them did. The ISY and the PLM are about six to eight months old now. I checked the history pior to clearing the log, I had saved it, and yesterday, as far as I could see, was the only occurance of the " UDQ:Queue Full: PWRIT" error. That said, I will continue to watch to see if the error "UDQ:Queue Full: PWRIT" re-occurs. If there is a next time I'll know to look toward the PLM and its cable to the ISY. And I thank you for your response and assistance regarding this issue. This is the most recent error log now, for about the last 24 hours or so. Time User Code Message Sat 2012/11/10 06:31:45 PM System -5 Start Sat 2012/11/10 06:31:46 PM System -110022 /CONF/INSTENG.OPT Sat 2012/11/10 06:31:46 PM System -110012 /CONF/INSTENG.OPT Sat 2012/11/10 06:31:47 PM System -170001 [Network] Established Sat 2012/11/10 03:32:05 PM System -10011 n/a Sat 2012/11/10 03:32:07 PM System -10011 n/a Sat 2012/11/10 03:32:08 PM System -170001 [Auth] 192.168.1.20:2521->80, Num=3 Sat 2012/11/10 03:32:08 PM System -10011 n/a Sat 2012/11/10 03:32:11 PM System -170001 [Auth] 192.168.1.20:2522->80, Num=4 Sat 2012/11/10 03:32:11 PM System -10011 n/a Sat 2012/11/10 03:32:12 PM System -170001 [Auth] 192.168.1.20:2529->80, Num=5 Sat 2012/11/10 03:32:12 PM System -10011 n/a Sat 2012/11/10 03:32:14 PM System -170001 [Auth] 192.168.1.20:2530->80, Num=6 Sat 2012/11/10 03:32:14 PM System -10108 Check log Sat 2012/11/10 03:32:14 PM System -10011 n/a Sat 2012/11/10 03:32:16 PM System -170001 [Auth] 192.168.1.20:2531->80, Num=7 Sat 2012/11/10 03:32:16 PM System -10108 Check log Sat 2012/11/10 03:32:16 PM System -10011 n/a Sat 2012/11/10 03:32:20 PM System -170001 [Auth] 192.168.1.20:2532->80, Num=8 Sat 2012/11/10 03:32:20 PM System -10108 Check log Sat 2012/11/10 03:32:20 PM System -10011 n/a Sat 2012/11/10 03:32:21 PM System -170001 [Auth] 192.168.1.20:2533->80, Num=9 Sat 2012/11/10 03:32:21 PM System -10108 Check log Sat 2012/11/10 03:32:21 PM System -10011 n/a Sat 2012/11/10 03:32:21 PM System -170001 [Auth] 192.168.1.20:2534->80, Num=10 Sat 2012/11/10 03:32:21 PM System -10108 Check log Sat 2012/11/10 03:32:21 PM System -10011 n/a Sat 2012/11/10 03:32:22 PM System -170001 [Auth] 192.168.1.20:2535->80, Num=11 Sat 2012/11/10 03:32:22 PM System -10108 Check log Sat 2012/11/10 03:32:22 PM System -10011 n/a Sat 2012/11/10 03:32:22 PM System -170001 [Auth] 192.168.1.20:2542->80, Num=12 Sat 2012/11/10 03:32:22 PM System -10108 Check log Sat 2012/11/10 03:32:22 PM System -10011 n/a Sat 2012/11/10 03:32:23 PM System -170001 [Auth] 192.168.1.20:2543->80, Num=13 Sat 2012/11/10 03:32:23 PM System -10108 Check log Sat 2012/11/10 03:32:23 PM System -10011 n/a Sat 2012/11/10 03:32:23 PM System -170001 [Auth] 192.168.1.20:2544->80, Num=14 Sat 2012/11/10 03:32:23 PM System -10108 Check log Sat 2012/11/10 03:32:23 PM System -10011 n/a Sat 2012/11/10 03:32:24 PM System -170001 [Auth] 192.168.1.20:2545->80, Num=15 Sat 2012/11/10 03:32:24 PM System -10108 Check log Sat 2012/11/10 03:32:24 PM System -10011 n/a Sat 2012/11/10 06:36:22 PM System -5 Start Sat 2012/11/10 06:36:23 PM System -110022 /CONF/INSTENG.OPT Sat 2012/11/10 06:36:23 PM System -110012 /CONF/INSTENG.OPT Sat 2012/11/10 06:36:23 PM System -170001 [Network] Established Sat 2012/11/10 06:38:44 PM System -5 Start Sat 2012/11/10 06:38:46 PM System -170001 [Network] Established Sat 2012/11/10 06:38:56 PM System -60006 n/a Sat 2012/11/10 08:46:56 PM System -5012 26 Sun 2012/11/11 06:38:49 AM System -100 [DHCP] state=RENEW Link to comment
Michel Kohanim Posted November 12, 2012 Share Posted November 12, 2012 Hi Flex, my pleasure ... The one thing that is NOT normal in your existing error log is all those unsuccessful login attempts from 192.168.1.20. Who's that device and why is it trying to login to ISY if it does not know the credentials? With kind regards, Michel Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.