glarsen Posted June 6, 2018 Posted June 6, 2018 Not sure whether this is significant or not but I frequently see "ISY Error: Data at the root level is invalid. Line 1, position 1. (Error creating variable list)" in the NodeLink logs. Can't say when it started, but it has been happening across several versions at least. Doesn't seem to impact anything as the servers I'm using all seem to work OK. No other errors appear in the log. ISY NodeLink Server v0.9.15 OS: Linux isynode.internal.home 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux Mono version: 5.12.0.226 (tarball Thu May 3 09:49:46 UTC 2018) Servers: ISYData | ISY Logger | RainMachine ISY Version 5.0.12 Cheers and thanks.
rccoleman Posted June 6, 2018 Posted June 6, 2018 I'm gonna predict that io_guy is going to ask for logs...
glarsen Posted June 6, 2018 Author Posted June 6, 2018 Perhaps, but there's nothing much in there: 2018-06-06 00:00:24 - ISY resolved to 192.168.155.50 2018-06-06 00:00:26 - ISY Node Server config detected (profile 3) 2018-06-06 00:00:54 - ISY resolved to 192.168.155.50 2018-06-06 00:00:55 - ISY Node Server config detected (profile 3) 2018-06-06 00:00:56 - Warning: nodesetup.zip file needs updating in ISY 2018-06-06 00:00:58 - ISY Error: Data at the root level is invalid. Line 1, position 1. (Error creating variable list) 2018-06-06 07:59:31 - ISY: ISY node profile nodedef/I_NDEFS.XML updated successfully 2018-06-06 08:00:04 - ISY resolved to 192.168.155.50 2018-06-06 08:00:04 - ISY Node Server config detected (profile 3) 2018-06-06 08:00:07 - ISY Error: Data at the root level is invalid. Line 1, position 1. (Error creating variable list)
io_guy Posted June 6, 2018 Posted June 6, 2018 That's in the logger module. It's crapping out reading the ISY variable list which happens after each subscription connection. If you enable verbose on the log and in the System Config tab we could see what it's crapping out on.
glarsen Posted June 7, 2018 Author Posted June 7, 2018 21 hours ago, io_guy said: That's in the logger module. It's crapping out reading the ISY variable list which happens after each subscription connection. If you enable verbose on the log and in the System Config tab we could see what it's crapping out on. Here's a log from today with the error at 2018-06-07 13:55:55. Cheers. logfile_2018-06-06.txt
io_guy Posted June 9, 2018 Posted June 9, 2018 It seems to be getting crap data for the values of the state variables but my logging doesn't give enough info to see what it is. Next version will have a little more logging there.
glarsen Posted June 9, 2018 Author Posted June 9, 2018 OK. I'll collect the log then and send it again.
glarsen Posted June 9, 2018 Author Posted June 9, 2018 1 hour ago, glarsen said: OK. I'll collect the log then and send it again. Did a little digging here and tried re-saving state variable 1 (it seemed the fail was happening on "vars/get/2"). The must have been some hidden character in there or something, because the error has now disappeared.
glarsen Posted June 10, 2018 Author Posted June 10, 2018 Crap...sorry, but the error came back again today. Again, nothing urgent as everything seems to be working OK.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.