Read the statement by Michael Teeuw here.
Motion Detector
-
and this is the error:
-
@trividar My apologies. This should be fixed. Just pull the latest.
-
@alexyak Now my MM start. But after awhile (2 min) i got this error and my MM freeze:
I disabled the DHT module but than i got this error:
Do you have also a solution for this? THX a lot!
-
@trividar I don’t see anything related to the motiondetector in your logs. It seems the error coming from the mmm-systemperature/node_helper.js
-
I disabled mmm-systemperature and now I have no errors on my log but after first deactivation of the monitor my raspberry freeze completely. Before the pull everything works perfekt beside DHT, now nothing works ;o( strange…
-
@trividar I’m having a similar issue. My mirror will turn on and off a few times, but after a few minutes it will peg the RAM and completely lock up the pi. Not sure what to try next.
-
I have also experienced something similar, always while running under a heavy load. Are you running a lot of modules, or anything that is very intensive? Some tasks like video streaming are incredibly demanding on the CPU.
My working solution was to modify my module selection so I’m not overworking the processor, and to increase the ‘updateInterval’ in my SystemStats section of config.js. Maybe try 15000 or 20000ms, see if it the crash occurs less often. I also run WatchDog and it would register the SystemStats failure. I don’t see WatchDog in these logs so this may not apply, but I also added increased ‘interval’ and ‘timeout’ settings to config.js. I have not seen this SystemStats crash for quite a while.
FWIW - after this crash WatchDog/pm2 does NOT restart my mm shell. All the other failures auto-restart, but something about this one crashes to the desktop. Also - sorry for threadjacking a “Motion Detection” thread!
-
I tried to increase the updateInterval to 200000ms and disabled all other modules, but always after the second time the monitor turn off my raspberry freeze completely and I have to reboot. My CPU is around 9 -15% when they freeze. I try again with the old version oft he motion-detector and it works, not perfect but works.
-
@in_a_days I guess I do run more modules than what “fit” the screen, but they’re cool and I can’t make up my mind which ones I want to keep lol.
However, I don’t believe that is the issue here. I have disabled all but three modules and still face the same issue. The second time the screen goes to sleep, it will not wake up. It doesn’t seem to matter what the CPU load or RAM is at.
Watching the pm2 logs, I get an uncaught exception error when the screen is supposed to wake up, but that is all the details I get from it. (That I know how to see, still new to this)
-
Unfortunately, I’m pretty new too!
To update - my mirror would still freeze (though it might take a couple hours) even after the changes I suggested. For me, the last error before the crash ALWAYS comes from the system status module (same exact ENOMEM error from the @trividar post). With the sys stat module disabled, I seem to be crash free. May not be the same thing you’re experiencing.
I also removed Watchdog after reading a bit more about it’s purpose.
If you are able to copy the log file from your most recent crash, someone smarter than me may be able to help.
