After update 2.23.0 crash

[sdetweil]

@swvalenti can u post the ~/MagicMirror/installers/upgrade.log

[swvalenti]

@sdetweil Here ya go
https://drive.google.com/file/d/1L5ORoBJlEV6lYSLzJC7VhHM1S1P-jRWy/view?usp=share_link

[sdetweil]

@swvalenti ok , because you had already done upgrade on this instance. apply doesnt do anything

do force
at the end instead of apply

[swvalenti]

@sdetweil You are the man worked like a charm. Only thing I noticed when running on windows “alt” does not bring the toolbar up in order to quit MM. Did anything change?

[sdetweil]

@swvalenti alt-spacebar, or ctrl-m

ctrl-q to quit, if not using pm2.
pm2 will just restart it

[swvalenti]

@sdetweil ctrl m worked thanks Sam!

[JoeFranz]

Same here, error after Update :-(
@sdetweil Update with your script

(Use electron --trace-warnings ... to show where the warning was created)
[05.04.2023 07:02.12.571] [ERROR] (node:4893) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
[4932:0405/070214.077646:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[4962:0405/070214.418104:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

[JoeFranz]

I ran “electron-rebuild”, now it works again :-)

[sdetweil]

@JoeFranz on what module?

[JoeFranz]

@sdetweil MMM-PIR-Sensor

[Wenike]

@sdetweil By chance, do you know of a command I can run to kill any running Node processes? I’m trying to run your upgrade script and its unable to upgrade Node because a process is already running. Googling gives me code to use within an application but that doesn’t seem like it’ll work from the CLI.

doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v16.13.1
Installed Node version: v10.24.1
Node should be upgraded.
A Node process is currently running. Can't upgrade.
Please quit all Node processes and restart the update.
running process(s) are
pi 881 879 0 09:05 ? 00:00:00 node ./node_modules/.bin/electron js/electron.js

[mumblebaj]

@JerryP Always use Sam’s update script. I used it last night and updated from 2.21.0 to 2.23.0 no issues. Often modules with a package.json requires an npm install in that folder and the upgrade script takes care of all of that.

[sdetweil]

@Wenike do this

from a terminal window

ps -ef | grep node

this will show you the node processes running and parms to what they are running (file path)

if all looks understandable and u can’t terminate them thru app shutdown (pm2 stop all will stop all.managed apps, mm included), do

ps -ef | grep node | awk '{ print $2 }' | xargs kill -9

this will hard kill all the node processes

[sdetweil]

@JoeFranz

the script does a new npm install in modules that have a package.json

but I know the post install process is wrong for this module

my fork fixes that
https://github.com/sdetweil/MMM-PIR-Sensor

[Wenike]

@sdetweil Perfect, fixed it. Thanks!

[sdetweil]

@JerryP said in After update 2.23.0 crash:

sudo git pull

just one more thing

NEVER use sudo with MM no need for it.
all it does is lead to trouble

[hrjmsh]

@sdetweil Thank you very much. Had the same error (cannot find module envsub) on updating the MagicMirror to the new version and this step (rm -rf node_modules and then npm install again) solved the issue for me.

[sdetweil]

@hrjmsh you should use my upgrade script

[hrjmsh]

@sdetweil I did, both with and without changes applied. Unfortunately, it didn’t work for me. The only thing that worked was the solution you provided by removing the node_modules and then reinstalling npm.

[sdetweil]

@hrjmsh can u send me the MagicMirror/installers/upgrade.log

same userid at gmail

never seen this problem