• 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.

[Remote-Control] Shutdown, Configure and Update your MagicMirror

Scheduled Pinned Locked Moved System
274 Posts 78 Posters 725.0k Views 77 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.
  • K Offline
    kurt @strawberry 3.141
    last edited by Apr 10, 2017, 6:30 PM

    @strawberry-3-141
    PM2 restart won’t work.
    Could you have a look, please.
    Thanks a lot

    [PM2] PM2 Successfully daemonized
    Use --update-env to update environment variables
    ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────────┐
    │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │
    └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────────┘
     Use `pm2 show ` to get more details about an app
    
    [PM2][ERROR] Process mm not found
    
    { Error: Command failed: pm2 restart mm
    [PM2][ERROR] Process mm not found
    
        at ChildProcess.exithandler (child_process.js:218:12)
        at emitTwo (events.js:106:13)
        at ChildProcess.emit (events.js:191:7)
        at maybeClose (internal/child_process.js:877:16)
        at Socket. (internal/child_process.js:334:11)
        at emitOne (events.js:96:13)
        at Socket.emit (events.js:188:7)
        at Pipe._handle.close [as _onclose] (net.js:493:12) killed: false, code: 1, signal: null, cmd: 'pm2 restart mm' }
    pi@raspberrypi:~/MagicMirror $
    S 1 Reply Last reply Apr 10, 2017, 7:09 PM Reply Quote 0
    • S Offline
      strawberry 3.141 Project Sponsor Module Developer @kurt
      last edited by Apr 10, 2017, 7:09 PM

      @kurt looks like there is currently no instance running that can be restarted so just start a new one by doing pm2 start mm

      Please create a github issue if you need help, so I can keep track

      K 1 Reply Last reply Apr 10, 2017, 7:21 PM Reply Quote 0
      • K Offline
        kurt @strawberry 3.141
        last edited by Apr 10, 2017, 7:21 PM

        @strawberry-3.141
        Thank you, this is what I get…

        pi@raspberrypi:~/MagicMirror $  pm2 start mm
        [PM2][ERROR] script not found : /home/pi/MagicMirror/mm
        script not found : /home/pi/MagicMirror/mm
        ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────────┐
        │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │
        └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────────┘
         Use `pm2 show ` to get more details about an app
        pi@raspberrypi:~/MagicMirror $ pm2 show
        
          error: missing required argument `id'
        
        pi@raspberrypi:~/MagicMirror $
        S 1 Reply Last reply Apr 10, 2017, 7:27 PM Reply Quote 0
        • S Offline
          strawberry 3.141 Project Sponsor Module Developer @kurt
          last edited by Apr 10, 2017, 7:27 PM

          @kurt [PM2][ERROR] script not found

          did you follow these steps to create the script? https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

          Please create a github issue if you need help, so I can keep track

          K 1 Reply Last reply Apr 10, 2017, 7:30 PM Reply Quote 0
          • K Offline
            kurt @strawberry 3.141
            last edited by Apr 10, 2017, 7:30 PM

            @strawberry-3.141
            yes I did it following the steps in that wiki

            1 Reply Last reply Reply Quote 0
            • Y Offline
              yawns Moderator
              last edited by Apr 11, 2017, 7:11 AM

              Shouldn’t pm2 start mm be executed in ~ and not in ~/MagicMirror ? The tutorial said to create mm.sh in ~

              So please go back one folder with cd .. or directly with cd ~ and try again

              K 1 Reply Last reply Apr 11, 2017, 8:54 AM Reply Quote 1
              • K Offline
                kurt @yawns
                last edited by Apr 11, 2017, 8:54 AM

                @yawns
                this is what I get,
                do you think it is a good idea to start the install routine once again from the beginning? pi@raspberrypi:~ $
                in my modules folder there is no PM2 folder. Should there be one?
                Thanks a lot for help
                kurt

                pi@raspberrypi:~ $ npm start
                npm ERR! Linux 4.4.50-v7+
                npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
                npm ERR! node v6.10.0
                npm ERR! npm  v3.10.10
                npm ERR! path /home/pi/package.json
                npm ERR! code ENOENT
                npm ERR! errno -2
                npm ERR! syscall open
                
                npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                npm ERR! enoent This is most likely not a problem with npm itself
                npm ERR! enoent and is related to npm not being able to find a file.
                npm ERR! enoent 
                
                npm ERR! Please include the following file with any support request:
                npm ERR!     /home/pi/npm-debug.log
                pi@raspberrypi:~ $  pm2 start mm
                [PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2
                [PM2] PM2 Successfully daemonized
                [PM2][ERROR] script not found : /home/pi/mm
                script not found : /home/pi/mm
                ┌──────┬──────┬────────┬───┬─────┬────────┐
                │ Name │ mode │ status │ ↺ │ cpu │ memory │
                └──────┴──────┴────────┴───┴─────┴────────┘
                 Use `pm2 show ` to get more details about an app
                
                
                Y 1 Reply Last reply Apr 11, 2017, 9:56 AM Reply Quote 0
                • Y Offline
                  yawns Moderator @kurt
                  last edited by Apr 11, 2017, 9:56 AM

                  @kurt

                  If you want to start the process with npm start then you have to do that inside ~/MagicMirror
                  However if you want to use pm2 then I would advise following the instructions again: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

                  pm2 seems to be working fine on your raspberry, so I would start here:


                  Make a MagicMirror start script. To use PM2 in combination with MagicMirror, we need to make a simple shell script. Preferable, we put this script outside the MagicMirror folder to make sure it won’t give us any issues if we want to upgrade the mirror.

                  cd ~
                  nano mm.sh
                  

                  Add the following lines:

                  cd ~/MagicMirror
                  DISPLAY=:0 npm start
                  

                  Save and close, using the commands CTRL-O and CTRL-X. Now make sure the shell script is executable bij performing the following command:

                  chmod +x mm.sh
                  

                  You are now ready to the MagicMirror using this script using PM2.

                  K 1 Reply Last reply Apr 11, 2017, 10:43 AM Reply Quote 1
                  • K Offline
                    kurt @yawns
                    last edited by Apr 11, 2017, 10:43 AM

                    @yawns
                    my first step was to make this start script following the instructions.
                    the mm.sh with the script cd ~/MagicMirror DISPLAY=:0 npm start is now in my /home/pi folder.
                    When I try to start the mm by npm start I get this (the mirror is not appearing):

                    { Error: listen EADDRINUSE :::8080
                        at Object.exports._errnoException (util.js:1026:11)
                        at exports._exceptionWithHostPort (util.js:1049:20)
                        at Server._listen2 (net.js:1253:14)
                        at listen (net.js:1289:10)
                        at net.js:1399:9
                        at _combinedTickCallback (internal/process/next_tick.js:77:11)
                        at process._tickCallback (internal/process/next_tick.js:98:9)
                        at Module.runMain (module.js:592:11)
                        at run (bootstrap_node.js:402:7)
                        at startup (bootstrap_node.js:157:9)
                      code: 'EADDRINUSE',
                      errno: 'EADDRINUSE',
                      syscall: 'listen',
                      address: '::',
                      port: 8080 }
                    

                    Thank you

                    K 1 Reply Last reply Apr 11, 2017, 11:28 AM Reply Quote 0
                    • Y Offline
                      yawns Moderator
                      last edited by Apr 11, 2017, 11:16 AM

                      EADDRINUSE means, there is another process running and listening on port 8080
                      It looks like the magicmirror somehow is running already.

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 19
                      • 20
                      • 21
                      • 22
                      • 23
                      • 27
                      • 28
                      • 21 / 28
                      21 / 28
                      • First post
                        201/274
                        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