"disposed object' Crashing

[skunkiechris]

Hi @io_guy,

For the last few days I'm getting constant crashes of NodeLink, with the following error:

2020-08-10 07:59:37 - Relay Server Error: Error: OnClientConnection - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
2020-08-10 07:59:37 - Hon TCP Error: Data Arrival Init - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [hwalrm1]

Any ideas?

Thank you!!

[io_guy]

What version?

Is it crashing NodeLink or does the relay port re-open after the error?

[skunkiechris]

4 minutes ago, io_guy said:

What version?

Is it crashing NodeLink or does the relay port re-open after the error?

It's 0.10.5, and it completely crashes NodeLink.  (Outside of any auto-updates, I've made no changes.) Thanks!!

[io_guy]

Any chance you have auto-update enabled and your system downloaded 0.10.6?  Possible multiple instances running?

[skunkiechris]

I do have auto-update enabled, and Friday is when this started...and I wasn't home this weekend and it was fine when I left and crashed when I got home, so I definitely didn't change something I'm forgetting about.  I re-downloaded from your web page to ensure it wasn't just a corrupt update download.  It's showing 0.10.5 on the web page for the app now.  Definitely not multiple instances running.  Should I try changing to .0.10.6?

I've literally changed nothing and it's been humming along forever with no issues, and I can't imagine how it would be related but I'm also wondering if the SD card is getting flakey...

[io_guy]

Something doesn't make sense.  The download from my page would be 0.10.6 so something isn't running correctly. It's quite a coincidence that the crashing started Friday since that's when 0.10.6 was released.

Also, the log errors are not a program "crash", they are handled.  Can you start NodeLink from putty so that you can see the actual crash error?

[skunkiechris]

On 8/10/2020 at 5:40 PM, io_guy said:

Something doesn't make sense.  The download from my page would be 0.10.6 so something isn't running correctly. It's quite a coincidence that the crashing started Friday since that's when 0.10.6 was released.

Also, the log errors are not a program "crash", they are handled.  Can you start NodeLink from putty so that you can see the actual crash error?

I did try swapping the SD card just to make sure, the error persists.  Yup, I'll start it up and let it run that way until it crashes....sometimes it happens in a few mins, sometimes it's hours.  I'll post back when I have the error.  Thanks for your help!!

[skunkiechris]

Well, running it from a command line I got this:

App Is Exiting...
2020-08-12 10:17:08 - Relay Server Error: Error: OnClientConnection - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
2020-08-12 10:17:08 - Hon TCP Error: Data Arrival Init - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [hwalrm1]

However, I don't know if that's the same error because the app restarted immediately after the error.  So not sure if it's something else causing the crash (although when I logged to file above it did appear to be the disposed object thing) or if the behavior is just different when started from a command line vs a service...

Edit: It had not been auto updating to .10.6, so I manually updated it and am running .10.6 now - so keep that in mind as well.

Edit2:  Still occurring. 

[skunkiechris]

Well, I did absolutely nothing and it's been up since Weds morning with no crashes, so I have no idea!

[gregkinney]

I started getting this same error yesterday

2020-09-18 11:13:04 - Web Request: /isylink/nodes/n001_hwalrm1_part1/cmd/DISARM
2020-09-18 11:13:06 - Hon TCP: No poll response, attempting to reconnect to alarm [hwalrm1]
2020-09-18 11:13:06 - Hon TCP Error: Data Arrival Init - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [hwalrm1]

Top of nodelink page shows 0.10.6. It does not crash NodeLink.

[gregkinney]

And 90 seconds after I posted this it updates for the first time in 2 days. It's working at the moment, I'll report back if it stops.

[Javi]

@io_guy are the log lines for "[hwalrml]"  related to the ISY or polling the device....asking for a friend.

2020-09-18 11:13:06 - Hon TCP: No poll response, attempting to reconnect to alarm [hwalrm1]

 

[io_guy]

Device

[gregkinney]

Yesterday I started getting this message:

2020-09-20 09:57:11 - Hon TCP: Reconnecting To Server [hwalrm1]
2020-09-20 09:57:11 - Hon TCP: Polling Alarm [hwalrm1]
2020-09-20 09:57:11 - Hon TCP Error: Data Arrival Init - Connection reset by peer [hwalrm1]
2020-09-20 09:57:11 - Hon TCP Error: Send Data - Broken pipe [hwalrm1]
2020-09-20 09:57:41 - Hon TCP: Reconnecting To Server [hwalrm1]
2020-09-20 09:57:41 - Hon TCP Error: Connected - Connection reset by peer [hwalrm1]
2020-09-20 09:58:11 - Hon TCP: No poll response, attempting to reconnect to alarm [hwalrm1]
2020-09-20 09:58:11 - Hon TCP: Reconnecting To Server [hwalrm1]
2020-09-20 09:58:11 - Hon TCP Error: Connected - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [hwalrm1]

@io_guy can you offer guidance where I should start to troubleshoot? Would the issue likely be with NL, EVL, ISY, Honeywell?

[gregkinney]

Ok I finally got to the bottom of it. I mistakenly adjusted cron and a previous instance of HonLink was running.