2.32.0 to 2.33.0 fails due to "some node app still running"

Martensite

Hi,
I am new to the Raspberry Pi and there are a lot of things that I am unfamiliar with. I have a Raspberry Pi 5 and I managed to get the MagicMirror up and running for the first time using a manual installation.

I am now getting notifications saying I should update to version 2.33.0 and I am trying to do so by using the script from sdetweil

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"

The output from this is

bash: line 148: cd: /home/usr/MagicMirror/installers: No such file or directory
update log will be in /home/usr/MagicMirror/upgrade.log

doing test run = true, NO updates will be applied!

Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.18.0
Installed Node version: v22.18.0
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.2
Installed npm version: V10.9.3
No npm upgrade necessary.

saving custom.css

upgrading from version 2.32.0 to 2.33.0
some node app still running, please shutdown MagicMirror and restart

I have tried several times to reboot the Pi. I have used ps aux | grep MagicMirror to kill any process related to it. This results in
4768 0.0 0.0 7520 1812 pts/4 S+ 22:23 0:00 grep --color=auto MagicMirror
and the PID changes whenever I try to kill the process.

I have tried both the apply and force command with the upgrade script, but to no luck.

Any help on this issue? What could be the “node app” still running that prevents this from running?

EDIT:
Writing this acted as rubber-ducking and my final resort was to close my remote ssh-connection and manually type in the command on my touch-screen.
That seemed to do it. Anyone knows how to be able to do this through ssh?

sdetweil

@Martensite I fixed the upgrade script if you didn’t use the installer script… for missing installers folder

now, some NODE app, not MM app

ps -ef | grep node

there is only ONE node lib being used so, ANY app (discord, visual studio)…

sdetweil

@Martensite the ssh session is not node…I do EVERYTHING over ssh…(well, I LOOK at the screen behind me!)

send me the installers/upgrade.log

same userid as here at gmail

cweinhofer

@sdetweil said in 2.32.0 to 2.33.0 fails due to "some node app still running":

ps -ef | grep node

Thanks for jumping in here. This command was really helpful. I wonder if I might make sense to change the error message from
“some node app still running, please shutdown MagicMirror and restart”
to
“some node app still running, run ps -ef | grep node to see running node apps and shut them down before continuing”

For others who might read this later, in my case NoMachine was the culprit.

sdetweil

@cweinhofer thanks…

I added a message and then
the list of processes from the ps -ef , which I already had

							echo some node app still running, please shutdown those apps, maybe MagicMirror, and restart
							echo here is a list of those processes
							echo $mline

if MM was running under pm2, I already stopped it…