Jump to content

Nodelink 0.9.12 and mono

kar1024

By kar1024
in NodeLink

Recommended Posts

kar1024 Newbie

kar1024

Posted
Posted

@io_guy

Nodelink 0.9.12 no longer starts under Mono. It actually starts, but fails to bind to port 8090.

Reverting to 0.9.11 and disabling updates solves the problem.

Tried three different versions of mono. Two dockers and straight Debian. Error message is always the same: 

Location: Error starting web config server - Address already in use

 

kar1024 Newbie

kar1024

Posted
  • Author
Posted

Removing location service does not solve the problem in 0.9.12

400 error. Nothing else notable in http header. Chrome log: 

Failed to load resource: the server responded with a status of 400 (Bad Request)
nodelink.*.*/ Failed to load resource: the server responded with a status of 400 (Bad Request)

 

io_guy Advanced

io_guy

Posted
Posted

There was no change to the web server between versions with the exception of some OSX handling.  

Working fine here on raspbian.  

Post your full piece of startup log, not just the error line. 

dwengrovitz Advanced

dwengrovitz

Posted
Posted

I saw a similar message on my Mac after upgrading to the new version, but the web UI was still working.  I restarted the machine and the messages did not reappear when starting Nodelink under mono again. 

kzboray Advanced

kzboray

Posted
Posted

Just updated to NodeLink 0.9.12 on a Pi3 running sketch and it no longer works. Ran update and upgrade then rebooted, no change. 0.9.12. Let me know if I can provide any specific information that might help isolate the issue.

Bumbershoot Advanced

Bumbershoot

Posted
Posted
2 hours ago, glarsen said:

It seems it may be related to mono.  I installed on a Windows 10 machine and everything works normally.

I'm running it normally on the same version of mono.  No errors or issues.  My RainMachine and ISY nodes are updating normally as well.  I'm running it on an RPi  running Debian 9.4 -- Stretch.  If I get some time I'll try to fire it up on a VMWare Fusion image of Fedora 27 and see how it goes... 

2018-03-26 12:48:01 - ISY NodeLink Server v0.9.12 started [4]
2018-03-26 12:48:01 - Mono version: 5.10.1.4 (tarball Wed Mar 21 12:01:46 UTC 2018)
2018-03-26 12:48:02 - Web config server started (http://192.168.1.5:8090)
2018-03-26 12:48:02 - ISY resolved to 192.168.1.20
2018-03-26 12:48:02 - ISY Node Server config detected (profile 2)
2018-03-26 12:48:06 - Relay Server: Started on port 2405

 

rccoleman Advanced

rccoleman

Posted
Posted
3 hours ago, glarsen said:

It seems it may be related to mono.  I installed on a Windows 10 machine and everything works normally.

I'm running NodeLink on an RPI3 with up-to-date Stretch and I got the same "Bad Request (Invalid host)" error repeatedly on Chrome on my Macbook.  I killed NodeLink and restarted it, but there were no obvious errors in the command line output.  I cleared cookies for that site, tried both the local DNS name and IP address, and nothing worked.  I tried with Safari and it connected fine right away, and then I was able to connect using Chrome.  I'm no smarter from the experience, but it's working for me now.

larryllix Advanced

larryllix

Posted
Posted

I found in the past that mono has different software revision levels and different loads for different versions of PRi Raspbian also.

Formerly I had the incorrect install version for Stretch and had more random problems with NodeLink.  When I corrected that and loaded the latest version of mono for  the matching version of Rasbian, many problems went away.

 

I feel most mono and NodeLink problems for my four device types have been mainly fixed now. I had to download and install the correct version from the mono website. On the mono website a different install package is offered for each different version of Raspbian, as well as different mono revisions.

 

2018-03-25 00:14:24 - ISY NodeLink Server v0.9.12 started [4]
2018-03-25 00:14:24 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-03-25 00:14:24 - Web config server started (http://192.168.0.175:8090)
2018-03-25 00:14:24 - ISY resolved to 192.168.0.161
2018-03-25 00:14:25 - ISY Node Server config detected (profile 1)

tibbar Experienced

tibbar

Posted
Posted
52 minutes ago, io_guy said:

No idea what this thing is supposed to be.

Did you open the file?

It's your nodelink docker log from UNRAID.

tibbar Experienced

tibbar

Posted
Posted
54 minutes ago, io_guy said:

No idea what this thing is supposed to be.

If it no use for you, just ignore it.

paulbates Advanced

paulbates

Posted
Posted
8 hours ago, tibbar said:

Well, Just downgraded UNRAID OS from v6.5 back to v6.3.5 and NodeLink is working again.

Tibbar, did you see this at the very bottom of your mht file?

Quote

a fatal error in the mono runtime or one of the native libraries

 

Paul

 

paulbates Advanced

paulbates

Posted
Posted

Some things I tried related to this thread:

  • Raspbian Stretch: Though Nodelink was working for me, I decided to refresh my pi.  I've been getting the out-of-date warning for mono for a while and I had been unable to upgrade it due to dependency problems that I likely caused along the way. I've also been using the same SD card that came with the pi for a number of years and wanted to replace it.

    I took the 20 mins to download stretch, use etcher to put it on a card, copy nodelink, reboot pi and install mono vbnc/complete. Nodelink works fine on that "by the book" fresh install
     
  • W10 iot Core "FWIW": Since i had switched nodelink to my dev pi for "operations",  I also took about an hour and gave the free version of W10iot core a try on my other pi. Easy and fast install, faster even than reloading linux. What I didn't catch is that you simply can't RDP to win10 iot core.

    There are some webby tools to copy things on to it, but mainly it uses powershell :shock: and new specialized CLI type commands like Azure does. :shock: I stopped right there. I'm not learning yet another command line environment. It tries really hard to get you to associate it with an Azure account. I've had free temp Azure accounts, but I'm not going down that path either. My "policy" is:  no cloud dependencies or requirements.

    If you're azure/powershell savvy, it might be worth a try.

Paul

Bumbershoot Advanced

Bumbershoot

Posted
Posted
24 minutes ago, paulbates said:

Some things I tried related to this thread:

  • Raspbian Stretch: Though Nodelink was working for me, I decided to refresh my pi.  I've been getting the out-of-date warning for mono for a while and I had been unable to upgrade it due to dependency problems that I likely caused along the way. I've also been using the same SD card that came with the pi for a number of years and wanted to replace it.

    I took the 20 mins to download stretch, use etcher to put it on a card, copy nodelink, reboot pi and install mono vbnc/complete. Nodelink works fine on that "by the book" fresh install
     
  • W10 iot Core "FWIW": Since i had switched nodelink to my dev pi for "operations",  I also took about an hour and gave the free version of W10iot core a try on my other pi. Easy and fast install, faster even than reloading linux. What I didn't catch is that you simply can't RDP to win10 iot core.

    There are some webby tools to copy things on to it, but mainly it uses powershell :shock: and new specialized CLI type commands like Azure does. :shock: I stopped right there. I'm not learning yet another command line environment. It tries really hard to get you to associate it with an Azure account. I've had free temp Azure accounts, but I'm not going down that path either. My "policy" is:  no cloud dependencies or requirements.

    If you're azure/powershell savvy, it might be worth a try.

Paul

Just for the heck of it, I installed and ran NodeLink in two VMWare Fusion Linux virtual machines just fine: Fedora 27 and Ubuntu 17.10 (Artful Aardvark).  Both were successful, even though the mono versions are older.  YMMV.

tibbar Experienced

tibbar

Posted
Posted
2 hours ago, paulbates said:

Tibbar, did you see this at the very bottom of your mht file?

 

Paul

 

Yes.This is the bottom of log file:

Native stacktrace:

mono() [0x49ff2f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x14bfdb52d3d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x14bfdb188418]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x14bfdb18a01a]
mono() [0x630409]
mono() [0x63069c]
mono() [0x63076f]
mono() [0x627a23]
mono() [0x62821e]
[0x40906c55]

Debug info from gdb:


=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

io_guy Advanced

io_guy

Posted
Posted

FYI, I've been ignoring this topic.  There's been multiple issues/non-issues posted with limited logs.

If you have a specific issue, post a new topic with a log, I'm not sorting through topics like this.

kar1024 Newbie

kar1024

Posted
  • Author
Posted

@io_guy

Would love to have provided logs for the problem. Nodelink logs are empty and mono logs are not enabled in docker package that I was using.

Has anyone tried building a docker package for Nodelink that's not using Mono? Windows server core with full .NET runs in docker just fine. So should Nodelink.

If this fails I'll take the plunge and install straight Nodelink + Mono + Debian so I can get to the mono logs.

kzboray Advanced

kzboray

Posted
Posted

kar1024,

 

I had similar issues with the update from 9.10 to 9.11 and 9.12. I found that there were two problems. First permissions were stopping config.xml from being updated. Second upon startup NodeLink was binding to 127.0.0.0 instead of the assigned port as listed in the config file. This was happening because the network wasn't loading before NodeLink on Pi startup. I inserted a delay in my services script per io_guy's suggestion and that resolved my problems. 

There is also a possibility that if NodeLink starts up before the network loads then the config.xml can be reset to a default state.

If you have nodelink running as a service you can see what happens on boot by doing the following. Reboot your Pi and then do a sudo systemctl status nodelink This should show the startup log and any errors should be listed. There's probably a better way to see that information, but I'm a novice at Linux.

Archived

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

Go to topic listing
×
×
  • Create New...