MM crashes after latest update

sdetweil

@joberbroeckling said in MM crashes after latest update:

MMM-Remote-Control

has an issue against it not working on 2.11, and

maybe MMM-homeassistant-sensors… I can’t tell, there are 6 different versions… which one do you have?
(git remote -v in the module folder will give the git repo name).

joberbroeckling

https://github.com/Snille/MMM-homeassistant-sensors

sdetweil

@joberbroeckling ok. That one only has fonts as a dependency

joberbroeckling

I think it may be the DarkSky module. Since I have reached my API request limit it has stopped crashing.

joberbroeckling

I think I spoke too soon. I removed the DarkSky, Remote Control and Home Assistant Sensors modules and it still crashes on start up. The system load is high but after a while it decreases. I think I will try to a fresh install and see what happens.

joberbroeckling

I did a fresh install and installed the modules one at a time. I commented out the modules I already added in my config file. I did notice there is a thread going on regarding MMM-Remote-Control module not working with latest update. So I removed it because I don’t use it that much anyways.

Then I un-commented all the modules in my config file and it crashed again. I think it has to do with Electron. But I am not a professional and I am only doing this for fun. The CPU load is huge when it starts up. I don’t think this will work on RPI 3 anymore.

I reverted back to 2.10.1 and everything seems to work fine.

sdetweil

@joberbroeckling i have it running on pi 0, pi 3, pi 4, odroid, nano, ubuntu, and Mac catalina

no issues…

I don’t use remote-control or pir, or buttons

there is a fix for the remote-control in that topic (u have to change the code)

so, fresh install, no additions/changes, does it run ok?

joberbroeckling

If I do a fresh install and add the same modules (except remote-control) I had before it crashes. So I am not sure how to test which module is causing the issue.

sdetweil

@joberbroeckling disabled all the modules u added,

add

disabled:true.

to each module section

module:?????,
disabled:true,

pm2 stop 0
one at a time, change true to false, restart mirror

npm start dev

if it works, ctrl-c to kill mirror, edit config, enable next
and repeat

if it fails, see the terminal window and developers window, console tab for errors
ctrl c on terminal window to exit

joberbroeckling

I think I figured out what the issue is. It has to do with the MMM-WatchDog and the interval was too low. It was previously set to 10s. I upped it to 30s and it hasn’t restarted since.