Hannes - Got an error today with my PiCanM Boar...
Got an error today with my PiCanM Board on the Raspberry since the update to 2.14
Cannot read properties of undefined (reading 'createRawChannelWithOptions')
It is not working actually. It worked well with previous 2.13.5.
candump can0 is working fine
i updated node to v22.16.0 before.
14 Replies
i think you are facing this issue 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...
Both did not work.
Neither installing socketcan via npm within node modules, i'm getting the error:
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/typedoc-signalk-theme - Not found
npm error 404
npm error 404 'typedoc-signalk-theme@^0.3.0' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
Nor executing "npm i -g signalk-server" worked.
ah, the typedoc problem is a new one, introduced in 2.14. @Brandon Keepers i think we should just publish that to skip this type of errors - unless you have other great ideas
how did the -g version fail?
can you please try with
--only=prod option? typedoc-signalk-theme is not really needed and this should skip trying to install it"npm i -g signalk-server" is running through with few warning:
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.
npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated lodash.isequal@4.5.0: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated fstream@1.0.12: This package is no longer supported.
changed 693 packages in 1m
122 packages are looking for funding
run
npm fund for details
--only prod is ending in the same:
/usr/lib/node_modules/signalk-server $ sudo npm install socketcan --only=prod
npm warn config only Use --omit=dev to omit dev dependencies from the install.
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/typedoc-signalk-theme - Not found
npm error 404
npm error 404 'typedoc-signalk-theme@^0.3.0' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.Seems that https://github.com/SignalK/signalk-server/blob/master/packages%2Ftypedoc-theme%2Fpackage.json requires publishing.
@Hannes
FWIW … i got the same error when doing the server upgrade to 2.14. (i didnt realise that prior it needed nodejs & npm updated)
.. i subsequently did the nodejs & npm updaates, & then did a reinstall of skserver, ( which fixed the n2k interface issue - i was getting same error as yours)
& then with a reboot of Rpi .. it all seemed to come good.
I didnt need to reinstall any of my ~20 plugins (they all “just worked”)
then try
--omit=dev as it says...
the warnings you can ignoresame with omit=dev
/usr/lib/node_modules/signalk-server $ sudo npm install socketcan --omit=dev
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/typedoc-signalk-theme - Not found
npm error 404
npm error 404 'typedoc-signalk-theme@^0.3.0' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
the thing is, i updated it prior the upgrade of the server. only thing i didn't is a reboot.... maybe thats why it's struggling.
but anycase there should be a check of nodejs within installation of 2.14
multiple restarts of skserver didnt help, only when i rebooted the Pi it came good
i just uninstalled signalk-server and installed again, as @Greg Young says. It worked !
🙂
👍 👍
there already is https://github.com/SignalK/signalk-server/blob/master/bin/signalk-server#L22-L33
but there should be a check before you upgrade https://github.com/SignalK/signalk-server/pull/1135
GitHub
[WIP] feature: implement check for minimum node version for next s...
Fixes #1134
TODO
fix tests to use the new api signature
show in the UI if update requires a newer Node version
GitHub
signalk-server/bin/signalk-server at master · SignalK/signalk-server
An implementation of a Signal K central server for boats. - SignalK/signalk-server
Yep, that sounds good to me