This morning, the mirror was dark again.
This is the memory output
pi@raspberrypi_1:~ $ free -m
total used free shared buff/cache available
Mem: 925 220 391 1 313 653
Swap: 1023 118 905
Edit: The mirror was stopped and started and after 15min he was dark again …
@sdetweil said in MMM-BackgroundSlideshow:
free -m
Command will show memory usage
pi@raspberrypi_1:~ $ free -m
total used free shared buff/cache available
Mem: 925 218 404 1 302 657
Swap: 1023 111 912
@sdetweil said in MMM-BackgroundSlideshow:
and rebooted after changing swap file
I have now reboot the mirror …
Now I thought it was solved, but after about 1 hour the screen was black again. I had to stop the MagicMirror with pm2 stop 0 and then restart it with pm2 start 0.
I also changed the size from 100 to 1024.
What else can it be?
sudo dphys-swapfile swapoff
sudo nano /etc/dphys-swapfile / (changed size 1024)
sudo dphys-swapfile swapon
Here are the logs from /home/pi/.pm2/logs/mm-out.log
> magicmirror@2.8.0 start /home/pi/MagicMirror
> sh run-start.sh
Starting MagicMirror: v2.8.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
Initializing new module helper ...
Module helper loaded: MMM-WatchDog
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: MMM-SystemStats
Initializing new module helper ...
Module helper loaded: newsfeed
Initializing new module helper ...
Module helper loaded: MMM-MyCommute
Initializing new module helper ...
Module helper loaded: MMM-GoogleMapsTraffic
Initializing new module helper ...
Module helper loaded: MMM-DarkSkyForecast
Initializing new module helper ...
Module helper loaded: MMM-MyCalendar
All module helpers loaded.
Starting server on port 8080 ...
Server started ...
Connecting socket for: updatenotification
Connecting socket for: MMM-WatchDog
Starting module helper: MMM-WatchDog
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-SystemStats
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-MyCommute
====================== Starting node_helper for module [MMM-MyCommute]
Connecting socket for: MMM-GoogleMapsTraffic
Starting node_helper for module: MMM-GoogleMapsTraffic
Connecting socket for: MMM-DarkSkyForecast
====================== Starting node_helper for module [MMM-DarkSkyForecast]
Connecting socket for: MMM-MyCalendar
Starting node helper for: MMM-MyCalendar
Sockets connected & modules started ...
Launching application.
Create new news fetcher for url: https://api.20min.ch/rss/view/1 - Interval: 300000
WatchDog started. Maximum timeout: 10s.
Create new news fetcher for url: https://api.20min.ch/rss/view/67 - Interval: 300000
Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: 'standard' }
Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/XXXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/basic.ics - Interval: 300000
And here are the logs from /home/pi/.pm2/logs/mm-error.log
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
ATTENTION: default value of option force_s3tc_enable overridden by environment.
pi@raspberrypi3:~ $ pm2 reloadLogs
Reloading all logs...
All logs reloaded
pi@raspberrypi3:~ $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2 | [2019-09-07T14:54:18.048Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.145Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.224Z] PM2 log: App [mm] with id [0] and pid [17526], exited with code [0] via signal [SIGINT]
PM2 | [2019-09-07T14:54:18.245Z] PM2 log: pid=17526 msg=process killed
PM2 | [2019-09-07T14:54:27.372Z] PM2 log: Starting execution sequence in -fork mode- for app name:mm id:0
PM2 | [2019-09-07T14:54:27.383Z] PM2 log: App name:mm id:0 online
PM2 | [2019-09-07T15:18:47.949Z] PM2 log: Process 0 in a stopped status, starting it
PM2 | [2019-09-07T15:18:47.954Z] PM2 log: Stopping app:mm id:0
PM2 | [2019-09-07T15:18:48.369Z] PM2 log: pid=597 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T15:18:48.372Z] PM2 log: App [mm] with id [0] and pid [597], exited with code [0] via signal [SIGINT]
PM2 | [2019-09-07T15:18:48.469Z] PM2 log: pid=597 msg=process killed
PM2 | [2019-09-07T15:18:48.473Z] PM2 log: Starting execution sequence in -fork mode- for app name:mm id:0
PM2 | [2019-09-07T15:18:48.493Z] PM2 log: App name:mm id:0 online
PM2 | [2019-09-07T16:10:56.689Z] PM2 log: Reloading logs...
PM2 | [2019-09-07T16:10:56.693Z] PM2 log: Reloading logs for process id 0
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm | Connecting socket for: MMM-MyCommute
0|mm | ====================== Starting node_helper for module [MMM-MyCommute]
0|mm | Connecting socket for: MMM-GoogleMapsTraffic
0|mm | Starting node_helper for module: MMM-GoogleMapsTraffic
0|mm | Connecting socket for: MMM-DarkSkyForecast
0|mm | ====================== Starting node_helper for module [MMM-DarkSkyForecast]
0|mm | Connecting socket for: MMM-MyCalendar
0|mm | Starting node helper for: MMM-MyCalendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new news fetcher for url: https://api.20min.ch/rss/view/1 - Interval: 300000
0|mm | WatchDog started. Maximum timeout: 10s.
0|mm | Create new news fetcher for url: https://api.20min.ch/rss/view/67 - Interval: 300000
0|mm | Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: 'standard' }
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/XXXXXXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/basic.ics - Interval: 300000
That would be my logs
pi@raspberrypi3:~ $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lin es option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2 | [2019-09-07T14:54:17.446Z] PM2 log: Stopping app:mm id:0
PM2 | [2019-09-07T14:54:17.944Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.048Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.145Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.224Z] PM2 log: App [mm] with id [0] and pid [1 7526], exited with code [0] via signal [SIGINT]
PM2 | [2019-09-07T14:54:18.245Z] PM2 log: pid=17526 msg=process killed
PM2 | [2019-09-07T14:54:27.372Z] PM2 log: Starting execution sequence in -fork mode- for app name:mm id:0
PM2 | [2019-09-07T14:54:27.383Z] PM2 log: App name:mm id:0 online
PM2 | [2019-09-07T15:18:47.949Z] PM2 log: Process 0 in a stopped status, starting it
PM2 | [2019-09-07T15:18:47.954Z] PM2 log: Stopping app:mm id:0
PM2 | [2019-09-07T15:18:48.369Z] PM2 log: pid=597 msg=failed to kill - re trying in 100ms
PM2 | [2019-09-07T15:18:48.372Z] PM2 log: App [mm] with id [0] and pid [5 97], exited with code [0] via signal [SIGINT]
PM2 | [2019-09-07T15:18:48.469Z] PM2 log: pid=597 msg=process killed
PM2 | [2019-09-07T15:18:48.473Z] PM2 log: Starting execution sequence in -fork mode- for app name:mm id:0
PM2 | [2019-09-07T15:18:48.493Z] PM2 log: App name:mm id:0 online
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm | Connecting socket for: MMM-MyCommute
0|mm | ====================== Starting node_helper for module [MMM-MyCommu te]
0|mm | Connecting socket for: MMM-GoogleMapsTraffic
0|mm | Starting node_helper for module: MMM-GoogleMapsTraffic
0|mm | Connecting socket for: MMM-DarkSkyForecast
0|mm | ====================== Starting node_helper for module [MMM-DarkSky Forecast]
0|mm | Connecting socket for: MMM-MyCalendar
0|mm | Starting node helper for: MMM-MyCalendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new news fetcher for url: https://api.20min.ch/rss/view/1 - Interval: 300000
0|mm | WatchDog started. Maximum timeout: 10s.
0|mm | Create new news fetcher for url: https://api.20min.ch/rss/view/67 - Interval: 300000
0|mm | Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC- GET payload: { style: 'standard' }
0|mm | Create new calendar fetcher for url: https://calendar.google.com/ca lendar/ical/XXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/b asic.ics - Interval: 300000
Ok, thanks for the explanation 
I can understand that reasonably. You are a genius
@Stoffbeuteluwe ok, aber was muss ich dort eingeben? Keine Ahnung…
Ich habe die 12% Variante genommen, passt für mich. Aber am besten ist wirklich, man geht mit einem Handy vorbei und testet jedes Glas
The module once worked on the PI. Do I have to do something now @sdetweil?