Modules stop work over time
My setup works at first but gradually some modules stop working.
I use newsfeed and clock from the default modules and MMM-Scrobler and MMM-RandomPhoto from third part.
The scrobbler can work for hours and then stop and then start again. The RandomPhoto seems to work but on the morning it has frozen and does not circle pictures anymore.
Everything works again if I restart through SSH.
Everything is updated.
Any thoughts what could be the solution?
Sounds to me like a hiccup on your network.
Well… nothing else on my network is hiccupy. Just those modules…
Is there anything in the logs? That would be first place I would start, maybe turning up the log level to get more detail.
I made a npm debug, if thats what you mean… Heres is some error, but I don’t know how to fix or if it is this making the troubles…
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/nodejs’, ‘/usr/bin/npm’, ‘start’, ‘dev’ ]
2 info using email@example.com
3 info using firstname.lastname@example.org
4 verbose config Skipping project config: /home/pi/.npmrc. (matches userconfig)
5 verbose stack Error: ENOENT: no such file or directory, open ‘/home/pi/package.json’
5 verbose stack at Error (native)
6 verbose cwd /home/pi
7 error Linux 4.4.19-v7+
8 error argv “/usr/bin/nodejs” “/usr/bin/npm” “start” “dev”
9 error node v6.4.0
10 error npm v3.10.6
11 error path /home/pi/package.json
12 error code ENOENT
13 error errno -2
14 error syscall open
15 error enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
16 error enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
16 error enoent This is most likely not a problem with npm itself
16 error enoent and is related to npm not being able to find a file.
17 verbose exit [ -2, true ]
In mm-out.log I find this
Whoops! There was an uncaught exception…
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
Thing is, once it’s up and running, things just remain in memory and run. The only time it will restart is if the entire thing crashes. But you can check on that by typing in
'pm2 list'and look at the restarts column. If you are seeing a lot of restarts, then something else is going on that’s causing it to crash. Mine’s been running stable for the past almost 30 days now (I haven’t been active on my mirror with coding nor updates, life took over.)
How things stop, specifically data being requested, is if there is a momentary network issue that the task could not reach the internet. However, even that will rectify itself at the next poll … If I disconnect my rpi from the network, eventually things like the calendar, newsfeed, and weather will all stop responding. When I reconnect it, they will all eventually refresh and start working again. So I don’t know what could be causing yours to simply quit.
@KirAsh4 The only restarts it shows is my manual restarts with pm2 restart mm command. Otherwise it does not crash. The modules just stop answer. And at the same time the news-ticker still works…
Could it be so that the memory is overflooded somehow?