TJF1960 Posted January 7, 2011 Share Posted January 7, 2011 What exactly does this error mean? It is not listed in the wiki and a search of the forum didn't provide any explainations other than some sort of network problem. Thu 2011/01/06 05:39:42 PM System -170001 [uDSockets] 33 active/error 6 I had about a half hour worth yesterday during which time the ISY seemed sluggish. After reboot it seemed ok. I had another of the same error at about the time of the nightly query all program running. I do have athome on an ipad and ipod but both have been asleep for days. And I am using DSCLink which has been working great for almost a week now. Also I have noticed since upgrading to 2.8.10 that a few notifications are not sent per day. I typically receive about 5 emails from the ISY a day. Since the upgrade I will usually miss 1 or 2 emails and its never the same ones that are missing. Not sure if this could be related or not. 2.8.10 with a static ip. Thanks, Tim Link to comment
Michel Kohanim Posted January 7, 2011 Share Posted January 7, 2011 Hi Tim, This is only a warning and you should not worry about it IF they go away by themselves. In short, something opened a socket but did not close it when ISY did the accounting. In all cases, the thing that opens the socket is waiting for something and will eventually close the socket. Sluggishness could be related to devices that have pending updates OR too many things are trying to control INSTEON devices one of which may have communications problems. As far as notifications, if you do not see any -5000x errors (SMTP errors), then the problem is with the programs. With kind regards, Michel Link to comment
TJF1960 Posted January 13, 2011 Author Share Posted January 13, 2011 Hi Michel, When I get the error -17001 it is usually in groups and can last until I have to reboot the ISY. For instance last night at 5:27:09 PM and lasted until I rebooted at 6:07:42 PM The interesting thing is that for the most part the times recorded in the error log all end in multiples of 10 seconds. for instances 5:27:09 next is 5:27:19 then 29 then maybe 59 etc. Here is a shortened list of the error log: 2011/01/12 05:00:38 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:00:47 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:11:38 PM System -140005 CLI-WBug Wed 2011/01/12 05:27:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:27:59 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:09 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:19 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:29 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:39 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:39 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:28:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:49 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:49 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:28:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:59 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:28:59 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:09 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:09 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:19 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:19 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:29 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:29 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:39 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:39 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:49 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:49 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:59 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:59 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:09 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:09 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:19 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:19 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:29 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:29 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:39 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:39 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:49 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:49 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:59 PM System -170001 [uDSockets] 27 active/error 6 Wed Again, this is just a short snippet of the error log, it continues this way until I reboot it During this period programs don't run. At least not that I could tell. Lights that should have turned on or off by programs didn't. However Insteon communication was fine as the motion sensors still turned lights on and off. Also during this period I am unable to log into the admin console. I have tried to log in via the desktop icon and thru the web. So I physically have to go to the ISY and power cycle it. I need to get this fixed. It is occurring at least twice a day now and always requires power cycling the ISY. What am I looking for? I am assuming this is something on my network that is communicating with the ISY? At first I thought perhaps it was my computer which had the admin console open but last nights problem occurred when all of my computers were off so there were no open admin consoles. Any suggestions would be greatly appreciated. Thanks, Tim Link to comment
Michel Kohanim Posted January 14, 2011 Share Posted January 14, 2011 Hi Tim, What else is communicating with your ISY except for the Admin Console? Do you have any mobile applications such as MobiLinc or Conductor? Do you have ELK? With kind regards, Michel Link to comment
TJF1960 Posted January 14, 2011 Author Share Posted January 14, 2011 Hi Michel, Am using AtHome with iPad and iPod but both are powered off completely. Also am using DSCLink on a dedicated desktop only used for that program, with XP. Thanks, Tim Link to comment
Michel Kohanim Posted January 14, 2011 Share Posted January 14, 2011 Hi Tim, I need a huge favor from you: please make sure your AtHome and iPod/Pad are completely off (not connected to ISY) and then disconnect DSCLinc and let me know if you still have the same issue. I do appreciate it very much. The synposis is that something is opening a socket and never closes it. ISY keeps waiting for the socket to get closed but it does not. These are HTTP sockets so it would really help if we figure out if any of the external applications are causing this. Once that has been established, we can figure out what steps to take next. With kind regards, Michel Link to comment
TJF1960 Posted January 14, 2011 Author Share Posted January 14, 2011 No problem, I will let you know. Thanks, Tim Link to comment
TJF1960 Posted January 15, 2011 Author Share Posted January 15, 2011 Hi Michel, Thank you for asking me to make sure the iPad/iPods were off. I remember turning them off but when I checked the iPod was indeed just asleep (I had forgotten my wife had borrowed it and must have left it on). I turned it off and since then I haven't had any -170001 errors like before. I did leave DSCLink running just to see if the errors continued after I turned the iPod off. All has been fine. So my next question is how do I fix it, short of turning it off all of the time? If the iPod is sleeping why is it affecting the ISY 2 to 3 times a day which in most cases requires me to reboot the ISY? Thanks, Tim Link to comment
Michel Kohanim Posted January 16, 2011 Share Posted January 16, 2011 Hi Tim, Thanks so very much for the update. We really need to know what is AtHome doing when in sleep mode or when it wakes up. From your logs, it seems that multiple threads start communicating with ISY (which is normal) but they never close the socket when AtHome goes to sleep. Do you have access to AtHome developers? If so, please do be kind enough to have them contact us at support@universal-devices.com and we'll figure it out. With kind regards, Michel Link to comment
TJF1960 Posted January 16, 2011 Author Share Posted January 16, 2011 Hi Michel, I have sent a request to the developers of AtHome. When a socket is opened, what is the timeout period until the error message? Does the ISY then close the opened socket when the error message is logged? Are all sockets in a closed state after rebooting the ISY or does it retain memory from pre reboot status? Thanks, Tim Link to comment
Michel Kohanim Posted January 17, 2011 Share Posted January 17, 2011 Hi Tim, Please see my comments below. With kind regards, Michel Hi Michel, I have sent a request to the developers of AtHome. Thanks! When a socket is opened, what is the timeout period until the error message? Depends on the type of the socket. For instance, HTTP/HTTPS sockets have a timeout which is configurable in the shell (CWT). Subscription sockets are closed if the subscriber cannot be reached. This said, if the client continues sending HTTP requests, then after a while, all HTTP tasks will be consumed and it might take a while for them to release (backlog of 20) the sockets. I suspect that AtHome, although asleep, is still communicating with ISY and is exhausting the HTTP tasks. Does the ISY then close the opened socket when the error message is logged? No, ISY only closes the socket if there's either timeout or subscriber is not responding. What I think is that AtHome has multiple requests queued up and thus exhausting the HTTP tasks. Are all sockets in a closed state after rebooting the ISY or does it retain memory from pre reboot status? All sockets are closed and discarded when the system is rebooted. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.