Cannot upgrade NodeLink

[tmorse305]

@io_guy, thanks for the new version 0.11.2 which fixes the case issue with IoP.

I seem to be stuck at rev at 0.10.6.  When I try the 'Check for Update' I get this:

2022-02-05 16:50:36 - Auto-Update: Checking for program update...
2022-02-05 16:50:37 - Auto-Update: No web update available

How do I update my NodeLink?

Thank you.

Edited February 5, 2022 by tmorse305

[io_guy]

Yep, you're still on a version that uses Net Core 3.  To upgrade you'll need to rerun the install script.  

It's simple, you won't loose any config or data.  

[dwengrovitz]

I'm on a fairly recent version, but am also having issues with the update.  Should I also rerun the install script to complete the update?

 

[io_guy]

Yeah something seems to be going on with the move over of the file.  

Rerunning the script is fine.  

[tmorse305]

@io_guy, I reran the script:

sudo curl -sSL http://automationshack.com/Files/install.sh | bash

 to try and update to v0.11.2 but it had some errors, see the screen shot plus the log file.  The connection to Envisa link is resetting and I could see there is a permission problem writing to the logger file.  Right now I cannot access the browser interface, it just times out.

 

Thank you for any advice you can offer.

logfile_2022-02-06.txt

[io_guy]

I can't tell from your log the versions you're using.  You cut off the first few lines.

On the pi, run "sudo apt upgrade" to get your system updated, then give me the full NodeLink log

[tmorse305]

@io_guy, I did the upgrade, there were many errors, see the upgrade attachment.  I can ping successfully to 93.93.128.193 from the RPi.

The log islogfile_2022-02-06.txt attached but the first few lines are still missing.  I ran the script again around 10:36.  I screen shot the first few lines from putty.

Thanks for your help.

Upgrade.txt

Edited February 6, 2022 by tmorse305

[io_guy]

Looks like you have multiple versions of NodeLink running (hence the 8090 port in use).  Areboot should fix it.

The package errors are likely to do with you still being on buster instead of bullseye.  I wouldn't worrk about it unless you want to be brave:

https://www.tomshardware.com/how-to/upgrade-raspberry-pi-os-to-bullseye-from-buster

[tmorse305]

44 minutes ago, io_guy said:

A reboot should fix it.

It did, thanks again for your help!  No I'm not that brave, if it's not broken...