Maresend

Fired up a new Pi3 today, Nodelink started immediately after running your script so i'm up and running! Sorry for wasting your time with a bum pi io_guy and bumbershoot!

So even with the brand new SD card and several attempts, still getting segmentation fault. I'm thinking the Pi itself is somehow faulty. Its quite old and had been sitting in my garage for a couple years. I'll try a new one...

So, got a brand new SD card, mounted the buster image and started up the pi. It ran through a bunch of stuff, for the last 45 mins or so it shows this: "[ OK ] Started Daily apt upgrade and clean activities" with a blinking cursor...

Ok, will do tomorrow sometime. Thanks for your help with this!

pi@raspberrypi:~ $ sudo rm /home/pi/node/NodeLink.dll rm: cannot remove '/home/pi/node/NodeLink.dll': No such file or directory I'm starting to suspect the SD card because I had the segmentation problem when I was on Rasbpian 8. I was resisting the idea because I didn't think the install would work if the card is faulty...

Bare with me - what am I doing wrong with the command: pi@raspberrypi:~ $ rm /home/pi/node/NodeLink.dll rm: cannot remove '/home/pi/node/NodeLink.dll': No such file or directory

Sorry, my previous post about a new install incorrectly said it was stretch. its actually buster (lite, I believe, as I have no GUI) pi@raspberrypi:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

I appreciate your time!

No luck with that one, segmentation fault

not sure if this is exactly the correct way, but... pi@raspberrypi:~ $ dotnet /home/pi/node/NodeLink.dll Segmentation fault Is that the correct way to run it?

Hi io_guy, ran this script: pi@raspberrypi:~ $ sudo apt install curl apt-transport-https Reading package lists... Done Building dependency tree Reading state information... Done curl is already the newest version (7.64.0-4). The following NEW packages will be installed: apt-transport-https 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 149 kB of archives. After this operation, 156 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://mirrors.switch.ca/raspbian/raspbian buster/main armhf apt-transport-https all 1.8.2 [149 kB] Fetched 149 kB in 1s (119 kB/s) Selecting previously unselected package apt-transport-https. (Reading database ... 39961 files and directories currently installed.) Preparing to unpack .../apt-transport-https_1.8.2_all.deb ... Unpacking apt-transport-https (1.8.2) ... Setting up apt-transport-https (1.8.2) ... Then I rebooted and looked for the process: pi@raspberrypi:~ $ ps aux | grep Node pi 743 0.0 0.4 7332 1816 pts/0 S+ 20:52 0:00 grep --color=auto Node should I be re-running the original install script?

Ok, good to know, Thanks for your time Bumbershoot!

Thanks Bumbershoot. I tried running it and it spat this out: pi@raspberrypi:~ $ dotnet /home/pi/node/NodeLink.dll Segmentation fault Is it possible this is because its running on a Pi2? Maybe doesn't have the resources? I couldn't find a definitive answer online.

Noticed that when tring to start NodeLink, Its getting the 5242 segementation fault again. ### 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. ### Cleaning/Creating directories ### Installing .NET Core ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink bash: line 48: 5242 Segmentation fault dotnet /home/pi/node/NodeLink.dll ### Install complete. Login to NodeLink at http://192.168.0.29:8090 Any ideas as to what that means?

Bumbershoot, sorry about the IP addresses, its because I gave up on a raspberry pi that I had previously installed, installed a new one from scratch, hence the new ip address at 192.168.0.29. Everything ran smooth as far as I could tell via the scrip, and i'm able to ssh into it no problem. However, I don't believe Nodelink is running, and have no idea where to go next. Running your script gave this: pi@raspberrypi:~ $ ps aux | grep Node pi 1574 0.0 0.4 7332 1892 pts/0 S+ 17:40 0:00 grep --color=auto Node