io_guy Posted February 23, 2019 Author Share Posted February 23, 2019 What version of debian are you using? The startup issue is likely because the system is systemd and no hook to run rc.local. To run via systemd (instead of rc.local) follow this post: Not trying to be rude here at all - the startup script was intended for RPi newbies. I kind of assume that someone running this with a linux VM would know enough about linux to handle a manual install. I'll modify the script to work with standard debian/ubuntu as well. This is where a docker install would have likely been a lot easier. Quote Link to comment Share on other sites More sharing options...
paulbates Posted February 23, 2019 Share Posted February 23, 2019 (edited) 10 hours ago, carealtor said: Thanks Paul. This really helped and I have it running now. What I'm still not able to fix (because I know virtually nothing about Linux) is the "startup script" portion of this. I fumbled around and did figure out how to see what was in the /etc directory. There is indeed no rc.local file. Paul, you mentioned "sysctl"... there is a sysctl.conf and a sysctl.d in /etc. I also have Polyglot (and only Polyglot) installed on this same machine and Polyglot does start automatically. Glad you made progress. Its one of those things that it can be hard to achieve, but once you get past it you can forget about it and it just works. I followed generic directions similar to what io_guy posted above, but they were specifically for the pi. I've had nodelink for a while, preceding his "all in one" script. At that time I hunted around the forums and Rpi docs and worked it out that way. This one took me a little time because I'm not experienced at linux either, just enough for basic administration tasks. Paul Edited February 23, 2019 by paulbates Quote Link to comment Share on other sites More sharing options...
carealtor Posted February 23, 2019 Share Posted February 23, 2019 11 hours ago, io_guy said: What version of debian are you using? Debian 9 Quote Link to comment Share on other sites More sharing options...
carealtor Posted February 24, 2019 Share Posted February 24, 2019 Thanks @io_guy and @paulbates for the help. I did get this all sorted out with your help. Quote Link to comment Share on other sites More sharing options...
GPG Posted March 24, 2019 Share Posted March 24, 2019 I am having a problem installing NodeLink. OS is ver 9. Used the following command via putty. sudo curl -sSL http://automationshack.com/Files/install.sh | bash At the end of the installation the console shows the following 3 lines: ### Starting NodeLink ### Install complete. Login to NodeLink at http://192.168.1.252:8090 Cannot open assembly 'home/pi/node/NodeLink.exe' File does not contain a valid CIL image. Does anyone have any suggestions as to how I can start to track down this problem? Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 24, 2019 Author Share Posted March 24, 2019 What is ver 9? Quote Link to comment Share on other sites More sharing options...
GPG Posted March 24, 2019 Share Posted March 24, 2019 Debian 9 on raspberry Pi 3 B+ Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 24, 2019 Author Share Posted March 24, 2019 That script is for a Pi, you should follow the how to for Linux. Quote Link to comment Share on other sites More sharing options...
GPG Posted March 24, 2019 Share Posted March 24, 2019 That's what I am trying to do - install it on a Raspberry pi. Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 24, 2019 Author Share Posted March 24, 2019 Paste the whole log from a script run. Quote Link to comment Share on other sites More sharing options...
GPG Posted March 24, 2019 Share Posted March 24, 2019 I ran the install again and took this from the terminal. pi@raspberrypi:~ $ sudo curl -sSL http://automationshack.com/Files/install.sh | bash ### Installing dirmngr and updating to offical mono repo dirmngr is already the newest version (2.1.18-8~deb9u4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Executing: /tmp/apt-key-gpghome.hwRmb9J9Lc/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF gpg: key A6A19B38D3D831EF: 2 signatures not checked due to missing keys gpg: key A6A19B38D3D831EF: "Xamarin Public Jenkins (auto-signing) <releng@xamarin.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 deb http://download.mono-project.com/repo/debian raspbianstretch main ### Updating System - this may take several minutes All packages are up to date. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Installing mono and relevant dependencies - this may take several minutes libmono-system-net-http-formatting4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). libmono-system-net-http-webrequest4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). libmono-system-net-http4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). mono-vbnc is already the newest version (4.7-0xamarin1+raspbian9b1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Creating directory ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink ### Install complete. Login to NodeLink at http://192.168.1.252:8090 pi@raspberrypi:~ $ Cannot open assembly '/home/pi/node/NodeLink.exe': File does not contain a valid CIL image. Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 25, 2019 Author Share Posted March 25, 2019 Odd, I'd guess the file is getting corrupted during download for some reason. I just tested it here with a new download and it works fine. Quote Link to comment Share on other sites More sharing options...
GPG Posted March 25, 2019 Share Posted March 25, 2019 Thanks for checking into this. Definitely something with how the download portion of the script ran. I repeated it several times, all with the same result. I ended up downloading NodeLink.exe directly from automationshack.com an put it in the raspi node folder. I was then able to setup the isylink node server in the isy. I am now at the point of adding the isylink nodes for the RainMachine. Is there any documentation for adding the the 3 RainMachine nodes. Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 25, 2019 Author Share Posted March 25, 2019 There's not. It should be pretty straightforward. Add the device to nodelink and then a new tab will show up. Enter the rain ip, logon and pass and everything else should work out. Quote Link to comment Share on other sites More sharing options...
Whitehambone Posted March 25, 2019 Share Posted March 25, 2019 23 hours ago, GPG said: I ran the install again and took this from the terminal. pi@raspberrypi:~ $ sudo curl -sSL http://automationshack.com/Files/install.sh | bash ### Installing dirmngr and updating to offical mono repo dirmngr is already the newest version (2.1.18-8~deb9u4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Executing: /tmp/apt-key-gpghome.hwRmb9J9Lc/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF gpg: key A6A19B38D3D831EF: 2 signatures not checked due to missing keys gpg: key A6A19B38D3D831EF: "Xamarin Public Jenkins (auto-signing) <releng@xamarin.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 deb http://download.mono-project.com/repo/debian raspbianstretch main ### Updating System - this may take several minutes All packages are up to date. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Installing mono and relevant dependencies - this may take several minutes libmono-system-net-http-formatting4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). libmono-system-net-http-webrequest4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). libmono-system-net-http4.0-cil is already the newest version (5.18.1.0-0xamarin4+raspbian9b1). mono-vbnc is already the newest version (4.7-0xamarin1+raspbian9b1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Creating directory ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink ### Install complete. Login to NodeLink at http://192.168.1.252:8090 pi@raspberrypi:~ $ Cannot open assembly '/home/pi/node/NodeLink.exe': File does not contain a valid CIL image. I had this same problem, are you behind a Fortigate? Quote Link to comment Share on other sites More sharing options...
GPG Posted March 26, 2019 Share Posted March 26, 2019 @Whitehambone No I am not. @io_guy RainMachine Irrigation Controller now shows as an installed device and RainMachine now shows up in the ISY. However, there are no zones showing up. Something I missed? Quote Link to comment Share on other sites More sharing options...
paulbates Posted March 26, 2019 Share Posted March 26, 2019 1 hour ago, GPG said: . However, there are no zones showing up. Something I missed? Sometimes subnodea are organized under a + sign. Are you seeing that? If no, and it’s your first nodeserver you might have to reboot the ISY to get the node profile recognized. Typically that’s not needed, but worth a try Paul Quote Link to comment Share on other sites More sharing options...
GPG Posted March 26, 2019 Share Posted March 26, 2019 There is no plus in front of RainMachine. I did reboot the ISY. No change. Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 26, 2019 Author Share Posted March 26, 2019 Paste a log of NodeLink after a reboot (of NodeLink) Quote Link to comment Share on other sites More sharing options...
GPG Posted March 27, 2019 Share Posted March 27, 2019 Which nodelink log level should I set? Is a restart from within nodelink sufficient? Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 27, 2019 Author Share Posted March 27, 2019 16 minutes ago, GPG said: Which nodelink log level should I set? Is a restart from within nodelink sufficient? Yep. Default levels. Quote Link to comment Share on other sites More sharing options...
GPG Posted March 27, 2019 Share Posted March 27, 2019 Options are: Emergency, Alert, Critical, Error, Warning, Notice, Information and Debug Quote Link to comment Share on other sites More sharing options...
GPG Posted March 27, 2019 Share Posted March 27, 2019 Are the log files supposed to appear in the node folder? Quote Link to comment Share on other sites More sharing options...
io_guy Posted March 28, 2019 Author Share Posted March 28, 2019 The default, notice. Logs are only saved if you check the option. Otherwise just cut and paste the light window. Quote Link to comment Share on other sites More sharing options...
GPG Posted March 28, 2019 Share Posted March 28, 2019 Finally it is working. I'm not sure why the logs were not showing up. I went back to the initial NodeLink setup and started from scratch. The log then showed up, which helped a lot. I'm sure part of the problem was me being new to the raspberry pi. Thanks much for your help. Looking forward to setting up my sprinkler programs now. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.