@sdetweil – OK, thanks for the effort!
Read the statement by Michael Teeuw here.
Posts
-
RE: MM won't start after upgrading to 2.29.0
-
RE: MM won't start after upgrading to 2.29.0
@sdetweil – Humm, I see what you mean. unfortunately this isn’t running on an actual Raspberry Pi so I don’t have that utility available to me.
It’s a VM running Ubuntu 23.10. If you can point me in the right direction, I’d be willing to give it a shot.
-
RE: MM won't start after upgrading to 2.29.0
@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?
-
RE: MM won't start after upgrading to 2.29.0
@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.
-
RE: MM won't start after upgrading to 2.29.0
@sdetweil – I sent you an email with extended pm2 logs output.
-
RE: MM won't start after upgrading to 2.29.0
@sdetweil – I can do that. Would you want it here or email?
-
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 -
RE: MMM-DynamicWeather Failed getting api: 401
@sdetweil – I intended to try the above, but the MagicMirror indicated it was due for an update, so I ran your update script first… Now it won’t run.
Rather than hijacking this thread, I will put the particulars in a new thread.
i just didn’t want if to look like I left this one hanging out there…
-
RE: MMM-DynamicWeather Failed getting api: 401
@sdetweil – Thanks, Sam.
If I want to try this, can I just do it in the module folder now, or do I go back in there first and undo the edits I performed manually? I’m not clear on whether it does or doesn’t make a difference.
-
RE: MMM-DynamicWeather Failed getting api: 401
@wishmaster270 --Thanks! I appreciate the effort, but it didn’t work for me. I will wait for your PR to go thru…