timlacey Posted May 16, 2009 Share Posted May 16, 2009 I went through my log and found a lot of codes under device "0": 0 /CONF/F Fri 05/08/2009 08:43:32 AM System -110022 0 /CONF/F Fri 05/08/2009 08:43:32 AM System -110012 0 /CONF/F Fri 05/08/2009 10:57:00 AM System -110022 0 /CONF/F Fri 05/08/2009 10:57:00 AM System -110012 0 null Sun 05/10/2009 08:58:20 AM System -5012 0 null Sun 05/10/2009 08:58:34 AM System -5012 0 null Sun 05/10/2009 08:58:34 AM System -5012 0 null Sun 05/10/2009 09:10:37 AM System -10011 0 /CONF/F Sun 05/10/2009 04:40:37 PM System -110022 0 /CONF/F Sun 05/10/2009 04:40:37 PM System -110012 0 /CONF/F Sun 05/10/2009 04:40:37 PM System -110022 0 /CONF/F Sun 05/10/2009 04:40:37 PM System -110012 0 /CONF/F Sun 05/10/2009 05:07:25 PM System -110022 0 /CONF/F Sun 05/10/2009 05:07:25 PM System -110012 0 null Tue 05/12/2009 09:02:16 AM System -5012 0 null Tue 05/12/2009 09:02:16 AM System -5012 0 null Tue 05/12/2009 09:02:16 AM System -5012 0 null Tue 05/12/2009 10:37:26 AM System -10011 0 /CONF/F Wed 05/13/2009 01:40:51 PM System -110022 0 /CONF/F Wed 05/13/2009 01:40:51 PM System -110012 0 (null) Wed 05/13/2009 05:25:29 PM System -2 0 /CONF/F Thu 05/14/2009 08:04:35 AM System -110022 0 /CONF/F Thu 05/14/2009 08:04:35 AM System -110012 0 null Thu 05/14/2009 09:38:13 AM System -5012 0 null Thu 05/14/2009 09:38:23 AM System -5012 0 null Thu 05/14/2009 09:38:23 AM System -5012 0 null Thu 05/14/2009 09:45:41 AM System -10011 0 /CONF/F Thu 05/14/2009 12:21:08 PM System -110022 0 /CONF/F Thu 05/14/2009 12:21:08 PM System -110012 0 /CONF/F Thu 05/14/2009 12:21:08 PM System -110022 0 /CONF/F Thu 05/14/2009 12:21:08 PM System -110012 0 /CONF/9 Fri 05/15/2009 09:26:55 AM System -110022 0 /CONF/9 Fri 05/15/2009 09:26:55 AM System -110012 0 /CONF/F Fri 05/15/2009 09:26:55 AM System -110022 0 /CONF/F Fri 05/15/2009 09:26:55 AM System -110012 How can I identify problems from these codes? Tim Link to comment
timlacey Posted May 16, 2009 Author Share Posted May 16, 2009 I apologize. A new search revealed a link to this: http://www.universal-devices.com/mwiki/ ... r_Messages So my answer is already there. . . now to figure out what these errors are. . . Link to comment
timlacey Posted May 16, 2009 Author Share Posted May 16, 2009 My 5012 errors and the following 10011 errors appear to come from the Homeseer plug-in. I will send a note to Bob about that one. The file open errors for /CONF/F and /CONF/9 seem to be a problem - should I backup the system and upgrade to 2.7.3 and see if those errors stop? Is a -2 error for no device anything unusual? Link to comment
Michel Kohanim Posted May 18, 2009 Share Posted May 18, 2009 Hello timlacey, 5012 you should not worry about (it simply means that ISY has deemed one of its clients unresponsive and thus has expired the subscription). 10011 is a little more serious because it means that someone/something is trying to login without the correct credentials. CONF files may be a problem if they happen all the time: basically, the file ISY was trying to access was locked by some other task for a longer time than ISY deemed normal. -2 means device communication error. If you have this without a device, please look at the next number. I suspect you either have an older firmware (2.7.0 and below) or that your PLM is starting to act up. With kind regards, Michel My 5012 errors and the following 10011 errors appear to come from the Homeseer plug-in. I will send a note to Bob about that one. The file open errors for /CONF/F and /CONF/9 seem to be a problem - should I backup the system and upgrade to 2.7.3 and see if those errors stop? Is a -2 error for no device anything unusual? Link to comment
bpwwer Posted May 18, 2009 Share Posted May 18, 2009 Hello timlacey, 5012 you should not worry about (it simply means that ISY has deemed one of its clients unresponsive and thus has expired the subscription). 10011 is a little more serious because it means that someone/something is trying to login without the correct credentials. Michel, I have these 2 errors (among others) in my log too. So I am a bit concerned that they may be caused by my plug-in. Is there any way to see what client IP address is at fault? I regularly have 3 to 4 clients connect to the ISY (1 or 2 admin consoles, MainLobby Plug-in, and HomeSeer Plug-in). I also have up to 8 computers on my network and a couple other IP enabled devices. Trying to track down what may be trying to log in with bad credentials. Link to comment
Michel Kohanim Posted May 18, 2009 Share Posted May 18, 2009 Hi Bob, As long as the intervals between these attempts is more than 10 minutes, I wouldn't worry about them at all. If you have these continuously every few seconds then we do have problems. We can add remote IP in Event Viewer quicker than in the logs. If you wish, let me know and I'll make a special build for you. With kind regards, Michel Hello timlacey, 5012 you should not worry about (it simply means that ISY has deemed one of its clients unresponsive and thus has expired the subscription). 10011 is a little more serious because it means that someone/something is trying to login without the correct credentials. Michel, I have these 2 errors (among others) in my log too. So I am a bit concerned that they may be caused by my plug-in. Is there any way to see what client IP address is at fault? I regularly have 3 to 4 clients connect to the ISY (1 or 2 admin consoles, MainLobby Plug-in, and HomeSeer Plug-in). I also have up to 8 computers on my network and a couple other IP enabled devices. Trying to track down what may be trying to log in with bad credentials. Link to comment
bpwwer Posted May 18, 2009 Share Posted May 18, 2009 Hi MIchel, Looks like both Tim's and mine are day(s) apart so what we're seeing probably isn't an issue. Thanks for the explanations. Hi Bob, As long as the intervals between these attempts is more than 10 minutes, I wouldn't worry about them at all. If you have these continuously every few seconds then we do have problems. We can add remote IP in Event Viewer quicker than in the logs. If you wish, let me know and I'll make a special build for you. With kind regards, Michel Hello timlacey, 5012 you should not worry about (it simply means that ISY has deemed one of its clients unresponsive and thus has expired the subscription). 10011 is a little more serious because it means that someone/something is trying to login without the correct credentials. Michel, I have these 2 errors (among others) in my log too. So I am a bit concerned that they may be caused by my plug-in. Is there any way to see what client IP address is at fault? I regularly have 3 to 4 clients connect to the ISY (1 or 2 admin consoles, MainLobby Plug-in, and HomeSeer Plug-in). I also have up to 8 computers on my network and a couple other IP enabled devices. Trying to track down what may be trying to log in with bad credentials. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.