After a few hours, MM or Raspberry stops responding

bmadeira

Hello, I’ve installed several weeks ago MM 2.6.x on a Pi 3 B+ and had it on tests several days in a row without problems. I also implemented the MMM-PIR-Sensor with a RCWL-0516 (radar sensor) for disconnecting the monitor and it worked like a charm.
When I finally installed it on the wood Frame, hung it to the wall, upgraded to 2.7.0, added more modules and something weird started to happen: after several hours being on, I noticed two occurrences:

1st - the screen was off, when I approached it the sensor would send the signal for the MMM-PIR-sensor module turn on the monitor, but it appeared on but black, with the RB Pi responding to ping and ssh. When I hit F11, Chromium would show in window mode but without information. When I restarted the MM services (pm2 restart mm), everything is ok for a few hours.

2nd - the screen is off (could not detect connecition), approaching doesn’t turn on the monitor and nothing responds (keyboard, ping, etc). I do a power cycle and everything is ok for a few hours.

This only started to happen after I installed it on the frame, updated to 2.7.0 and installed some additional modules. Did anyone else had this kind of behaviour? How can I debug this?

Here are the modules I have installed:

MMM-AirQuality
MMM-Globe
MMM-HASS
MMM-ImageSlideshow
MMM-NetworkScanner
MMM-PIR-Sensor
MMM-Remote-Control
MMM-Tools
MMM-WorldTides
MMM-pihole-stats
octomirror-module

Best regards,

Bruno

bmadeira

Also I fond this on “pm2 logs mm”:

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 | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | ERROR! Could not find main module js file for .AppleDouble
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 | ERROR! Could not find main module js file for .AppleDouble
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.

Regards,

Bruno

bhepler

My first approach in debugging this would be to remove all of the modules and just go with a couple core ones to let you know that the mirror is functioning.

Back up your config.js file and use the config.js.sample from the repository. Strip out the weather modules, calendar module and newreader modules. Leave the clock & compliments. Run the mirror like that for a day to see if you still lose the mirror.

If it is stable with only those modules, add your PIR-Sensor module. Test that it controls the monitor correctly. Then run it like that for a day or so and see if the problem returns.

At that point, it should help you establish roughly where the problem lies.

sdetweil

@bhepler and u don’t have to remove anything from config… just add

"disabled" : true,

to turn off each module
make it false to turn a module back on

bmadeira

I found out that it seams the MMM-HASS and MMM-pihole-stats are causing the problems.
Whe I use the “disabled” : true", the mirror works for hours without any problems, but when I load the modules, the chromium browser turns black (like without any info) until I restart MM.
Any ideas?

Regards, Bruno

bmadeira

Hello,

After all, disabling MMM-HASS and MMM-pihole-stats did not solve the problem.
Even after a fresh install without this modules, it still hapens. The strange thing is that if i access the MagicMirror via HTTP from my computer, the we page loads correctly with all the items, but on the mirror/Pi it’s a black page, only displaying correctly after a MM service restart.
Could it be something with the MM browser?

Best regards, Bruno

Maybe this could be stupid question but Have you considered screensaver or energy saving issue?

bmadeira

@Sean I’ve followed the guide to disable the screen saver and the power management for the Pi, so this shouldn’t be an issue.

dazza120

@bmadeira it’s the pi running out of memory, not sure what is using all of it, I use cronjob to restart mm every 12 hours

UNSOLVED After a few hours, MM or Raspberry stops responding