Unable to update Signal K from version 2.14.0
Hi everybody. For some reason the update process is failing in my Signal K setup from version 2.14.0 (it worked flawlessly in the previous updates).
I am enclosing the related Server log, I would appreciate any clue (I am not used to the linux intrincacies).
Thnak you.
13 Replies
the error message looks like you npm installation is broken. can you invoke for example
npm -version and npm list -gIf I do either of those i get error messages, so I suppose NPM is broken. I will try to reinstall it.
npm reinstalled but still no joy, unable to update Signal K Server from version 2.14.0
The npm version is 11.5.2.
Now the error messages are different:
Aug 20 12:35:25 stderr: npm warn deprecated inflight@1.0.6: 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.
Aug 20 12:35:25 stderr: npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
Aug 20 12:35:25 stderr: npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
Aug 20 12:35:25 stderr: npm warn deprecated lodash.isequal@4.5.0: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
Aug 20 12:35:25 stderr: npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
Aug 20 12:35:25 stderr: npm warn deprecated fstream@1.0.12: This package is no longer supported.
Aug 20 12:36:01 stdout: changed 670 packages in 1m
Aug 20 12:36:01 stdout: 121 packages are looking for funding run
npm fund for details
Maybe I need to use a different npm version?Are u using nvm?
GitHub
FAQ: Frequently Asked Questions
An implementation of a Signal K central server for boats. - SignalK/signalk-server
Yes, I was (somehow) using nvm. After deleting it and reinstalling Signal K from scracht I was able to run the latest version.
Thank you Teppo!!!
I have the same message. (Rpi 5, open plotter 4). Is it really worth updating to 2.15.1 as life is getting a little short and I really do not want to install from scratch signal k again. And then have to set up everything again.
What message are you seeing?
It just says that it has updated and to restart. I restart and I am back to the 2.14.0 version.
I followed the instructions on the signal k FAQ page and it made no difference.
That is what I see when I try to reinstall signal K from the instructions in the FAQ. I have also tried to reinstall Signal K server from the Openplotter function. This didn't work either
ok! can u please check if the directory with the -1to... ending exists? and if you try to update one more time from the Admin UI is there anything in the server's log that looks like the same thing?
afaik these ENOTEMPTY errors are caused by an earlier install attempt that left temporary files. for the life of me i don't understand how there's no npm official way for dealing with these
Yes the -1to directory exists.
try removing that
Ok. I delete the whole directory.