MagicMirror² v2.11.0 is available! For more information about this release, check out this topic.
READ THE CHANGELOG BEFORE UPDATING!

MMM-BackgroundSlideshow


  • Project Sponsor

    Sorry, it’s me again.

    One of my PI’s actually ran for months without any problems. I updated the module MMM-BackgroundSlideshow 3 days ago. Since this update, my mirror is about 10min always dunek. When I enter pm2 start mm in the console, the picture comes back. I have also run the dependency in module folder npm install, without success.

    What could be the reason for this?



  • @CyruS1337 show us pm2 logs


  • Project Sponsor

    that would be the log files

    pi@raspberrypi_1:~/MagicMirror $ 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-07T10:11:41: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:41: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
    PM2        | 2019-09-07T10:11:42: PM2 log: Process with pid 840 still alive after 1600ms, sending it SIGKILL now...
    PM2        | 2019-09-07T10:11:42: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL]
    PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=process killed
    PM2        | 2019-09-07T10:11:42: PM2 log: App [mm:0] starting in -fork mode-
    PM2        | 2019-09-07T10:11:43: PM2 log: App [mm:0] online
    
    /home/pi/.pm2/logs/mm-out.log last 15 lines:
    0|mm       | All module helpers loaded.
    0|mm       | Starting server on port 8080 ...
    0|mm       | Server started ...
    0|mm       | Connecting socket for: updatenotification
    0|mm       | Connecting socket for: MMM-Remote-Control
    0|mm       | Starting node helper for: MMM-Remote-Control
    0|mm       | Connecting socket for: MMM-NowPlayingOnSpotify
    0|mm       | Connecting socket for: MMM-MyCommute
    0|mm       | ====================== Starting node_helper for module [MMM-MyCommute]
    0|mm       | Connecting socket for: MMM-SystemStats
    0|mm       | Connecting socket for: MMM-BackgroundSlideshow
    0|mm       | Sockets connected & modules started ...
    0|mm       | Launching application.
    0|mm       | Refreshed access token because it has expired. Expired at: 10:12:00 now is: 10:12:01
    0|mm       | Refreshed access token because it has expired. Expired at: 11:12:01 now is: 10:12:01
    
    /home/pi/.pm2/logs/mm-error.log last 15 lines:
    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       | 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       | (node:871) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
    0|mm       | [960:0907/095911.730586:FATAL:memory.cc(22)] Out of memory. size=96002048
    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       | (node:3175) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
    0|mm       | [3214:0907/102404.493830:FATAL:memory.cc(22)] Out of memory. size=96002048
    
    
    
    


  • @CyruS1337 said in MMM-BackgroundSlideshow:

    | [3214:0907/102404.493830:FATAL:memory.cc(22)] Out of memory. size=96002048

    make the swap space bigger

    https://wpitchoune.net/tricks/raspberry_pi3_increase_swap_size.html


  • Project Sponsor

    @sdetweil Ok, I did. I’ll watch that. Can you explain in one sentence what I just did here or where the mistake was?



  • @CyruS1337 by default, the raspberry pi OS uses physical memory… if it runs out, it will try to swap out things not being used to make room for current work. but… the swap space is very small, only 100 meg…
    so the swap out fails, and the current process is killed


  • Project Sponsor

    Ok, thanks for the explanation 🙂 I can understand that reasonably. You are a genius



  • @CyruS1337 no… it happened to me!


  • Project Sponsor

    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
    
    


  • @CyruS1337 and rebooted after changing swap file


Log in to reply