3. MagicMirror wont start
MagicMirror² v2.5.0 is available! For more information about this release, check out this topic.

MagicMirror wont start

  • K

    hello
    i have a problem. the magicmirror installation was succesfull and i tried a few things. ive made a break and now i thougt i can continue my work. but when i type npm start in MagicMirror folder i get this errorcode

    
> magicmirror@2.3.1 start /home/pi/MagicMirror
> sh run-start.sh

Starting MagicMirror: v2.3.1
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.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper ...
Module helper loaded: newsfeed
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control-Repository
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: MMM-TelegramBot
Initializing new module helper ...
Module helper loaded: MMM-PIR-Sensor
Initializing new module helper ...
Module helper loaded: MMM-Todoist
All module helpers loaded.
Starting server on port 8080 ...
You're using a full whitelist configuration to allow for all IPs
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-Remote-Control-Repository
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-TelegramBot
Connecting socket for: MMM-PIR-Sensor
Connecting socket for: MMM-Todoist
Starting node helper for: MMM-Todoist
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 }
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.
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined
(node:7234) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 7): TypeError: Cannot read property 'refs' of undefined

    i hope you can help me. sorry for my bad english

    0 1 Reply
  • Moderator

    That means there is another process running on port 8080. Did you maybe install pm2 to automate startup? Check with pm2 list

    0
  • Module Developer

    @kalleK This looks like you already have an instance of MagicMirror running. Do you use pm2 to run your MagicMirror on startup?

    If you use pm2 you can run pm2 restart MagicMirror to restart the MagicMirror.

    0
  • K

    Thank you for your reply. You are right. Nevertheless is there another Error :

    (node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined
(node:7234) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): TypeError: Cannot read property 'refs' of undefined
(node:7234) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 7): TypeError: Cannot read property 'refs' of undefined

    What means this ?

    0
  • K

    this is the reply now:

    pi@raspberrypi:~/MagicMirror $ npm start

> magicmirror@2.3.1 start /home/pi/MagicMirror
> sh run-start.sh

Starting MagicMirror: v2.3.1
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.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper ...
Module helper loaded: newsfeed
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control-Repository
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: MMM-TelegramBot
Initializing new module helper ...
Module helper loaded: MMM-PIR-Sensor
Initializing new module helper ...
Module helper loaded: MMM-Todoist
All module helpers loaded.
Starting server on port 8080 ...
You're using a full whitelist configuration to allow for all IPs
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-Remote-Control-Repository
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-TelegramBot
Connecting socket for: MMM-PIR-Sensor
Connecting socket for: MMM-Todoist
Starting node helper for: MMM-Todoist
Sockets connected & modules started ...
Launching application.
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined
(node:19302) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'refs' of undefined
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'refs' of undefined
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): TypeError: Cannot read property 'refs' of undefined
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): TypeError: Cannot read property 'refs' of undefined
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): TypeError: Cannot read property 'refs' of undefined
(node:19302) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 7): TypeError: Cannot read property 'refs' of undefined
Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/m9e75p8rl08l641vc5cm4bhrtg%40group.calendar.google.com/public/basic.ics - Interval: 300000
Create new calendar fetcher for url: http://www.schwarze-elster.de/touren/getICalendar.php?reminder=0&ort=1&from=1.4.2018&to=31.12.2018&tonnen=12354 - Interval: 300000
Create new news fetcher for url: http://www.spiegel.de/schlagzeilen/tops/index.rss - Interval: 300000
[RCREPO] Repository scanning...
[RCREPO] modules.json is updated.
    0 1 Reply

  • @kalleK Well, those errors didn’t seem to kill your mirror. I would comment out the 3rd-party modules in your config.js and restart your mirror process. Add them back one at a time until you get those warnings again and then talk to the module developer. Assuming those are module errors.

    1