Read the statement by Michael Teeuw here.
Modules stop work over time
-
@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?
-
Not unless you have a bunch of other stuff running on your rpi. What happens if you run only the default configuration and modules? Do any of those stop responding after a while, and what exactly happens, what does the display say or do?
-
@KirAsh4 The only thing i run besides MM is Pi-hole.
The Scrobbler-plugin has never lived for a longer time. It works for a few songs, maybe an album and when a song ends it just disappears. No error messages or something on the screen. If i pm2 restart mm it again, it works for a few songs again.
When RandomPhoto stops working, it freezes on an image, like it comes to an end of a stack. (Maybe it does?)
Clock and news seems to work all the time.
Could it be that file package.json?
-
Yeah, neither of those are default packages (that I could help you with.) Perhaps this is something you need to take to the respective authors and have them help you track down what the problem could be. It sounds like MM and its default modules are working just fine, so this is something that happens outside of it (specifically with those modules you mentioned.)
As a side query: why do you need pi-hole on the rpi? None of the default modules display ads, unless you’re actively using the rpi as a desktop computer and browse the internet with it.
-
@KirAsh4 Well, I suppose that is my next step then…
I use it to block out ads throughout my network. I set it as a dns in the router. It filters ads quiet nice. From web and in apps.
The MM install was to make use of my display I bought with some nifty information.
-
Is it possible that pi-hole is seeing those network queries (from those modules) and actively blocking them till you reset the whole thing again?
-
-
Those are questions for the authors. If it were me though, I would disable everything from running on the rpi, or start with a completely clean setup (including a reformat and reload of the Raspbian image), and see where that takes you. But that’s me. I like to eliminate any and all possible causes. It’s also why I have multiple rpis sitting on my desk … I can easily and quickly spin one up from scratch.
-
@KirAsh4 I only have one at home. And one at work… But I will soon lay my hands on some more.
Well, thanks for your input. I’ll dig deeper…
-
Fresh error log
{ Error: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1087:19)
at TLSSocket.g (events.js:286:16)
at emitNone (events.js:91:20)
at TLSSocket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:926:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9) code: ‘ECONNRESET’ }
