SK not Updating
I tried to update to 2.13.4 and could not get SK to update. I tried to update from 2.13.3 to 2.13.5 an still no luck. I have made sure the RPi is updated and follwed the update instructions on the SK Updating Your Installations page. Node version is 18.20.7. Any ideas?
62 Replies
Check the server logs for errors?
Here are the errors wehen I run the update: Mar 25 09:43:22 sh: 1: mpstat: not found
Mar 25 09:43:43 stderr: npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
Mar 25 09:43:43 stderr: npm warn deprecated [email protected]: This package is deprecated. Use the optional chaining (?.) operator instead.
Mar 25 09:43:43 stderr: npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
Mar 25 09:43:43 stderr: npm warn deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
Mar 25 09:43:44 stderr: npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
Mar 25 09:43:45 stderr: npm warn deprecated [email protected]: This package is no longer supported.
I think you updated your nodejs
I will see if I can get it back to an earlier version
No. That’s ok.
v18 is needed
GitHub
FAQ: Frequently Asked Questions
An implementation of a Signal K central server for boats. - SignalK/signalk-server
thank you
Appears to be pointing at the correct location
https://github.com/SignalK/signalk-server/wiki/FAQ:-Frequently-Asked-Questions#server-update-not-updating-the-server-version
/usr/local/lib/node_modules/signalk-server/bin/signalk-server -c /home/Pi/.signalk $*
And if you type ‘which node’ at the command line?
/usr/local/bin/node
Ok. So that’s not the issue.
You are restarting sk after updating?
Yes. Each time I have tried. I have also tried restart and reboot.
Try updating from the command line
sudo npm install -g signalk-server
will do.
Ran it and restarted and still not updated.
Pi@SVLDMPi:~ $ sudo npm install -g signalk-server
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
changed 695 packages in 3m
120 packages are looking for funding
run
npm fund for details‘which npm’
/usr/local/bin/npm
grep version /usr/local/lib/node_modules/signalk-server/package.json
"version": "2.13.3",
"compare-versions": "^3.0.1",
npm view signalk-server version
2.13.5
really strange!
interesting. just not updating what is shows as the current vesion in SK
no
yu still have 2.13.3
oh
"npm view signalk-server version" shows what version is available
got it
we can try something a littile more destructive...
ok
"mv /usr/local/lib/node_modules/signalk-server /usr/local/lib/node_modules/signalk-server.old"
forgot "sudo"
"sudo mv /usr/local/lib/node_modules/signalk-server /usr/local/lib/node_modules/signalk-server.old"
"sudo npm install -g signalk-server"
"grep version /usr/local/lib/node_modules/signalk-server/package.json"
in progress
grep: /usr/local/lib/node_modules/signalk-server/package.json: No such file or directory
so where the heck is it puting it?
ls /usr/lib/node_modules/signalk-server
ls: cannot access '/usr/lib/node_modules/signalk-server': No such file or directory
i checked and that directory does not exist. There is a singalk-server.old directory
seems like there is something really wrong with npm
I've never seen this behaviour before
tiem for a reinstall?
time for me to reinstall?
SK is gone now. Wont start
you can rename that .old directory back
sudo mv /usr/local/lib/node_modules/signalk-server.old /usr/local/lib/node_modules/signalk-server
I would reinstall nodejs (it comes with npm)
and ideas @Teppo Kurki ?
its back
nodejs needs to v18 or v20
i will update and let you know
not sure if it's relevant but on openplotter on pi4 i get..
pi@openplotter:~ $ which npm
/usr/bin/npm
pi@openplotter:~ $ grep version /usr/local/lib/node_modules/signalk-server/package.json
grep: /usr/local/lib/node_modules/signalk-server/package.json: No such file or directory
pi@openplotter:~ $ grep version /usr/lib/node_modules/signalk-server/package.json
"version": "2.13.5",
"compare-versions": "^3.0.1",
pi@openplotter:~ $
i updated and now have node 20.19.0 rebooted, ran the update, restarted SK and the update did not work.
“node -v” shows v20?
v20.19.0
"ran the update" probably meant
sudo npm install -g signalk-server ? or from the ui?
what does npm list -g signalk-server say?
and npm config list/home/Pi/.nvm/versions/node/v20.19.0/lib
└── (empty)
; node bin location = /home/Pi/.nvm/versions/node/v20.19.0/bin/node
; node version = v20.19.0
; npm local prefix = /home/Pi
; npm version = 10.8.2
; cwd = /home/Pi
; HOME = /home/Pi
; Run
npm config ls -l to show all defaults.so, you are using nvm, not a node installed with the package manager
yes but glad to do it a different way if that is better
and have tried the update to SK both ways, UI and command line. Same result.
if you run
nvm deactivate first can you still start node?ran node and it shows node.js v18.20.7
it sounds like you have a regular node install (or have had it at some point) that places stuff in /usr/lib/node_modules (that you tried renaming earlier with Scott) but now you have nvm managed node that probably places -g global installs under /home/Pi/.nvm/versions/node/v20.19.0/lib
what does
npm config list say now?; node bin location = /usr/local/lib/node_modules/node/lib/node_modules/node/bin/node
; node version = v18.20.7
; npm local prefix = /home/Pi
; npm version = 10.9.2
; cwd = /home/Pi
; HOME = /home/Pi
; Run
npm config ls -l to show all defaults.
my apoligies to both you and Scott for being a nuisancenode bin location is rather interesting, but what about
npm list -g signalk-server now?/usr/local/lib/node_modules/node/lib/node_modules/node/lib
└── [email protected]
now, i would have expected that to say 2.13.3
if i were you i would probably get rid of nvm, see https://www.linode.com/docs/guides/how-to-install-use-node-version-manager-nvm/#nvm-uninstall-steps and remove everything under
/home/Pi/.nvm/
that eliminates one level of re/misdirectionLinode Guides & Tutorials
How to Install and Use NVM (Node Version Manager)
Learn to use NVM to install Node.js on your computer. This guide shows you how to install and use NVM and how to install the LTS version of Node.js.
then reboot and see where you are at. if things don't work you can proceed to uninstall and reinstall nodejs and install sk with
sudo npm install -g signalk-serverwill post when I get that done
unistalled nvm
/usr/local/lib/node_modules/node/lib/node_modules/node/lib
└── [email protected]
; node bin location = /usr/local/lib/node_modules/node/lib/node_modules/node/bin/node
; node version = v18.20.7
; npm local prefix = /home/Pi
; npm version = 10.9.2
; cwd = /home/Pi
; HOME = /home/Pi
; Run
npm config ls -l to show all defaults.i think your node environment is wonky because you have installed an npm module with name
node that is a different thing from the actual nodejs that is the program that signalk-server runs under - and this is why there is this node_modules/node/lib/node_modules/node/lib part there
again if I were you i'd remove /usr/local/lib/node_modules/node and everything under it and reinstall nodejs v20
i think npm list -g signalk-server should give you
and not include the node_modules/lib/node... thingok I will get back to you when I get that done
😓 😆 i think your system has the most obfuscation layers i've encountered: nvm and TodayILearned there is an npm module called
node....node -v
Installed v20 and now have other issues. Seems like it would be best to remove several things and reinstall. Let me know what I am missing - Remove NVM, Remove Node, Remove Node JS, Remove SignalK - Then reinstall NodeJS V18 or V20 and install SignalK. I should be able to back up my KIP and SignalK (with Plugins) and restore those when the reinstalltion is complete.
At this point, it would easier start with a fresh os?
Was hoping to avoid that but that is probably best.
Keep your .signalk except for node_modules
Carry them over to the new system and then reinstall plugins after server is up
..or you could switch running sk in docker in current system, but we don’t have that documented