• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

Looking for Beta-testers!

Scheduled Pinned Locked Moved MagicMirror
56 Posts 17 Posters 52.5k Views 18 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    roramirez Core Contributors
    last edited by Jan 30, 2017, 10:33 PM

    Hey Guys,

    To prevent problems like the error on validation on develop branch I say to you we are working a test suite for MagicMirror.

    Now is initial state with some tests. Today @MichMich merged a change with some testing for e2e area. At now isn’t integrated the e2e tests in Travis. You can run e2e tests with

    export DISPLAY=:0 && npm run test:e2e
    You need run npm install before

    The build a test is simple. If someone is animated and want to build one or need some light let me know.

    So, also it helps if you run the e2e tests into your system and tells us if something is wrong or good.

    Easy module development with MagicMirror Module Template

    M 1 Reply Last reply Jan 30, 2017, 11:37 PM Reply Quote 0
    • M Offline
      morozgrafix Moderator @roramirez
      last edited by Jan 30, 2017, 11:37 PM

      @roramirez I just submitted PR to add chai-as-promised to devDependencies. I was missing it from globally installed packages and ran into an error when tried to run tests.

      E 1 Reply Last reply Jan 31, 2017, 11:49 PM Reply Quote 0
      • E Offline
        ESOB @morozgrafix
        last edited by Jan 31, 2017, 11:49 PM

        Something on the develop branch turned my magic mirror back to black screen again (It ran fine on develop branch yesterday but when I did my pull&&install today it went down again). Here is the information from the pm2 logs, tell me if you need anything else:

        mm-0 (out): Module helper loaded: MMM-NFL
        mm-0 (out): Initializing new module helper ...
        mm-0 (out): Module helper loaded: newsfeed
        mm-0 (out): All module helpers loaded.
        mm-0 (out): Starting server op port 8080 ...
        mm-0 (out): Server started ...
        mm-0 (out): Connecting socket for: MMM-Remote-Control
        mm-0 (out): Starting node helper for: MMM-Remote-Control
        mm-0 (out): Connecting socket for: calendar
        mm-0 (out): Starting node helper for: calendar
        mm-0 (out): Connecting socket for: MMM-Traffic
        mm-0 (out): MMM-Traffic helper started ...
        mm-0 (out): Connecting socket for: MMM-WunderGround
        mm-0 (out): MMM-WunderGround helper started ...
        mm-0 (out): Connecting socket for: MMM-NFL
        mm-0 (out): Starting module: MMM-NFL
        mm-0 (out): Connecting socket for: newsfeed
        mm-0 (out): Starting module: newsfeed
        mm-0 (out): Sockets connected & modules started ...
        mm-0 (out): Launching application.
        
        mm-0 (err):     at exports._exceptionWithHostPort (util.js:1049:20)
        mm-0 (err):     at Server._listen2 (net.js:1253:14)
        mm-0 (err):     at listen (net.js:1289:10)
        mm-0 (err):     at net.js:1399:9
        mm-0 (err):     at _combinedTickCallback (internal/process/next_tick.js:77:11)
        mm-0 (err):     at process._tickCallback (internal/process/next_tick.js:98:9)
        mm-0 (err):     at Module.runMain (module.js:592:11)
        mm-0 (err):     at run (bootstrap_node.js:402:7)
        mm-0 (err):     at startup (bootstrap_node.js:157:9)
        mm-0 (err):   code: 'EADDRINUSE',
        mm-0 (err):   errno: 'EADDRINUSE',
        mm-0 (err):   syscall: 'listen',
        mm-0 (err):   address: '::',
        mm-0 (err):   port: 8080 }
        mm-0 (err): ERROR! Could not find main module js file.
        
        
        M 1 Reply Last reply Jan 31, 2017, 11:51 PM Reply Quote 0
        • M Offline
          morozgrafix Moderator @ESOB
          last edited by Jan 31, 2017, 11:51 PM

          @ESOB looks like your port 8080 is in use. Do you happen to have another instance of MM running already? Or maybe something else is taking your port 8080.

          E 1 Reply Last reply Jan 31, 2017, 11:57 PM Reply Quote 0
          • E Offline
            ESOB @morozgrafix
            last edited by ESOB Feb 1, 2017, 12:05 AM Jan 31, 2017, 11:57 PM

            @morozgrafix maybe, I issued a pm2 stop and then did a restart and I am no longer getting that error. I am still getting a black only screen with the only error being:

            "ERROR! Could not find main module js file."
            

            What logs should I get you to figure out the reason for lack of display?

            Edit:
            Scratch that, I double checked the logs and I get the same error. I will do a full pi reboot again to triple check but it seems consistent.
            Edit 2:
            After triple check, only one MM instance open and same error noted about port 8080.

            M 2 Replies Last reply Feb 1, 2017, 12:06 AM Reply Quote 0
            • M Offline
              morozgrafix Moderator @ESOB
              last edited by Feb 1, 2017, 12:06 AM

              @ESOB did you run npm install after pulling development branch? Next step would be to try to start it in node serveronly mode and point your browser at http://:8080 or run npm start Dev and see if you get any errors in console log of the browser or electron app

              1 Reply Last reply Reply Quote 0
              • M Offline
                morozgrafix Moderator @ESOB
                last edited by morozgrafix Feb 1, 2017, 12:08 AM Feb 1, 2017, 12:08 AM

                @ESOB sorry I was replying before you edited post with update. Try temporarily changing your config.js to another port if 8080 is taken for some reason.

                E 1 Reply Last reply Feb 1, 2017, 12:19 AM Reply Quote 0
                • E Offline
                  ESOB @morozgrafix
                  last edited by Feb 1, 2017, 12:19 AM

                  @morozgrafix So I tried changing the port number to 8081 and I got this:

                  mm-0 (err): WARNING! Could not load config file. Starting with default configuration. Error found: RangeError: "port" argument must be >= 0 and < 65536
                  mm-0 (err): App threw an error during load
                  mm-0 (err): RangeError: "port" argument must be >= 0 and < 65536
                  mm-0 (err):     at assertPort (internal/net.js:17:11)
                  mm-0 (err):     at Server.listen (net.js:1371:7)
                  mm-0 (err):     at new Server (/home/pi/MagicMirror/js/server.js:20:9)
                  mm-0 (err):     at /home/pi/MagicMirror/js/app.js:193:18
                  mm-0 (err):     at loadNextModule (/home/pi/MagicMirror/js/app.js:142:5)
                  mm-0 (err):     at /home/pi/MagicMirror/js/app.js:137:6
                  mm-0 (err):     at Class.loaded (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:19:3)
                  mm-0 (err):     at loadModule (/home/pi/MagicMirror/js/app.js:118:6)
                  mm-0 (err):     at loadNextModule (/home/pi/MagicMirror/js/app.js:135:5)
                  mm-0 (err):     at /home/pi/MagicMirror/js/app.js:137:6
                  mm-0 (err): ERROR! Could not find main module js file.
                  
                  

                  I did run npm install, also tried serveronly and running npm start dev but did not gather any additional information. I will say the weird thing is when I leave it on port 8080, the remote control module still loads.

                  M 2 Replies Last reply Feb 1, 2017, 12:25 AM Reply Quote 0
                  • M Offline
                    morozgrafix Moderator @ESOB
                    last edited by morozgrafix Feb 1, 2017, 12:26 AM Feb 1, 2017, 12:25 AM

                    @ESOB This error WARNING! Could not load config file. seems very odd. Can you please post your config.js file? Also another option is to backup your config.js and do file copy of config.js.sample to config.js to have good known configuration to begin with.

                    When starting with npm start dev or node serveronly do you see any errors in the Console Log of the dev tools of the electron or your browser?

                    P.S. I wanted to fork this troubleshooting conversation into a separate thread, but can’t seem to find a way.

                    1 Reply Last reply Reply Quote 0
                    • M Offline
                      morozgrafix Moderator
                      last edited by Feb 1, 2017, 12:41 AM

                      @roramirez & @MichMich looks like develop branch got broken with this commit https://github.com/MichMich/MagicMirror/commit/354b745c39a19915c3a8547445a5049555bd37ff#diff-75953debd6cf3faf33d4ff10e8353645R11

                      Line 11 of defaults.js got this change port: process.env.MM_PORT || 8080, and server is not starting up throwing error in the console log:

                      Uncaught ReferenceError: process is not defined
                          at defaults.js:11
                      (anonymous) @ defaults.js:11
                      
                      R 1 Reply Last reply Feb 1, 2017, 1:10 AM Reply Quote 0
                      • 1
                      • 2
                      • 3
                      • 4
                      • 5
                      • 6
                      • 5 / 6
                      5 / 6
                      • First post
                        44/56
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy