Error with CAN/NMEA2000 after upgrade to 2.17.2
Logfile in attachment
Thank you in advance for making it work again and for eventually implementing quality assurance in SignalK.
6 Replies
is this another case of https://github.com/SignalK/signalk-server/issues/1870
GitHub
Socketcan missing after server update · Issue #1870 · SignalK/sig...
candump can0 | candumpanalyzerjs confirms the can0 network is up and running. Signalk shows 0 delta/second since the upgrade. The only errors I see in the logs are: Jan 28 10:58:08 [signalk-to-nmea...
@Teppo Kurki Thank you for pointing in right direction. Yes, it's same issue. Fix ist trivial, but cause for non-technical users will be critical. I don't know how this can happen, it seems to depend on certain combinations of node/npm/signalk.
I have tried a few:
1. arm64:
node 22.21.1 with 2.17.2 failed
2. armhf:
node 22.15.0 ( last stable. why so old, don't know) with sk 2.17.2 successfully
exactly. when you say failed do you mean that the update failed OR that your attempt at fixing it (
sudo npm install socketcan) failed?After "npm install socketcan" in /usr/lib/node_modules/signalk-server" is all ok. But per default npm do not install always "socketcan " as requirement of signalk-server
socketcan is an optional dependency because it is not supported on all platforms. Mac, Windows, etc. So if the socketcan install fails, npm ignores it and moves on. I don’t love how npm handles this,
I don’t understand how it would somewhat methodically fail with server install/update and succeed with individual install