GDavis01 Posted April 4, 2018 Posted April 4, 2018 I was having some odd issues with my Raspberry pi3 lately so I decided to a completely clean install on a different card. I set up Raspian Stretch and everything was looking great until I set up NodeLink! I followed the instructions and got it up and running. If I run NodeLink manually it works well, but when it is run from the rc.local file on a reboot I can no longer access NodeLink from a browser on my network! When I look at the running processes on the Rpi after manually starting NodeLink I see the process shows as 127.0.0.1:8090 instead of 10.0.1.69:8090!! Here are the contents of the log file after a reboot with the command in the rc.local file: 2018-04-04 15:48:03 - ISY resolved to 10.0.1.19 2018-04-04 15:48:04 - ISY Error: Network is unreachable (profiles/ns/0/connection) 2018-04-04 15:48:04 - ISY Error: Error getting Node Server list - Root element is missing. 2018-04-04 15:48:04 - ISY Node Server profile set to 1 2018-04-04 15:48:04 - DSC Error: Connection refused. [dsc1] 2018-04-04 15:48:04 - Relay Server: Started on port 2405 2018-04-04 15:48:04 - Auto-Update: Error retrieving update list: Error: NameResolutionFailure 2018-04-04 15:48:56 - DSC: Reconnecting To Server [dsc1] 2018-04-04 15:48:59 - DSC Error: Connection refused. [dsc1] 2018-04-04 15:49:26 - DSC: Reconnecting To Server [dsc1] 2018-04-04 15:49:29 - DSC Error: Connection refused. [dsc1] 2018-04-04 15:49:56 - DSC: Reconnecting To Server [dsc1] 2018-04-04 15:49:59 - DSC Error: Connection refused. [dsc1] 2018-04-04 15:50:26 - DSC: Reconnecting To Server [dsc1] 2018-04-04 15:50:29 - DSC Error: Connection refused. [dsc1] 2018-04-04 15:50:56 - DSC: Reconnecting To Server [dsc1] If I then manually run the NodeLink command (sudo mono /home/pi/node/NodeLink.exe) the processes show 127.0.0.1:8090 and 10.0.1.69:8090! Then I can access NodeLink from any browser on my network. Instead of using rc.local, I tried starting NodeLink as a systemd service... but I ended up with the same result (although the log file didn't show the errors like those above!). I also tried uninstalling and reinstalling mono but that did nothing! I find it odd because I have set this up numerous times on other SD cards and on another Rpi without ever encountering this issue!! Any thoughts on what is wrong?
io_guy Posted April 4, 2018 Posted April 4, 2018 Try setting the raspi-config setting to wait for network on boot.
GDavis01 Posted April 4, 2018 Author Posted April 4, 2018 Thanks for the quick reply... That was spot on!! It now works! I do not remember ever having to set that parameter before!!
io_guy Posted April 4, 2018 Posted April 4, 2018 I'll add it to the howto. Just depends on the persons network. From the log you can see NodeLink couldn't connect to anything, so the interface wasn't up yet.
larryllix Posted April 5, 2018 Posted April 5, 2018 I had the same problem with some light animations software I was writing on a Pi The port is not ready, and then the software gives up on the connection and takes other actions. The same "wait on network" fix cured many problems for me, as well.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.