Jump to content

NodeLink and Mono Version


DennisC

Recommended Posts

Is there any issue running NodeLink under Mono version 5.16.0.179?

After doing an update to this version, I couldn't get NodeLink to run. After much difficulty, I decided to reinstall Mono, however, I can't get past the following:

Mono precompiling /usr/lib/mono/4.5/Microsoft.CodeAnalysis.CSharp.dll for arm...

Thanks for any help.

Dennis

Link to comment
Share on other sites

Until mono releases a fix I did this:

- Commented out the repo in /etc/apt/sources.list.d/mono-official.list
- Ran sudo apt update
- Removed mono (sudo apt remove --purge --auto-remove mono-runtime)
- Installed raspbian version (sudo apt-get install mono-vbnc mono-complete)

This brings you back to 4.6.2.7.  Not ideal but it works.

Once it's fixed you'd just remove the mono-official comment and apt update.

Link to comment
Share on other sites

10 hours ago, io_guy said:

Until mono releases a fix I did this:

- Commented out the repo in /etc/apt/sources.list.d/mono-official.list
- Ran sudo apt update
- Removed mono (sudo apt remove --purge --auto-remove mono-runtime)
- Installed raspbian version (sudo apt-get install mono-vbnc mono-complete)

This brings you back to 4.6.2.7.  Not ideal but it works.

Once it's fixed you'd just remove the mono-official comment and apt update.

Thank you! Following your instructions, I was able to revert back to Mono v4.6.2.7 and get NodeLink running again.

I did have an extra step to perform however. Apparently, the error (previous post) was preventing me from removing mono-runtime. I had to remove the files inside /var/lib/dpkg/updates first. Once I did that everything else went as you described.

Thanks again for your assistance.

Link to comment
Share on other sites

4 hours ago, DennisC said:

Thank you! Following your instructions, I was able to revert back to Mono v4.6.2.7 and get NodeLink running again.

I did have an extra step to perform however. Apparently, the error (previous post) was preventing me from removing mono-runtime. I had to remove the files inside /var/lib/dpkg/updates first. Once I did that everything else went as you described.

Thanks again for your assistance.

As a matter of interest what RPi version are you installing to?

Link to comment
Share on other sites

4 hours ago, TJF1960 said:

Sorry for the stupid question but can you give an example of an http client you were referring to ?

Thanks,

Tim

Mono can use http:// to talk to the ISY and nodelink supported devices on local APIs.

Examples of devices that nodelink supports on a local api via http: includes the rainmachine and Venstar Colortouch Thermostats.

Paul

Link to comment
Share on other sites

On 10/15/2018 at 9:00 AM, DennisC said:

Thank you! Following your instructions, I was able to revert back to Mono v4.6.2.7 and get NodeLink running again.

I did have an extra step to perform however. Apparently, the error (previous post) was preventing me from removing mono-runtime. I had to remove the files inside /var/lib/dpkg/updates first. Once I did that everything else went as you described.

Thanks again for your assistance.

I reinstalled the broken 5.16.0.179 to test out using the interpreter instead of JIT (saw it work for someone on a forum).  FYI, it doesn't work.

Another forum mentioned that this is RPi specific and that it has something to do with the complete library (which didn't make a lot of sense to me, but I figured I'd try).  So I removed all of mono again and reinstalled with just "sudo apt install mono-vbnc libmono-system-net-http*" and all is running fine now.

If you've got a few minutes and some bravery it could be worth trying.  Otherwise I noticed the bug made it to mono's "bug week" so it'll be fixed in the next minor release.

Link to comment
Share on other sites

7 hours ago, io_guy said:

I reinstalled the broken 5.16.0.179 to test out using the interpreter instead of JIT (saw it work for someone on a forum).  FYI, it doesn't work.

Another forum mentioned that this is RPi specific and that it has something to do with the complete library (which didn't make a lot of sense to me, but I figured I'd try).  So I removed all of mono again and reinstalled with just "sudo apt install mono-vbnc libmono-system-net-http*" and all is running fine now.

If you've got a few minutes and some bravery it could be worth trying.  Otherwise I noticed the bug made it to mono's "bug week" so it'll be fixed in the next minor release.

I fear I'm not knowledgeable enough to recover if I get in to trouble. I think I will wait until it's proven to be fixed. I like it when things work. Lol

Thanks for keeping me informed.

Link to comment
Share on other sites

3 hours ago, DennisC said:

I fear I'm not knowledgeable enough to recover if I get in to trouble. I think I will wait until it's proven to be fixed. I like it when things work. Lol

Thanks for keeping me informed.

If things are working, you can continue to upgrade nodelink and not mono. I'm sure not upgrading mono.

Paul

Link to comment
Share on other sites

On ‎10‎/‎20‎/‎2018 at 9:20 PM, io_guy said:

I reinstalled the broken 5.16.0.179 to test out using the interpreter instead of JIT (saw it work for someone on a forum).  FYI, it doesn't work.

Another forum mentioned that this is RPi specific and that it has something to do with the complete library (which didn't make a lot of sense to me, but I figured I'd try).  So I removed all of mono again and reinstalled with just "sudo apt install mono-vbnc libmono-system-net-http*" and all is running fine now.

If you've got a few minutes and some bravery it could be worth trying.  Otherwise I noticed the bug made it to mono's "bug week" so it'll be fixed in the next minor release.

This worked great for me. Thanks io_guy!

Question, once the bug is fixed do we revert back to the original package and upgrade or stick with this package just installed?

Edit: I noticed I am getting "TCC Login Error: The socket is not connected" errors. Could it be this version of mono?

Link to comment
Share on other sites

On 10/20/2018 at 4:42 PM, paulbates said:

Mono can use http:// to talk to the ISY and nodelink supported devices on local APIs.

Examples of devices that nodelink supports on a local api via http: includes the rainmachine and Venstar Colortouch Thermostats.

Paul

I'm running the affected version of Mono (version: 5.16.0.179) on an RPi, and my RainMachine is connecting to NodeLink over http -- "Use HTTPS" is NOT checked in the NodeLink configuration.  It's working...  ?

I've certainly got no clue.

Link to comment
Share on other sites

I'm running the affected version of Mono (version: 5.16.0.179) on an RPi, and my RainMachine is connecting to NodeLink over http -- "Use HTTPS" is NOT checked in the NodeLink configuration.  It's working... 
I've certainly got no clue.

Yep, and I believe you. But as a traveler with a fully locked down firewall config, I can’t risk knocking out ‘prod’ for no substantive improvements. I only update my pi once a year anyway, or if there is a significant relevant security patch.

Paul


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...