johnnyt Posted December 16, 2012 Posted December 16, 2012 Hi, Am getting a number of the errors below on a daily basis. Could not find the error on wiki and my search in the forum yielded many scenarios that had many more error messages at the same time. In my case I'm not getting any other errors when these occur. Sun 2012/12/16 05:34:12 AM System -170001 [uDSockets] HTTP:25 error:6 Sun 2012/12/16 05:34:37 AM System -170001 [uDSockets] HTTP:25 error:6 Sun 2012/12/16 05:40:39 AM System -170001 [uDSockets] HTTP:25 error:6 Sun 2012/12/16 06:30:39 AM System -170001 [uDSockets] HTTP:25 error:6 Sun 2012/12/16 07:02:12 AM System -170001 [uDSockets] HTTP:23 error:6 Sun 2012/12/16 07:08:11 AM System -170001 [uDSockets] HTTP:31 error:6 Sun 2012/12/16 08:30:10 AM System -170001 [uDSockets] HTTP:25 error:6 Sun 2012/12/16 08:38:10 AM System -170001 [uDSockets] HTTP:25 error:6 Sun 2012/12/16 08:45:21 AM System -170001 [uDSockets] RSub:21 error:6
Michel Kohanim Posted December 16, 2012 Posted December 16, 2012 Hi johnnyt, Those are informational messages and you would see them when you have Admin Console on level 3. It basically means that the end device sent close notify but ISY never received the actual close and it's still waiting. If the same error for the same socket is NOT repeated every 10 seconds and for a duration of more than 2 minutes, then you can ignore these messages. With kind regards, Michel
johnnyt Posted December 16, 2012 Author Posted December 16, 2012 I didn't have the admin console on level 3 when these messages happened early this morning. could this also be warnings related to exchanges between ISY and services subscribed to it other than the console, in my case HomeSeer and DSClilnk? I ask because I do periodically during the day get timeouts in DSCLink like this: 2012-12-15 23:59:05 - ISY Error: The operation has timed out (vars/set/2/12/1)
Michel Kohanim Posted December 17, 2012 Posted December 17, 2012 Hi johnnyt, The only way you would have timeout on clients is if all HTTP tasks are busy doing something. The errors in the long only indicate that a socket that was supposed to close is not closed. This should not cause timeout issues. With kind regards, Michel
Recommended Posts