Jump to content

Help EISY error log entries


TheA2Z
Go to solution Solved by Geddy,

Recommended Posts

See error log entries below.  I get them pretty much non-stop.  Any idea of the issue and what I can do to fix?  I am at current levels

image.png.c1720db86f65fbbf8cd799ebc9aeac20.png

Time                          User         Code    Message
Mon 1900/01/01 12:00:00 AM    System    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>    
Tue 2023/11/21 11:17:04 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:17:20 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:17:25 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:17:26 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:17:49 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:17:51 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:18:02 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:18:55 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:19:13 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:19:16 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:19:29 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>

Tue 2023/11/21 11:20:12 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:20:30 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:21:12 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:21:29 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:21:37 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:21:46 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:21:46 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 11:21:53 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
 

Link to comment

@TheA2Z The "-170001" error has always just been blown off as "informational". At least by many users around here.  There is no mention of this error number in the wiki error details. (Just Google site search for "-170001" to see other posts about this.) 

I also have these randomly appearing and don't worry about it.

If really concerned/worried probably best to open a support ticket, but I doubt there's any way to "fix" it since it's been brought up a good bit over the years and nothing had been done to stop/slow these items down. 

https://www.universal-devices.com/my-tickets

  • Like 1
Link to comment

@Michel Kohanim Ticket number is 21458.

I did a test.  I cleared error log at 121PM.  Top part is while I am still logged into Admin.  I only have level: 1. Status/Operational events in event log selected.   I then log out of admin console at 137PM

  1. I get the IoX service errors while logged into admin at 121PM and then when I log back in at 252PM.  I didnt get them when I was not logged into Admin.  What can cause this?
  2. In between those times, I got random Authorization errors.  How do I tell what device is throwing the Auth errors to fix this?

Time                          User         Code    Message
Mon 1900/01/01 12:00:00 AM    System    -170001    <s:Envelope><s:Body><u:GetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetDebugLevel></s:Body></s:Envelope>    
Tue 2023/11/21 01:21:41 PM    0    -170001    <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetErrorLog></s:Body></s:Envelope>
Tue 2023/11/21 01:22:20 PM    0    -170001    <s:Envelope><s:Body><u:SetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"><option>0</option></u:SetDebugLevel></s:Body></s:Envelope>
Tue 2023/11/21 01:22:20 PM    0    -170001    <s:Envelope><s:Body><u:Unsubscribe xmlns:u="urn:udi-com:service:X_IoX_Service:1"><SID>uuid:26</SID></u:Unsubscribe></s:Body></s:Envelope>
Tue 2023/11/21 01:37:13 PM    0    -170001    --308e3d4e328700b91b02df3a1ddaa85e
Content-Disposition: form-data; name="x_Setting"; filename="x_Setting"

0
--308e3d4e328700b91b02df3a1ddaa85e--

Tue 2023/11/21 01:38:50 PM    0    -170001    --308e3d4e328700b91b02df3a1ddaa85e
Content-Disposition: form-data; name="x_Setting"; filename="x_Setting"

0
--308e3d4e328700b91b02df3a1ddaa85e--

Tue 2023/11/21 02:14:14 PM    0    -170001    --308e3d4e328700b91b02df3a1ddaa85e
Content-Disposition: form-data; name="x_Setting"; filename="x_Setting"

0
--308e3d4e328700b91b02df3a1ddaa85e--

Tue 2023/11/21 02:14:14 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:18961->64288
Tue 2023/11/21 02:15:50 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:4705->36895,
Tue 2023/11/21 02:51:11 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:3691->64288,
Tue 2023/11/21 02:51:20 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:17932->64288
Tue 2023/11/21 02:51:20 PM    0    -10108    Check log
Tue 2023/11/21 02:51:21 PM    0    -170001    --308e3d4e328700b91b02df3a1ddaa85e
Content-Disposition: form-data; name="x_Setting"; filename="x_Setting"

0
--308e3d4e328700b91b02df3a1ddaa85e--

Tue 2023/11/21 02:51:21 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:24097->64288
Tue 2023/11/21 02:51:21 PM    0    -10108    Check log
Tue 2023/11/21 02:52:51 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:59622->36895
Tue 2023/11/21 02:52:51 PM    0    -10108    Check log
Tue 2023/11/21 02:52:57 PM    0    -170001    --308e3d4e328700b91b02df3a1ddaa85e
Content-Disposition: form-data; name="x_Setting"; filename="x_Setting"

0
--308e3d4e328700b91b02df3a1ddaa85e--

Tue 2023/11/21 02:52:57 PM    0    -170001    [Auth:-10104] ::ffff:80.94.95.226:47707->36895
Tue 2023/11/21 02:52:57 PM    0    -10108    Check log
Tue 2023/11/21 03:19:58 PM    0    -170001    <s:Envelope><s:Body><u:GetISYConfig xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetISYConfig></s:Body></s:Envelope>
Tue 2023/11/21 03:20:17 PM    0    -170001    Authenticate
Tue 2023/11/21 03:20:18 PM    0    -170001    <s:Envelope><s:Body><u:GetStartupTime xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetStartupTime></s:Body></s:Envelope>
Tue 2023/11/21 03:20:18 PM    0    -170001    <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/INTEGER.VAR</name></u:GetSysConf></s:Body></s:Envelope>
Tue 2023/11/21 03:20:18 PM    0    -170001    <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/STATE.VAR</name></u:GetSysConf></s:Body></s:Envelope>
Tue 2023/11/21 03:20:18 PM    0    -170001    <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>1</type></u:GetVariables></s:Body></s:Envelope>
Tue 2023/11/21 03:20:18 PM    0    -170001    <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>2</type></u:GetVariables></s:Body></s:Envelope>
Tue 2023/11/21 03:20:18 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemOptions></s:Body></s:Envelope>
Tue 2023/11/21 03:20:19 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemOptions></s:Body></s:Envelope>
Tue 2023/11/21 03:20:20 PM    0    -170001    <s:Envelope><s:Body><u:GetNodesConfig xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetNodesConfig></s:Body></s:Envelope>
Tue 2023/11/21 03:20:22 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemTime xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemTime></s:Body></s:Envelope>
Tue 2023/11/21 03:20:23 PM    0    -170001    <s:Envelope><s:Body><u:SetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"><option>1</option></u:SetDebugLevel></s:Body></s:Envelope>
Tue 2023/11/21 03:20:23 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemOptions></s:Body></s:Envelope>
Tue 2023/11/21 03:20:23 PM    0    -170001    <s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_IoX_Service:1"><reportURL>REUSE_SOCKET</reportURL><duration>infinite</duration><send>F</send></u:Subscribe></s:Body></s:Envelope>
Tue 2023/11/21 03:20:23 PM    0    -170001    <s:Envelope><s:Body><u:IsSubscribed xmlns:u="urn:udi-com:service:X_IoX_Service:1"><SID>uuid:27</SID></u:IsSubscribed></s:Body></s:Envelope>
Tue 2023/11/21 03:20:24 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:20:24 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:20:24 PM    0    -170001    <s:Envelope><s:Body><u:RefreshDeviceStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"><sid>uuid:27</sid></u:RefreshDeviceStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:20:25 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:20:25 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:20:29 PM    0    -170001    <s:Envelope><s:Body><u:GetDisclaimerStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetDisclaimerStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:21:14 PM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Tue 2023/11/21 03:21:22 PM    0    -170001    <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetErrorLog></s:Body></s:Envelope>

Link to comment

@TheA2Z,

20 minutes ago, TheA2Z said:

I didnt get them when I was not logged into Admin.  What can cause this?

As I mentioned, these messages are coming from the Admin Console to check how busy is IoX. You will get multiple of these when you start the Admin Console. And, you will get many many more of these if IoX is actually busy. This is the method that the Admin Console uses to figure out when to show you a progress bar. If these bother you, you can set the log level to 0 when you login to the Admin Console (it does not mean that these calls are not made. It just means that they are not going to be logged).

I will have @Chris Jahn to respond to your ticket.

With kind regards,
Michel

Link to comment
  • Solution
16 minutes ago, TheA2Z said:

Are they not required anymore?  Had this setup from a few years ago.

Do you have an active UD Portal subscription? That's been the suggested method of accessing the system (Admin Console) while remote. Port forwarding leaves the system open to port sniffing and risk of attacking...but they don't know what they're attacking. With a UD Portal account you don't need to port forward and just use the URL to Admin Console found in the portal information screen. Just make sure you have a strong portal password and use the portal credentials to log into admin console while remote. (or while using UD Mobile while remote)

 

Good luck on the ticket side. 

 

  • Like 1
Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...