MMM-WatchDog

paviro

Maybe this should be a default module?

MichMich

In most cases this module should not be necessary and probably only causes confusion. I built it for a mirror running on macOS which gives some issues due to an webGL module which causes a buffer overflow after a few days of running. (Bug in WebGL).

So this module is only there for edge cases. In most cases we just need to hunt down the bug causing the UI issue.

paviro

@MichMich ah I see :)

KirAsh4

macOS is the edge case. :)

Mr.Meeseeks

Does it work on server only mode?

MichMich

In that case only the server will be restarted, so that doesn’t make sense.

Mr.Meeseeks

Ha, ya that’s what I saw, it would shut down server. so I guess another reason why it’s not a default module unless it could detect if running in server mode.

fox

Are there any issues with the newest update known?
I got it work again after removed the watchdog module

rak

Hello guys,

I have mm running via PM2 already. I installed MMM-Watchdog. The gui crashed this night, but it did not restart. What did I do wrong?

My PM2 looks like this …

$ pm2 info MagicMirror
 Describing process with id 0 - name MagicMirror 
┌───────────────────┬──────────────────────────────────────────┐
│ status            │ online                                   │
│ name              │ MagicMirror                              │
│ restarts          │ 0                                        │
│ uptime            │ 37m                                      │
│ script path       │ /home/pi/MagicMirror/installers/mm.sh    │
│ script args       │ N/A                                      │
│ error log path    │ /home/pi/.pm2/logs/MagicMirror-error.log │
│ out log path      │ /home/pi/.pm2/logs/MagicMirror-out.log   │
│ pid path          │ /home/pi/.pm2/pids/MagicMirror-0.pid     │
│ interpreter       │ bash                                     │
│ interpreter args  │ N/A                                      │
│ script id         │ 0                                        │
│ exec cwd          │ /home/pi                                 │
│ exec mode         │ fork_mode                                │
│ node.js version   │ N/A                                      │
│ node env          │ N/A                                      │
│ watch & reload    │ ✔                                        │
│ unstable restarts │ 0                                        │
│ created at        │ 2018-09-09T08:36:00.617Z                 │
└───────────────────┴──────────────────────────────────────────┘
 Revision control metadata 
┌──────────────────┬────────────────────────────────────────────────┐
│ revision control │ git                                            │
│ remote url       │ https://github.com/MichMich/MagicMirror.git    │
│ repository root  │ /home/pi/MagicMirror                           │
│ last update      │ 2018-09-07T00:04:31.656Z                       │
│ revision         │ 6aa156d95667b230264fd99c5df877b25759e710       │
│ comment          │ Merge pull request #1343 from MichMich/develop │
│ branch           │ master                                         │
└──────────────────┴────────────────────────────────────────────────┘

rak

Found this. Can this b the reason it did not restart again?

When your app stays up for less than min_uptime (1s by default) until max_restarts (15 by default) is exceeded, it will stop restarting. So the most likely explanation here is that your app keeps crashing over and over for some reason. Whenever it stays up for longer than min_uptime, max_restarts is reset, so the default values should work just fine.