4. BUG - after 3/4 days

BUG - after 3/4 days

  • S

    Hello,

    I installed magicMirror in my Raspberry pi 3 and i have successfully added my module. now, the software stop working after three/four days without significative error in log.

    maybe you had already this error, so thank you for your help in advance.

    the error in mm-out.log
    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
    Launching application.

    mm-error.log
    { 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 }

    magicmirror-error.log
    TypeError: Cannot read property ‘ServiceDelivery’ of undefined
    at processStif (/home/pi/MagicMirror/modules/infostransport/node_helper.js:79:30)
    at /home/pi/MagicMirror/modules/infostransport/node_helper.js:51:13
    at Request.handleRequestResponse [as _callback] (/home/pi/MagicMirror/modules/infostransport/node_modules/unirest/index.js:463:26)
    at Request.self.callback (/home/pi/MagicMirror/modules/infostransport/node_modules/request/request.js:187:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at Request. (/home/pi/MagicMirror/modules/infostransport/node_modules/request/request.js:1044:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at IncomingMessage. (/home/pi/MagicMirror/modules/infostransport/node_modules/request/request.js:965:12)
    fatal: unable to access ‘https://github.com/MichMich/MagicMirror.git/’: Could not resolve host: github.com

    fatal: unable to access ‘https://github.com/MichMich/MagicMirror.git/’: Could not resolve host: github.com

    fatal: unable to access ‘https://github.com/MichMich/MagicMirror.git/’: Could not resolve host: github.com

    fatal: unable to access ‘https://github.com/MichMich/MagicMirror.git/’: Could not resolve host: github.com

    fatal: unable to access ‘https://github.com/MichMich/MagicMirror.git/’: Could not resolve host: github.com

    fatal: unable to access ‘https://github.com/MichMich/MagicMirror.git/’: Could not resolve host: github.com

    i saw TypeError: Cannot read property ‘ServiceDelivery’ of undefined, it’s from my module, but i’m not sur that this error is the main cause, no one have probleme with communication with github ?

    thank you

    0

  • Error: listen EADDRINUSE 127.0.0.1:8080 usually means that something is already using port 8080 when the mm process attempts to start. The magic mirror process is trying to start a web server on port 8080, but something is already using that port.

    Usually, this occurs when you try to start the magic mirror again when it is already running. Sometimes this is because you’ve put the command to start MM in the init.d file to start upon boot and used pm2 to run a mm.sh script. Both can’t run, so one of them fails.

    The could not resolve host sounds like a problem either with your internet connection or with your DNS server settings. Quick troubleshooting:

    • SSH into your Magic Mirror (Or get a terminal on the mirror itself. Whatever.)
    • Try to ping the Google DNS servers: ping 8.8.8.8. If you do not get a response back immediately, troubleshoot your internet connection.
    • Test your DNS settings by typing curl www.abc.com. You should get a small amount of HTML text. If you get “Could not resolve host: www.abc.com” then you should probably troubleshoot your DNS nameserver settings. Start by typing cat /etc/resolv.conf and posting the results here.

    Good luck!

    0
  • H

    I am having similar issues as you! The problem is that the wifi connection drops after a day or so. I am also having similar logs like
    fatal: unable to access 'https://github.com/MichMich/MagicMirror.git/': Could not resolve host: github.com
    Which shows pretty clearly that internet is not available.

    I have also have custom module with poor error handling and I am getting undefined errors. But I tested my module without internet on my local OSX. It starts to give me same undefined errors. But when I put wifi back up it recovers perfectly. So I am wondering if the mirror is getting wifi back ever?!

    Also I am pretty sure that when mirror drops the connection it can’t get it back up because I can’t ssh into it anymore.

    Do you guys have any idea how to know if mirror is trying to reconnect to the internet?

    0 1 Reply

  • @henrikra The mirror application itself doesn’t connect to the internet. It uses your existing network connections as configured in the Raspbian operating system. The Raspbian installation already contains auto-reconnect out of the box. (this arrangement means that you can use a wireless connection, an ethernet connection or a bluetooth connection and the mirror will grab whatever is at hand).

    The failure to connect to GitHub is most likely the Update module checking to see if the Magic Mirror application has been updated. It’s what pops up the “An update to XXX is available!” notification.

    I don’t know how flaky your internet connection is, but it definitely seems like something you will have to account for in your coding. The update module seems to gracefully handle it and try again when the connection has been restored. Perhaps you can look to it for ideas.

    In the meantime, I would suggest an sudo apt-get update & sudo apt-get upgrade to make sure that you have any improvements to the networking of your Raspbian installation.

    0