Help pllsss - update from server 2.13.x to latest 2.14 failed

ran the update from browser to latest 2.14 , appears update failed - server will not start? (nothing showing in browser)
… all was running fine prior to update , looked at changelog for 2.14 .. didnt appear anything substantive that would cause ??? RPi 4 …. can access Pi and command line et al, grafana running (albeit with no data) , likewise WSK cant find server … havent had to debug this type of issue previously… any guidance pls on where to start?
50 Replies
Greg Young
Greg YoungOP4mo ago
also have tried a RPi reboot - no joy
Scott Bender
Scott Bender4mo ago
Probably old version of nodejs
Greg Young
Greg YoungOP4mo ago
from 2.13 to 2.14 requires a newer nodejs?
Scott Bender
Scott Bender4mo ago
Yep
Greg Young
Greg YoungOP4mo ago
ok… didnt see that in the changelog notes?
Scott Bender
Scott Bender4mo ago
It’s not. You can update nodejs or just revert to previous server.
Greg Young
Greg YoungOP4mo ago
🙂 i feel less dumb.. haha
Scott Bender
Scott Bender4mo ago
Assuming you are on nodejs v18?
naugehyde
naugehyde4mo ago
Don't know about the docs but I found "engines": { "node": ">=20" }, in the package.json file!
Scott Bender
Scott Bender4mo ago
The docs do say v20 now
Greg Young
Greg YoungOP4mo ago
yep just checked 18.20.6 ok my bad … i only looked at the changelog …
Scott Bender
Scott Bender4mo ago
Yeah. We should be something in the there. Let me see if I can add it…
Greg Young
Greg YoungOP4mo ago
nodejs .. update to latest? or a specifiv version? ah .. V20 i assume from yr above comment
Scott Bender
Scott Bender4mo ago
Go to v22
Greg Young
Greg YoungOP4mo ago
noted thx
Scott Bender
Scott Bender4mo ago
And I added a note to the release notes.
Greg Young
Greg YoungOP4mo ago
🙂 hmm did a sudo apt update sudo apt install nodejs … which i thought woud install latest nodejs version .. but it keeps telling me i have the latest (clearly not) .. seems you now? need to specify a version? further .. tried sudo apt install nodejs=22.* .. but this didnt work …
Scott Bender
Scott Bender4mo ago
I don’t recall exactly (I use nvm)
Greg Young
Greg YoungOP4mo ago
ok … i will keep looking
Scott Bender
Scott Bender4mo ago
GitHub
GitHub - nodesource/distributions: NodeSource Node.js Binary Distri...
NodeSource Node.js Binary Distributions. Contribute to nodesource/distributions development by creating an account on GitHub.
Scott Bender
Scott Bender4mo ago
GitHub
Installing and Updating Node.js
An implementation of a Signal K central server for boats. - SignalK/signalk-server
Greg Young
Greg YoungOP4mo ago
noted thx … ouch nodejs updated all ok to V22.x sk server started - all good and showing V2.14 dashboard shows all but n2k plugin working (its throwing an error ) .. im thus assuming i will still need to do the “reinstall plugin” stuff above?
Greg Young
Greg YoungOP4mo ago
No description
Scott Bender
Scott Bender4mo ago
Yes. Can probably just do canboatjs, but easiest to just reinstall everything
Greg Young
Greg YoungOP4mo ago
ok … following the instructions … and praying i dont screw my install! (setting off for 3mth cruise in 3 days!)
Scott Bender
Scott Bender4mo ago
Perfect time to be updating things! 😉
Greg Young
Greg YoungOP4mo ago
yeah i know what ya saying … i was just about to issue the “NO touchig ths system edict”…
Scott Bender
Scott Bender4mo ago
Very Low risk reinstalling plugins
Greg Young
Greg YoungOP4mo ago
noted .. update .. still struggling nodejs updated ok npm updated ok (using sudo npm install npm@latest -g ) following reported nodejs - v V22.16.0 npm -v 11.4.2 renamed .signalk/node_modules (to old_node_modules) ran sudo npm install when inside .signalk directory. it runs for a while, generates buncg warnings (ignore) but a bunch errors - see below. it creates the new .signalk/node_modules directory, with a subdirectory under it mdns (empty) but no files, no other directories.
Greg Young
Greg YoungOP4mo ago
Greg Young
Greg YoungOP4mo ago
No description
Greg Young
Greg YoungOP4mo ago
have tried twice, second time it didnt even create the new node_modules directory under .signalk Update to above 1) .. to get sk "working" ... renamed old_node_modules back to node_modules Restarted skserver ... ALL plugins reporting status ok... except n2k Note my n2k interface is on a USB port , Ive checked using command lsusb, and the interface is definitely there ... havent made any changes & was working as expected prior to the server update
2) following the instructions under "easy way : wipe & reinstall plugins" doesnt appear to work (see above error log) 3) I note in the "correct errors" instructions It states that plugins that use serial ports will fail" (presumably my USB connected n2k interface falls into this category?) .. although I have USB bluetooth interface - with associated plugin, working ok. 3) maybe i just need to "reinstall" the n2k “plugin” (but its installed as part of server i believe?) guidance appreciated .. thx
Greg Young
Greg YoungOP4mo ago
from server log - this presumably connected with item 3) above
No description
Greg Young
Greg YoungOP4mo ago
** question: given that i did the skserver update BEFORE i did the nodejs & npm updates, is this my problem? that is, i should force a further “reinstall” of server? (using sudo npm install -g signalk-server) will this overwrite anything? critical
Scott Bender
Scott Bender4mo ago
Yes, you need to reinstall the server That will not overwrite anything You used sudo when installing plugins That’s definitely going to cause issues down the road
Greg Young
Greg YoungOP4mo ago
resinstalled server - all ok. renamed node_modules ran npm install after changing to .signalk directory. .. exact same error messages as previous ** npm error code 7 npm error path /home/pi/.signalk/node_modules/bufferutil npm error command failed npm error command sh -c node-gyp-build npm error gyp info it worked if it ends with ok npm error gyp info using node-gyp@7.1.2 npm error gyp info using node@22.16.0 | linux | arm64 npm error (node:137025) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead. npm error (Use node --trace-deprecation ... to show where the warning was created) npm error gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3" npm error gyp ERR! UNCAUGHT EXCEPTION npm error gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#<Object>' npm error gyp ERR! stack at createConfigFile (/home/pi/.signalk/node_modules/node-gyp/lib/configure.js:117:21) npm error gyp ERR! stack at /home/pi/.signalk/node_modules/node-gyp/lib/configure.js:84:9 npm error gyp ERR! stack at FSReqCallback.oncomplete (node:fs:188:23) npm error gyp ERR! System Linux 6.6.62+rpt-rpi-v8 npm error gyp ERR! command "/usr/bin/node" "/home/pi/.signalk/node_modules/node-gyp/bin/node-gyp.js" "rebuild" npm error gyp ERR! cwd /home/pi/.signalk/node_modules/bufferutil npm error gyp ERR! node -v v22.16.0 npm error gyp ERR! node-gyp -v v7.1.2 npm error gyp ERR! Node-gyp failed to build your package. npm error gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author. npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-06-20T12_27_01_105Z-debug-0.log
Greg Young
Greg YoungOP4mo ago
dashboard shows this ... is that correct? (never seen that status before)
however still not reciving n2k messages
No description
Greg Young
Greg YoungOP4mo ago
unders status it says "claimed address 100"
Scott Bender
Scott Bender4mo ago
I wonder if the server code needs to be deleted, it may have not rebuilt stuff because it was already there Although the error from npm install could be related.
Greg Young
Greg YoungOP4mo ago
im kinda helpless where to go next ...
Scott Bender
Scott Bender4mo ago
Remove the server code and re-install
Scott Bender
Scott Bender4mo ago
Also, I wonder if python version is an issue. Can you check which version you are running?
Greg Young
Greg YoungOP4mo ago
just completed the server removal and reinstall. no erros reported, a few warns only did a rpi reboot ... !!!! success .. thus far ... n2k now reciving messages! (plugins not working as node_modules was renamed) .. about to try npm install again
Scott Bender
Scott Bender4mo ago
no “sudo”, right?
Greg Young
Greg YoungOP4mo ago
correct.. NO sudo 🙂 before i did that ... i renamed node_modules back, and restarted ... it looks like "all" plugins are working .. interesting... ... so do i still try the npm install ? (after renaming node_modules)
or do i stop fiddling?
Scott Bender
Scott Bender4mo ago
If everything is working, I would stop fiddling
Greg Young
Greg YoungOP4mo ago
i agree .... nothing good happens after 11pm ... MANY thanks for your assistance ... much appreciated
Scott Bender
Scott Bender4mo ago
Welcome!
Greg Young
Greg YoungOP4mo ago
if only getting the weather to play ball was as easy... just had two glorious calm weeks (no sails on my boat:) .. and just when i planned to leave .... 20kts for days ..... and Im not feeling so comfy with 2m wave/swells

Did you find this page helpful?