Modules stop work over time

[lali]

@KirAsh4 I dont think so, I do not reset the pi-hole, i only reset MM.

If the pi-hole were to blame, I should not be able to reach last.fm or the source where I load images from. And it should not work for at first and then all of a sudden not…

Maybe something just times out…?

[KirAsh4]

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.

[lali]

@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…

[lali]

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’ }

[lali]

I think i resolved the issue… It was related to my use of Pi-hole.
I was using OpenDNS and according to logs in my router some connections were timed out or was unreachable. I changed it first to Google DNS and later to my ISPs DNS-severs. And, behold, no error in my pm2-logs (at least not at the moment) and the modules are up and running

So, you were all on to something; @KirAsh4, @McSorley and @kckndrgn!