Signalk on Pi Zero 2w install hangs.
Ah.. Here you all are. I wondered where everyone had got to. I was wandering around the github discussion thinking it was awfully quiet and everyone is here having a party!
Anyway:
Hello
I have been trying to install Signal K on a pi zero 2, just for testing and as an experiment. I have got to the actual installation part (sudo npm install -g signalk-server) and it appears to have hung my Pi zero 2. I can ping the Pi but get no response from my SSH sessions. The CPU seems to max out at 100% and no mouse response if I connect a screen/mouse to the HDMI output. I have left it like that for several hours with no progress. I am running the installation in a screen. Any thoughts or options?
The last output from the installation is:
(node:2245) ExperimentalWarning: CommonJS module /usr/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /usr/lib/node_modules/npm/node_modules/supports-color/index.js using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use node --trace-warnings ...to show where the warning was created) ⠙
The progress dots seem not to have changed either.
Anyway:
Hello
I have been trying to install Signal K on a pi zero 2, just for testing and as an experiment. I have got to the actual installation part (sudo npm install -g signalk-server) and it appears to have hung my Pi zero 2. I can ping the Pi but get no response from my SSH sessions. The CPU seems to max out at 100% and no mouse response if I connect a screen/mouse to the HDMI output. I have left it like that for several hours with no progress. I am running the installation in a screen. Any thoughts or options?
The last output from the installation is:
(node:2245) ExperimentalWarning: CommonJS module /usr/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /usr/lib/node_modules/npm/node_modules/supports-color/index.js using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use node --trace-warnings ...to show where the warning was created) ⠙
The progress dots seem not to have changed either.
