Blank screen - noob needs support



  • Hi, I just finished my MM project and it works fine for 5 days. This morning I got a blank screen with following notification:

    Starting MagicMirror: v2.1.3
    Loading config ...
    Loading module helpers ...
    No helper found for module: alert.
    Initializing new module helper ...
    Module helper loaded: updatenotification
    No helper found for module: clock.
    No helper found for module: MMM-TextClock.
    Initializing new module helper ...
    Module helper loaded: newsfeed
    No helper found for module: MMM-Globe.
    No helper found for module: MMM-GoogleMapsTraffic.
    All module helpers loaded.
    Starting server on port 8080 ... 
    Server started ...
    Connecting socket for: updatenotification
    Connecting socket for: newsfeed
    Starting module: newsfeed
    Sockets connected & modules started ...
    Whoops! There was an uncaught exception...
    { Error: listen EADDRINUSE 127.0.0.1:8080
        at Object.exports._errnoException (util.js:1050:11)
        at exports._exceptionWithHostPort (util.js:1073:20)
        at Server.setupListenHandle [as _listen2] (net.js:1263:14)
        at listenInCluster (net.js:1304:12)
        at doListen (net.js:1428:7)
        at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:10)
      code: 'EADDRINUSE',
      errno: 'EADDRINUSE',
      syscall: 'listen',
      address: '127.0.0.1',
      port: 8080 }
    

    Any ideas?
    Thx and Regards, Chris



  • Problem solved - I installed an other SD Card with the backup of MM and everything is working fine again… but I do not know what happened before. So I will have a backup in the desk if something will appear in near future 😉

    Regards, Chris



  • @chris1971 something was already using port 8080, probably the previous instance of magic mirror was not shut down properly and still occupying this port, or a different programm was using it



  • I have powered the PI and monitor via a wlan socket which can be switched on/off - could this cause the problem?
    Regards, Chris