Read the statement by Michael Teeuw here.
MMM-BackgroundSlideshow
-
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 mmin the console, the picture comes back. I have also run the dependency in module foldernpm install, without success.What could be the reason for this?
-
@CyruS1337 show us pm2 logs
-
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
-
@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 -
Ok, thanks for the explanation :) I can understand that reasonably. You are a genius
-
@CyruS1337 no… it happened to me!
-
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 0and then restart it withpm2 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
-
@sdetweil said in MMM-BackgroundSlideshow:
and rebooted after changing swap file
I have now reboot the mirror …
-
free -m
Command will show memory usage -
@sdetweil said in MMM-BackgroundSlideshow:
free -m
Command will show memory usagepi@raspberrypi_1:~ $ free -m total used free shared buff/cache available Mem: 925 218 404 1 302 657 Swap: 1023 111 912 -
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 905Edit: The mirror was stopped and started and after 15min he was dark again …
-
I seem to have found the mistake. I have selected one to quality of photos for playing the photos (4mb per photo). The fact that I have chosen a lower quality of the photos, the problem is gone.
-
@CyruS1337 interesting, i use MMM-ImagesPhotos, and have lots of images over 4meg, most in the 11-13 meg range
-
Yes, that’s really interesting. But since I let the pictures play with max 1-2 MB, the mirror was never black anymore. Although I did the elevation of SWAP.
-
Hello,
I’m new to magic mirror. Since two weeks I try to get MMM-ImagesPhotos or MMM-BackgroundSlideshow to work with the photos of my camera (all pictures are JPEG with 5 to 10 meg).
Like @CyruS1337 the whole mirror goes black, if I use my photos but works if I use the example-pictures.
@sdetweil :
How did you get this to work with your pictures?
Could you post your config (including tweeks you did) and tell us which pi you are using?I was so desperate that I looked for alternatives. I found pi3d but couldn’t integrate it into magic mirror.
I would really appreciate your help.
Best regards
hootzter
-
@hootzter said in MMM-BackgroundSlideshow:
MMM-ImagesPhotos
usually black screen means some missing library…
if u npm start from the terminal window you will see runtime messages
also from the developers window , ctrl-shift-i on the mirror keyboard, select the console tab, and scroll up.you can try my MMM-ImagesPhotos
https://github.com/sdetweil/MMM-ImagesPhotosmy config
{ module: "MMM-ImagesPhotos", disabled: false, position: "fullscreen", // < --- this is the div location NOT screen covered with image config: { opacity: 0.9, animationSpeed: 0, updateInterval: 30000, // how often to change pic backgroundColor: "#808080", // color around pic (if u want something other than black) }, },I have run this on pi0 thru pi4, mac, and two non-pi SBCs, odroid Xu4, and nano jetson.
where did u put your pictures? the module is looking in the folder
~/MagicMirror/modules/MMm_ImagesPhotos/uploadsI linked that to a mounted server volume
now, my tweaks were to display the images without distortion… same aspect ratio as taken.
I did NOT want the screen completely filled… (image stretched or clipped)to use mine, just rename the old MMM-ImagesPhotos folder out of the way, and then git clone my version of the module.
-
@sdetweil Hi, is it possible to cover the whole screen with mmm images photos?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login