The Z2W feels a very lopsided device (wrt cpu vs memory). Conversely, on a Pi3, there is 1GB of memory to feed the four build threads. I agree that this looks like a Z2W problem, on a Z1W there is only one core and therefore one build thread that can be managed. HTOP with npm in 'foreground-script' mode showing single build process operating just within limits of available memory/swap: HTOP with npm in 'normal' mode showing multiple build processes and swap space thrashing i.e. With the foreground-scripts enabled then the pi will only start a single build process and that can operate within the 512MB memory. responding to pings) but there isn't enough spare cycles to deal with a new SSH request. During this period, the pi is still 'operating' (e.g. Looks like everything grinds to a halt and eventually times out. The pi then thrashes between the four build processes spending more time swapping out memory than actually progressing the build. But the Z2W only has 512MB of memory so that quickly gets exhausted along with available swap space. For what it is worth, looks like a deeper root-cause.īasically, npm sees that the Z2W has four cores and wants to run a build process on each. I managed to replicate this on one of my Zero 2 Ws. When you get into the 'hung' situation, are you still able to ping the pi and even ssh back in to see if the npm command is still running ? If the pi is still running but the npm command is not then that would lend weight to a 'keep-alive' problem.īeta Was this translation helpful? Give feedback. You could check if your client has an 'SSH Keep Alive' option and try setting that ?

Running with foreground-scripts enabled could be creating enough traffic to avoid this. This will also terminate all processes running in that shell including the npm command. The newer npm command runs the scripts in the background and swallows the output by default.Ĭould be that the pi is terminating the ssh session thinking it is inactive as the regular command will go for some time without generating output during the build phase.

In previous versions of npm, the build scripts would be run in the foreground and the associated output sent to the screen. So once npm has downloaded mathjs then it starts to build a bunch of modules that take quite a bit of time.

Room assistant pi zero