Bookworm: MM not starting

calimero

Hi,

I just did a fresh install of MM under Bookwork (full version).
If system launches to GUI I did not find any way of autostart MM in kiosk-mode browser.

MM-service is starting, but I don’t get a local MM-GUI running.

Trying this way had no success.

No change if GUI is set to Wayland or X11.

I remember an older version of MM which was just startable via PM2, npm start or service file.

If I setup boot to CLI instead of GUI, MM also does not start because of an error that the GUI is needed.

TL;DR: How can I autostart MM on a local display on a debian bookworm?

Any advices are highly appreciated!

calimero

@sdetweil

Nevermind -

my last two replys are not published yet.
Anyway - I read about a smiliar problem and tried the following:

backup MM folder
use your install-script
removed module and config-content from backup to new folder

MM starts up as intended.
No idea, what was the issue exactly, but after your installation-script-usage it works as a charm.

Thanks for support!

sdetweil

@calimero use pm2

if you had used my install script this was a choice
there is a separate script so yiu can add pm2 later
see
https://github.com/sdetweil/MagicMirror_scripts

calimero

@sdetweil Thank you for your reply.
You’re talking about this script?

Behaviour did not change after executing.

┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1 │ MagicMirror │ default │ 2.29.0 │ fork │ 3229 │ 3s │ 23 │ online │ 0% │ 2.6mb │ pi │ enabled │
│ 0 │ mm │ default │ N/A │ fork │ 3285 │ 0s │ 3 │ online │ 0% │ 2.6mb │ pi │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

pm2 log:

Do you have a further advice? Thanks in advance!

sdetweil

@calimero said in Bookworm: MM not starting:

@sdetweil Thank you for your reply.
You’re talking about this script?

Behaviour did not change after executing.

┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1 │ MagicMirror │ default │ 2.29.0 │ fork │ 3229 │ 3s │ 23 │ online │ 0% │ 2.6mb │ pi │ enabled │
│ 0 │ mm │ default │ N/A │ fork │ 3285 │ 0s │ 3 │ online │ 0% │ 2.6mb │ pi │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

pm2 log:

[ERROR] right is not defined

looks lik you have a module in a wrong position

calimero

@sdetweil Touché.

U’re absolutely right. Just removed the handy PIR-script and installed PIR-Sensor-Lite and forgot the “”. My bad.

But: Beaviour is like before. I can start the process and access the MM via Browser but it does not start on the local display.

What works is:

Browse the MM-IP from whitelistet IP. That’s nice but I’d like to have the MM just showing via autostart on the display which is attached to the PI:(

calimero

@sdetweil

Perhaps I should have named the title “MM not showing” instead of “MM not starting”.

sdetweil

@calimero if you do

pm2 stop all
cd ~/MagicMirror 
npm start

does it come up?

calimero

@sdetweil

Unfortunately not:

[…]
ozone_platform_x11.cc(245) Missing X server or $DISPLAY
env.cc(258)] The platform failed to initialize.
/home/pi/MagicMIrror/node_modules/electron/dist/electron exited with signal SIGSEGV

calimero

@sdetweil

Nevermind -

my last two replys are not published yet.
Anyway - I read about a smiliar problem and tried the following:

backup MM folder
use your install-script
removed module and config-content from backup to new folder

MM starts up as intended.
No idea, what was the issue exactly, but after your installation-script-usage it works as a charm.

Thanks for support!

sdetweil

@calimero glad you got it going.

as for your delayed posts

everyone with reputation below 2 has their posts reviewed. this to stop all the junk posts

i review every such post, and occasionally sleep! lol

please don’t double post