It seems to be working fine again here… I don’t have any idea what has happened. But I will keep an eye out for further problems.

Hey,

a few days ago I upgraded to 2.5.0. I don’t know if it’s correlated, but I can’t exclude…
This morning I noticed my Mirror showing the desktop and not the mirror interface. It seems to be in a restarting loop, but I don’t see any reason why. I also tried to start it manually without pm2, but I just said Launching application.and returned to the console. Has anyone an idea how to find the cause?

Regards,
Anduril

pi@Spieglein:~ $ pm2 logs MagicMirror
[TAILING] Tailing last 15 lines for [MagicMirror] process (change the value with --lines option)
/home/pi/.pm2/logs/MagicMirror-out.log last 15 lines:
0|MagicMir | No helper found for module: MMM-doomsDay.
0|MagicMir | No helper found for module: MMM-forecast-io.
0|MagicMir | All module helpers loaded.
0|MagicMir | Starting server on port 8080 ...
0|MagicMir | You're using a full whitelist configuration to allow for all IPs
0|MagicMir | Server started ...
0|MagicMir | Connecting socket for: MMM-Remote-Control
0|MagicMir | Starting node helper for: MMM-Remote-Control
0|MagicMir | Connecting socket for: updatenotification
0|MagicMir | Connecting socket for: MMM-DVB
0|MagicMir | Starting module helper: MMM-DVB
0|MagicMir | Connecting socket for: calendar
0|MagicMir | Starting node helper for: calendar
0|MagicMir | Sockets connected & modules started ...
0|MagicMir | Launching application.

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information

pi@Spieglein:~/MagicMirror $ DISPLAY=:0 npm start dev

> magicmirror@2.5.0 start /home/pi/MagicMirror
> sh run-start.sh "dev"

Starting MagicMirror: v2.5.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: updatenotification
Initializing new module helper ...
Module helper loaded: MMM-DVB
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: compliments.
No helper found for module: MMM-doomsDay.
No helper found for module: MMM-forecast-io.
All module helpers loaded.
Starting server on port 8080 ...
You're using a full whitelist configuration to allow for all IPs
Server started ...
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: updatenotification
Connecting socket for: MMM-DVB
Starting module helper: MMM-DVB
Connecting socket for: calendar
Starting node helper for: calendar
Sockets connected & modules started ...
Launching application.
pi@Spieglein:~/MagicMirror $

some additional information: when running fine, pm2 seems to be the parent process:

  612 ?        Ssl    0:34 PM2 v3.1.3: God Daemon (/home/pi/.pm2)
  797 ?        Ss     0:00  \_ bash /home/pi/MagicMirror/installers/mm.sh
  799 ?        Sl     0:04      \_ npm
  946 ?        S      0:00          \_ sh -c sh run-start.sh
  947 ?        S      0:00              \_ sh run-start.sh
  949 ?        Sl     0:01                  \_ node /home/pi/MagicMirror/node_modules/.bin/electron js/electron.js
  958 ?        Sl     8:43                      \_ /home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js
  960 ?        S      0:00                          \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=zygote --no-sandbox
 1088 ?        Sl     4:50                          |   \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=renderer --no-sandbox --service-pipe-token=756DBD94487A30A46611ABEDF5588C31 --
 1087 ?        Sl     0:05                          \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9

but as soon as I stop MM in pm2 I see 2 different parent processes:

  612 ?        Ssl    0:34 PM2 v3.1.3: God Daemon (/home/pi/.pm2)
  958 ?        Sl     8:45 /home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js
  960 ?        S      0:00  \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=zygote --no-sandbox
 1088 ?        Sl     4:51  |   \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=renderer --no-sandbox --service-pipe-token=756DBD94487A30A46611ABEDF5588C31 --lang=de --app-path=/home
 1087 ?        Sl     0:05  \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-exte

so pm2 is still running, but left the electron browser also running now without a parent.

Hey there,

always after restarting I get an error EADDRINUSE. To investigate I looked at `netstat -lptn’ to see which program uses what port.
At startup I see only one line coresponding to MM which is this:

tcp        1      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      1019/electron.js

But when I use `pm2 stop mm’ I still see this line. I also tried to change the port for each restart with the result of having multiple instances of electron listening on the coresponding ports.
When starting it manually without pm2 in the console it opens and closes correctly after quitting.
Has anyone a guess how to solve this?

Hi @Mykle1,
great module! Is it also possible to show only the days left? It’s kind of useless to show for example seconds until a specific date (vacation, birthday,…)
Maybe you could add an option in the config to display only dd or dd:hh or dd:hh:mm.

I use crontab and added
@reboot tvservice -o to deactivate hdmi output on start. You can activate it on demand (as I do) or maybe after 60 seconds

well something strange I noticed… (don’t know if that’s related)
My Desktop used to be PIXEL I think (this nice road wallpaper and menu bars at the top. Now it looks like it is running Openbox. I don’t know how this happened, but it was not intended by me. Was that changed in the newest version because of my upgrades?

I did use CTRL + ALT + RIGHT or LEFT, but that didn’t helped either. Only change was that in the middle of the VNC-session was a small blue notification saying Desktop 1 so I suppose I have only one virtual desktop active.

trying your script or chvt 6 [or 7] manually does result in this error:

Konnte keinen Dateideskriptor finden, der auf die Konsole verweist.

The monitor is turning on correctly and I can see the background dark grey in the mirror, but it simply does not show the mirror. Maybe it somehow has multiple desktops defined and just showing the wrong on hdmi output…

well that didn’t worked. I still only see a black monitor. I did also reinstall MagicMirror and connected to it via VNC. Strange thing is that I can see my MM on my VNC client, but not on my monitor. I didn’t even thought this would be possible…