Mirror not starting after update

sdetweil

@xIExodusIx did you use my upgrade script?

sdetweil

@chrisfr1976 can you show me the output of thew npm run install-mm

do it this way (from the MM folder of course)

cd ~/MagicMirror
npm run install-mm >somefile.txt 2>&1

then when it finishes all the output is in somefile.txt

xIExodusIx

@sdetweil
lsb_release -a shows:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm

uname -a shows:
Linux MirrorPi 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt2 (2024-10-01) aarch64 GNU/Linux

yes I used your upgrade-script with apply and also with force.

pm2 start MagicMirror will start the MM but it won’t show up!

npm start results in following errors:
[41163:1002/155017.678545:ERROR:ozone_platform_x11.cc(245)] Missing X server or $DISPLAY
[41163:1002/155017.688550:ERROR:env.cc(258)] The platform failed to initialize. Exiting.
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

sdetweil

@xIExodusIx before this morning, my upgrade script had a bug

do

cd ~/MagicMirror
ls installers

that should fail (not found)
then do

mkdir installers
curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/mm.sh >installers/mm.sh
chmod +x installers/mm.sh

sdetweil

@xIExodusIx also, if you do

cd ~/MagicMirror
npm start

does MM come up?

xIExodusIx

@sdetweil

magicmirror@2.29.0 install-mm
npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

magicmirror@2.29.0 postinstall
npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully!
"

magicmirror@2.29.0 install-vendor
echo "Installing vendor files …
" && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing vendor files …

up to date in 2s

magicmirror@2.29.0 install-fonts
echo "Installing fonts …
" && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing fonts …

up to date in 1s
MagicMirror² installation finished successfully!

magicmirror@2.29.0 prepare
[ -f node_modules/.bin/husky ] && husky || echo no husky installed.

no husky installed.

up to date in 14s

after that, nodejs is still the same: 18.19.0

xIExodusIx

@sdetweil
the installers folder is still there.
should I delete it?
or should run the script without delete the installers folder?

xIExodusIx

@sdetweil
if I do npm start

I get this error at the end:
.
.
.
[2024-10-02 16:13:22.616] [LOG] All module helpers loaded.
[2024-10-02 16:13:22.627] [LOG] Starting server on port 8181 …
[63161:1002/161323.449087:ERROR:ozone_platform_x11.cc(245)] Missing X server or $DISPLAY
[63161:1002/161323.449298:ERROR:env.cc(258)] The platform failed to initialize. Exiting.
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

sdetweil

@xIExodusIx said in Mirror not starting after update:

nodejs is still the same: 18.19.0

this version like last requires node 20 or 22 (not 21)
this is the ‘problem’

magicMirror will not upgrade nodejs… only my upgrade script will do that
npm run install-mm should have failed as there is a test for the correct node version(s)…

can you show me the part of
~/MagicMirror/installers/upgrade.log
from one of your upgrade runs?
or open an issue on my scripts repo and attached the log there
no personal info is present in the log

xIExodusIx

@sdetweil
Upgrade started - Wed Oct 2 15:47:21 CEST 2024
system is Linux MirrorPi 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt2 (2024-10-01) aarch64 GNU/Linux
user requested to force apply changes
doing test run = false
the os is PRETTY_NAME=“Debian GNU/Linux 12 (bookworm)” NAME=“Debian GNU/Linux” VERSION_ID=“12” VERSION=“12 (bookworm)” VERSION_CODENAME=bookworm ID=debian HOME_URL=“https://www.debian.org/” SUPPORT_URL=“https://www.debian.org/support” BUG_REPORT_URL=“https://bugs.debian.org/”
[0mNode currently installed. Checking version number.[0m
[0mMinimum Node version: [1mv20.9.0[0m
[0mInstalled Node version: [1mv20.9.0[0m
[96mCheck current Node installation …[0m
[0mNode currently installed. Checking version number.
[0mMinimum Node version: [1mv20.9.0[0m
[0mInstalled Node version: [1mv20.9.0[0m
[92mNo Node.js upgrade necessary.[0m
[96mCheck current NPM installation …[0m
[0mNPM currently installed. Checking version number.
[0mMinimum npm version: [1mV10.1.0[0m
[0mInstalled npm version: [1mV10.8.3[0m
[92mNo npm upgrade necessary.[0m

increasing swap space
saving custom.css
remote name = origin
upgrading from version 2.29.0 to 2.29.0
fetching latest revisions
git fetch rc=0
current branch = master
On branch master
Your branch is up to date with ‘origin/master’.

Changes not staged for commit:
(use “git add …” to update what will be committed)
(use “git restore …” to discard changes in working directory)
modified: package-lock.json
modified: package.json

Untracked files:
(use “git add …” to include in what will be committed)
core
installers/
run-start.sh
splashscreen/

no changes added to commit (use “git add” and/or “git commit -a”)
there are 2 local files that are different than the master repo

package-lock.json
package.json

save/restore files selection = y
erasing lock files
Saved working directory and index state WIP on master: 94c3c69 Release 2.29.0 (#3568)
test merge result rc=‘’ , if empty, no conflicts
executing merge, apply specified
merge result rc= 0
Already up to date.
processor architecture is aarch64
updating MagicMirror runtime, please wait

magicmirror@2.29.0 postinstall
npm run install-vendor && npm run install-fonts && echo "MagicMirrorÂ² installation finished successfully!
"

magicmirror@2.29.0 install-vendor
echo "Installing vendor files …
" && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing vendor files …

up to date in 3s

magicmirror@2.29.0 install-fonts
echo "Installing fonts …
" && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing fonts …

up to date in 1s
MagicMirrorÂ² installation finished successfully!

magicmirror@2.29.0 prepare
[ -f node_modules/.bin/husky ] && husky || echo no husky installed.

no husky installed.

added 466 packages in 35s

112 packages are looking for funding
run npm fund for details
npm install completed - Wed Oct 2 15:48:06 CEST 2024 on base
fixing sandbox permissions

Checking for modules with removed libraries
downloading dumpactivemodules script

updating dependencies for active modules with package.json files

processing for module MMM-mmpm please wait

----------------------------------

up to date, audited 1 package in 1s

found 0 vulnerabilities

processing complete for module MMM-mmpm

processing for module MMM-pages please wait

----------------------------------

up to date, audited 1 package in 1s

found 0 vulnerabilities

processing complete for module MMM-pages

processing for module MMM-FlipClock please wait

----------------------------------

added 1 package, and audited 2 packages in 5s

found 0 vulnerabilities

processing complete for module MMM-FlipClock

processing for module MMM-GoogleCalendar please wait

----------------------------------

npm warn deprecated google-p12-pem@4.0.1: Package is no longer maintained

added 52 packages, and audited 53 packages in 26s

17 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

processing complete for module MMM-GoogleCalendar

processing for module MMM-DynamicWeather please wait

----------------------------------

up to date, audited 1 package in 1s

found 0 vulnerabilities

processing complete for module MMM-DynamicWeather

processing for module MMM-Bring please wait

----------------------------------

added 3 packages, and audited 4 packages in 3s

1 package is looking for funding
run npm fund for details

1 moderate severity vulnerability

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.

processing complete for module MMM-Bring

processing for module MMM-PublicTransportHafas please wait

----------------------------------

mmm-publictransporthafas@2.1.1 prepare
[ -f node_modules/.bin/husky ] && husky || echo husky is not installed.

husky is not installed.

added 51 packages, and audited 52 packages in 9s

16 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

processing complete for module MMM-PublicTransportHafas

processing for module MMM-Autobahn please wait

----------------------------------

added 1 package, and audited 2 packages in 2s

found 0 vulnerabilities

processing complete for module MMM-Autobahn

processing for module MMM-Globe please wait

----------------------------------

up to date, audited 1 package in 1s

found 0 vulnerabilities

processing complete for module MMM-Globe

processing for module MMM-FRITZ-Box-Callmonitor-py3 please wait

----------------------------------

added 11 packages, and audited 12 packages in 5s

found 0 vulnerabilities

processing complete for module MMM-FRITZ-Box-Callmonitor-py3

processing for module MMM-Fuel please wait

----------------------------------

added 17 packages, and audited 18 packages in 4s

8 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

processing complete for module MMM-Fuel

processing for module MMM-NINA please wait

----------------------------------

up to date, audited 1 package in 1s

found 0 vulnerabilities

processing complete for module MMM-NINA

processing for module MMM-network-signal please wait

----------------------------------

added 1 package, and audited 2 packages in 4s

found 0 vulnerabilities

processing complete for module MMM-network-signal

restoring custom.css
removing git alias
we stashed a set of files that appear changed from the latest repo versions. you should review them
Upgrade ended - Wed Oct 2 15:49:22 CEST 2024