Read the statement by Michael Teeuw here.
rpi3 freezes every few days .. need help
-
@nagaculun sounds like the swap space might need to be enlarged
-
@sdetweil and how do I do that ?
Thanks
-
@nagaculun now now… google is your friend
see https://www.bitpi.co/2015/02/11/how-to-change-raspberry-pis-swapfile-size-on-rasbian/
-
@nagaculun Are you using MMM-GoogleTrafficMap? This module has a severe memory leak. Increasing swap memory will not help, as it just shifts the freeze to a later point in time. Other option is to setup a cron job that reboots regularly the RPi.
-
@Fozi i have a fixed GoogleMapsTraffic module on my github.
I submitted it, but it hasn’t been picked up… -
@sdetweil thanks for the heads up!
Didn’t know you fixed it. I’ll give it a try for my next MM version, I’m currenttly planning. -
@Fozi I dont have the MMM-GoogleTrafficMap. Even just the default clock module has the issue.
I setup a cron to reboot every day at 6am; and it happens as well.
-
Just modify accordingly. Now wait and see. Thanks.
-
@sdetweil
It still freezes even I made the modification. -
@nagaculun bummer…
-
@nagaculun Are you sure that the crontab is really executed? ssh into the RPI, execute ‘htop’ and check the uptime. The uptime should be the difference between the cronjob execution and the actual time.
For setting up the crontab, that reboots the RPi I needed priviledged rights.
$ sudo crontab -e and then insert, e.g. 15 1,9,17 * * * sudo shutdown -r now >/dev/null 2>&1This reboots the RPi at 01:15, 9:15 and 17:15 every day (every 8 hrs.).
Note the two ‘sudo’ for editing the crontab and initiating the shutdown. -
Some experiences I made:
My “productive” MM runs on a RPi 3B+. I have also a normal RPi 3B, which I use as a test bench in the exact same configuration as my MM (I’ve use a cloned SD card).
Surprisingly, the 3B’s memory is not filling up and stalling like my 3B+.
God knows why. -
@Fozi said in rpi3 freezes every few days .. need help:
@nagaculun Are you sure that the crontab is really executed? ssh into the RPI, execute ‘htop’ and check the uptime. The uptime should be the difference between the cronjob execution and the actual time.
For setting up the crontab, that reboots the RPi I needed priviledged rights.
$ sudo crontab -e and then insert, e.g. 15 1,9,17 * * * sudo shutdown -r now >/dev/null 2>&1This reboots the RPi at 01:15, 9:15 and 17:15 every day (every 8 hrs.).
Note the two ‘sudo’ for editing the crontab and initiating the shutdown.Yes, as I literally wait and see when it happens.
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