SK
Signal K3mo ago
Bram

No NMEA2000 data anymore

I've upgraded to the latest signalk server and suddenly i am not receiving and NMEA2000 data anymore. It fails with the message: Cannot read properties of undefined (reading 'createRawChannelWithOptions'). This could be coincidence, i've also installed mqtt-gw plugin (now disabled). I am using a Sailhat (SH-RPI) to receive the data. It was receiving fine two weeks ago, i haven't made any changes to the NMEA2000 connection settings. I'm running node v22.15.0 (saw the other posts about 2.14.0). Downgrade to 2.13.5 failed with
pi@tjielpi3b:~ $ sudo npm install -g [email protected]
npm error code ENOTEMPTY
npm error syscall rename
npm error path /usr/lib/node_modules/signalk-server
npm error dest /usr/lib/node_modules/.signalk-server-1toVL4zJ
npm error errno -39
npm error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/signalk-server' -> '/usr/lib/node_modules/.signalk-server-1toVL4zJ'
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-06-21T13_59_00_551Z-debug-0.log
pi@tjielpi3b:~ $ node -v
v22.15.0
pi@tjielpi3b:~ $ sudo npm install -g [email protected]
npm error code ENOTEMPTY
npm error syscall rename
npm error path /usr/lib/node_modules/signalk-server
npm error dest /usr/lib/node_modules/.signalk-server-1toVL4zJ
npm error errno -39
npm error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/signalk-server' -> '/usr/lib/node_modules/.signalk-server-1toVL4zJ'
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-06-21T13_59_00_551Z-debug-0.log
pi@tjielpi3b:~ $ node -v
v22.15.0
Any thoughts really appreciated. thx
20 Replies
Hannes
Hannes3mo ago
Scott Bender
Scott Bender3mo ago
Remove that directory in the error message The .signalk-server.1toV….. You might want to try 2.14 again. That issue you’re having happens when something terrible goes wrong during install
Bram
BramOP3mo ago
Thx. Removed the folder. You mean reinstall 2.14 or just reboot?
Scott Bender
Scott Bender3mo ago
Reinstall 2.14
Bram
BramOP3mo ago
Ok, will lay course close to land to stay in 4G range 😉
Hannes
Hannes3mo ago
i needed to uninstall and install again. anything else did not work dont forget the backup 😉
Bram
BramOP3mo ago
How do i uninstall? good reminder just remove node_modules?
Hannes
Hannes3mo ago
npm uninstall signalk-server
Hannes
Hannes3mo ago
once again run npm install signalk-server maybe with sudo, depending on your system.
Scott Bender
Scott Bender3mo ago
Yes. Need sudo. and it’s “sudo npm install -g signalk-server”
Bram
BramOP3mo ago
Thanks a lot working on it... Will this kill the installation process? I guess my 4G is flaky at the moment
pi@tjielpi3b:~ $ 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.
⠋Read from remote host 192.168.9.1: Operation timed out
Connection to 192.168.9.1 closed.
client_loop: send disconnect: Broken pipe
pi@tjielpi3b:~ $ 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.
⠋Read from remote host 192.168.9.1: Operation timed out
Connection to 192.168.9.1 closed.
client_loop: send disconnect: Broken pipe
Would there be a way for npm to first download signalk to the pi and than install from that? I guess that will be difficult with dependencies though
Scott Bender
Scott Bender3mo ago
Yeah, not that I know of
Bram
BramOP3mo ago
Pfff again disconnected... will try in the harbour. Thx so far Will try using vnc, because i think it is the connection with the pi that might be the problem. In vnc the npm process would keep running.
Scott Bender
Scott Bender3mo ago
you coud also run it in the background
Bram
BramOP3mo ago
True with & at the end wasn't it?
Scott Bender
Scott Bender3mo ago
need to redirect the output, so sudo npm install -g signalk-server > /tmp/npm.out & 2>&1
Bram
BramOP3mo ago
thx will try that the next time. VNC failed for some reason. Tried running it in the bckground. After the connection was reset again i couldn't find /tmp/npm.out (i could before it disconnected). Though with top i see an active node process running, so i guess its doing something. Strange
Scott Bender
Scott Bender3mo ago
Might be something to do with sudo. Not sure I ever tried that before…
Bram
BramOP3mo ago
Had to reinstall two more times but now it works. Thx again!

Did you find this page helpful?