Read the statement by Michael Teeuw here.
MM won't start after upgrading to 2.29.0
-
@sdetweil and others – I ran Sam Detweil’s update script. Trial mode didn’t show anything worrying, so I re-ran it and applied the changes. I was running pm2 logs in another terminal window and saw it stall…
I’ve rebooted the machine, and it is stuck in a loop now. What looks like the relevant section of the logs is pasted below. This repeats over and over…
@sdetweil - I sent you the upgrade log by email.
0|MagicMirror | [2024-10-29 15:16:06.807] [LOG] Starting node helper for: newsfeed 0|MagicMirror | [2024-10-29 15:16:06.807] [LOG] Connecting socket for: MMM-DynamicWeather 0|MagicMirror | [2024-10-29 15:16:06.808] [LOG] Sockets connected & modules started ... 0|MagicMirror | Authorization required, but no authorization protocol specified 0|MagicMirror | [123146:1029/151606.810294:ERROR:ozone_platform_x11.cc(245)] Missing X server or $DISPLAY 0|MagicMirror | [123146:1029/151606.810429:ERROR:env.cc(258)] The platform failed to initialize. Exiting. 0|MagicMirror | /home/al/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV PM2 | App [MagicMirror:0] exited with code [1] via signal [SIGINT] PM2 | App [MagicMirror:0] starting in -fork mode- PM2 | App [MagicMirror:0] online 0|MagicMirror | > magicmirror@2.29.0 start 0|MagicMirror | > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js 0|MagicMirror | [2024-10-29 15:16:13.638] [LOG] Starting MagicMirror: v2.29.0 0|MagicMirror | [2024-10-29 15:16:13.664] [LOG] Loading config ... 0|MagicMirror | [2024-10-29 15:16:13.666] [LOG] config template file not exists, no envsubst 0|MagicMirror | [2024-10-29 15:16:14.116] [INFO] Checking config file /home/al/MagicMirror/config/config.js ... 0|MagicMirror | [2024-10-29 15:16:14.230] [INFO] Your configuration file doesn't contain syntax errors :) 0|MagicMirror | [2024-10-29 15:16:14.231] [INFO] Checking modules structure configuration ... 0|MagicMirror | [2024-10-29 15:16:14.329] [INFO] Your modules structure configuration doesn't contain errors :) 0|MagicMirror | [2024-10-29 15:16:14.331] [LOG] Loading module helpers ... 0|MagicMirro -
@JohnGalt can you show me more of the output? after starting Application,
there is a dump of system data
like this2024-10-29 17:55:20.819] [INFO] System information: ### SYSTEM: manufacturer: ; model: ; virtual: false ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.6.51+rpt-rpi-v8 ### VERSIONS: electron: 31.7.3; used node: 20.18.0; installed node: 20.9.0; npm: 10.1.0; pm2: 5.4.2 ### OTHER: timeZone: America/Chicago; ELECTRON_ENABLE_GPU: undefined -
@JohnGalt this is a pm2 problem…
SOMEtimes we can fix it like this
pm2 stop all pm2 delete MagicMirror pm2 save -f sudo npm remove pm2 -g # I edited a typo herethen run my fixuppm2.sh script
(same place as my install script, near the bottom of the page -
@sdetweil – I can do that. Would you want it here or email?
-
@sdetweil – I sent you an email with extended pm2 logs output.
-
-
S sdetweil referenced this topic on
-
@sdetweil – I wasn’t sure you [still] wanted me to do that before you had a chance to see the extended pm2 logs outputs. I will do it now and get back to you.
-
@JohnGalt the log show me the wayland/pm2 confusion
i opened a pm2 issue about this back in the early spring
-
@sdetweil – I did the pm2 work you asked for, and still have the same results.
As this is a dev instance it’s not as critical as it might be for the regular [production] instance we use to get actual information. Am I better off just re-installing Magic Mirror from scratch on this machine?
-
@JohnGalt its not MagicMirror its pm2 talking to the display manager
you could use raspi-config to set the display manager back to x11
without doing anything else
