ralbright Posted February 21, 2018 Author Posted February 21, 2018 22 minutes ago, larryllix said: You could try the "Install NodeDef Files" again, or delete the nodes in ISY and then try installing them again. I would try them in that order. You may have some program lines using them, to refresh after, though. Currently there are 0 programs trying to utilize the data from the GEM (I haven't made it that far yet.) I did both of your options above. I am still getting the error message: Warning: nodesetup.zip file needs updating in ISY HOWEVER, I am receiving data on all active channels. BUT, I am receiving the error message in the NodeLink Server: 2018-02-20 22:36:01 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-20 22:36:01 - GEM: Reconnected [gem1] Problem is, I have no idea what object it is trying to access.
ralbright Posted February 21, 2018 Author Posted February 21, 2018 Okay, I have a love hate relationship with this thing. Love it when it works, hate it trying to set everything up. (Once it is setup, it works, and I love it....) I went into the GEM setup and changed the data to push every 5 seconds (rather than at every 10 seconds). Then rebooted the NodeLink once again (at least the 10th time), I am still getting the error message: "Warning: nodesetup.zip file needs updating in ISY", however the Socket Error is now gone. ????
io_guy Posted February 21, 2018 Posted February 21, 2018 Nodedef warning is a bug in new versions, will fix it tonight.
ralbright Posted February 21, 2018 Author Posted February 21, 2018 3 hours ago, io_guy said: Nodedef warning is a bug in new versions, will fix it tonight. Could you perhaps while you are fixing that error. Also indicate what stale object the NodeLink Server is looking for that it could not find. My error above is rather weird, (at least to me), I think it is trying to find a Node that I deleted but it didn't recreate. But in the last 9 hours I have not gotten that error again.
io_guy Posted February 21, 2018 Posted February 21, 2018 Not really, it's not a object to play with. It's the node server definition files.
ralbright Posted February 28, 2018 Author Posted February 28, 2018 So over the past few days, I have been monitoring my NodeLink Server. Which is now on 0.9.10. (auto updated). I am still getting the error: 2018-02-28 08:09:44 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 08:09:44 - GEM: Reconnected [gem1] However on the plus side, Nodedef warning has gone away.
io_guy Posted February 28, 2018 Posted February 28, 2018 The first error is just cleanup i need in the messages. The error is the socket disconnecting between the Pi and GEM and it reconnecting. Pretty standard unless it's happening frequently.
ralbright Posted February 28, 2018 Author Posted February 28, 2018 7 minutes ago, io_guy said: The first error is just cleanup i need in the messages. The error is the socket disconnecting between the Pi and GEM and it reconnecting. Pretty standard unless it's happening frequently. Happens every 30 seconds. (between the Pi and GEM? I am using the ISY.) 2018-02-28 09:24:16 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:24:16 - GEM: Reconnected [gem1] 2018-02-28 09:24:46 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:24:46 - GEM: Reconnected [gem1] 2018-02-28 09:25:16 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:25:16 - GEM: Reconnected [gem1] 2018-02-28 09:25:46 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:25:46 - GEM: Reconnected [gem1] 2018-02-28 09:26:16 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:26:16 - GEM: Reconnected [gem1] 2018-02-28 09:26:46 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:26:46 - GEM: Reconnected [gem1] 2018-02-28 09:27:16 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:27:16 - GEM: Reconnected [gem1] 2018-02-28 09:27:46 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:27:46 - GEM: Reconnected [gem1] 2018-02-28 09:28:16 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:28:16 - GEM: Reconnected [gem1] 2018-02-28 09:28:46 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:28:46 - GEM: Reconnected [gem1] 2018-02-28 09:29:16 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:29:16 - GEM: Reconnected [gem1] 2018-02-28 09:29:46 - GEM: Socket Error - Send Data - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [gem1] 2018-02-28 09:29:46 - GEM: Reconnected [gem1]
io_guy Posted February 28, 2018 Posted February 28, 2018 Can you enable debug logging on the NodeLink GEM page and on the Main page. I want to see what's being sent. What's your GEM send interval?
ralbright Posted March 1, 2018 Author Posted March 1, 2018 My GEM send interval is set at 15 seconds. Here is a few minutes of log file under debug mode. logfile_2018-02-28 - Copy.txt
io_guy Posted March 1, 2018 Posted March 1, 2018 Wrong debug. Looking for GEM page, not System Config page.
ralbright Posted March 1, 2018 Author Posted March 1, 2018 10 minutes ago, io_guy said: Wrong debug. Looking for GEM page, not System Config page. Okay, how do I get that? I set the Log Level in Gem1 (on NodeLink Server, page for the GEM device) to Debug level logging. But I am not seeing any additional log files being created. (Or is this a log file created by the GEM itself?
io_guy Posted March 1, 2018 Posted March 1, 2018 Then something doesn't add up. You'll see GEM: data lines if you're getting data in from the device and being sent to the ISY. Just give me a longer log then, that was only 1 minute, give me 5.
ralbright Posted March 1, 2018 Author Posted March 1, 2018 Here is a 10 minute log file. logfile_2018-02-28 - Copy.txt
io_guy Posted March 1, 2018 Posted March 1, 2018 There's no GEM data coming in or sent to the ISY there. The socket error is coming from a failed Ping to the GEM because NodeLink never receives any data. You sure you're connected to the right port?
ralbright Posted March 1, 2018 Author Posted March 1, 2018 28 minutes ago, io_guy said: There's no GEM data coming in or sent to the ISY there. The socket error is coming from a failed Ping to the GEM because NodeLink never receives any data. You sure you're connected to the right port? Ummm.... I am quite sure, as I am getting data updated in the ISY. Refer to attached image
io_guy Posted March 1, 2018 Posted March 1, 2018 You sure that wasn't a one time gig when playing with ports? There's nothing in your log. I'm talking GEM port.
ralbright Posted March 1, 2018 Author Posted March 1, 2018 The variables change every 15 seconds or so, I am getting data through the NodeLink server from the GEM. The data reflects what the GEM page shows. I am thinking the log file I sent was not capturing GEM debug data for some reason. I restarted NodeLink prior to leaving for some meetings I had this evening. Came back and looked at it. There are lines related to GEM I have attached that log file (it is big.) logfile_2018-02-28.txt
ralbright Posted March 1, 2018 Author Posted March 1, 2018 So, rebooting NodeLink, rebooting GEM seemed to do the trick. However as the logs show it looks like the data is timing out. The connection appears to drop, 5 seconds later I get a data packet from the GEM, then 22 seconds (or so) later the Socket error.... wash, rinse, repeat logfile_2018-02-28 - Copy (2).txt
ralbright Posted March 4, 2018 Author Posted March 4, 2018 io_guy: Were you able to decipher why I am getting this error?
io_guy Posted March 4, 2018 Posted March 4, 2018 You're not getting data every 15s, your getting it every 30s, after the socket reconnects. If the socket was open you'd see data every 15s. Why the socket is dropping off, dunno. Try it on a different machine and see if it makes a difference.
ralbright Posted March 4, 2018 Author Posted March 4, 2018 Tried it on 2 other machines. Same result, every 30 seconds the GEM disconnects and reconnects. This is really weird, however I am receiving data.
io_guy Posted March 4, 2018 Posted March 4, 2018 Can you open the GEM port through your router? I'll try it here.
ralbright Posted March 4, 2018 Author Posted March 4, 2018 6 minutes ago, io_guy said: Can you open the GEM port through your router? I'll try it here. PM sent
ralbright Posted March 5, 2018 Author Posted March 5, 2018 So due to failures to open ports on my firewall (dang pfSense router), we were unable to test this.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.