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.

    npm start error?

    Scheduled Pinned Locked Moved Troubleshooting
    13 Posts 5 Posters 9.9k Views 5 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.
    • L Offline
      longod
      last edited by

      Hi,
      I’m using a RPi 0 wireless, I have followed this tutorial step by step: https://forum.magicmirror.builders/topic/2075/magicmirror-on-pi-zero-w/2. However, when I put in “npm start” I’m getting this message:

      npm ERR! Linux 4.4.50+
      npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
      npm ERR! node v4.2.1
      npm ERR! npm v2.14.7
      npm ERR! file sh
      npm ERR! code ELIFECYCLE
      npm ERR! errno ENOENT
      npm ERR! syscall spawn
      npm ERR! magicmirror@2.1.1 start: 'sh run-start.sh'
      npm ERR! spawn ENOENT
      npm ERR!
      npm ERR! Failed at the magicmirror@2.1.1 start script 'sh run-start.sh'.
      npm ERR! This is most likely a problem with the magicmirror package,
      npm ERR! not with npm itself.
      npm ERR! Tell the author that this fails on your system:
      npm ERR!       sh run-start.sh
      npm ERR! You can get their info via:
      npm ERR!       npm owner ls magicmirror
      npm ERR! There is likely additional logging output above.
      
      npm ERR! Please include the following file with any support request:
      npm ERR!        /home/pi/MagicMirror/npm-debug.log```
      

      Here is the /home/pi/MagicMirror/npm-debug.log:

      0 info it worked if it ends with ok
      1 verbose cli ['/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
      2 info using npm@2.14.7
      3 info using node@v4.2.1
      4 verbose run-script [ 'prestart', 'start', 'poststart' ]
      5 info prestart magicmirror@2.1.1
      6 info start magicmirror@2.1.1
      7 verbose unsafe-perm in lifecycle true
      8 info magicmirror@2.1.1 Failed to exec start script
      9 verbose stack Error: magicmirror@2.1.1 start: 'sh run-start.sh'
      9 verbose stack spawn ENOENT
      9 verbose stack          at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:17:16)
      9 verbose stack          at emitTwo (events.js:87:13)
      9 verbose stack          at ChildProcess.emit (events.js:172:7)
      9 verbose stack          at maybeClose (internal/child_process.js:818:16)
      9 verbose stack          at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
      10 verbose pkgid magicmirror@2.1.1
      11 verbose cwd /home/pi/MagicMirror
      12 error Linux 4.4.50+
      16 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
      14 error node v4.2.1
      15 error npm v2.14.7
      16 error file sh
      17 error code ELIFECYCLE
      18 error errno ENOENT
      19 error syscall spawn
      20 error magicmirror@2.1.1 start: 'sh run-start.sh'
      20 error spawn ENOENT
      21 error Failed at the magicmirror@2.1.1 start script 'sh run-start.sh'.
      21 error This is most likely a problem with the magicmirror package,
      21 error not with npm itself.
      21 error Tell the author that this fails on your system:
      21 error       sh run-start.sh
      21 error You can get their info via:
      21 error         npm owner ls magicmirror
      21 error There is likely additional logging output above.
      22 verbose exit [ 1, true ]
      

      Any help on how to solve this issue would be greatly appreciated! Thanks in advanced!

      romainR Mykle1M 2 Replies Last reply Reply Quote 0
      • romainR Offline
        romain @longod
        last edited by

        @longod I don’t own a pi zero but I have few question.

        1. Were you on the MagicMirror folder when you did the npm start ?
        2. Were you directly on the pi using a usb keyboard (or equivalent) or were you on ssh ?

        If you were on the MagicMirror folder and you were directly on the pi I don’t know what the issue could be.
        If you wasn’t on the MagicMirror folder npm start won’t work.
        If you accessed your pi by ssh you need to use DISPLAY=:0 npm start command instead of npm start because graphical application need to know where they should be open. DISPLAY:0 mean the host machine (your pi)

        L 1 Reply Last reply Reply Quote 1
        • Mykle1M Offline
          Mykle1 Project Sponsor Module Developer @longod
          last edited by

          @longod

          Try updating your versions of node and npm as well

          Create a working config
          How to add modules

          1 Reply Last reply Reply Quote 0
          • L Offline
            longod @romain
            last edited by

            @romain

            1. Yea I was on the MagicMirror folder when I used npm start
            2. I’ve tried npm start on the pi using a keyboard, and I’ve tried through SSH. Got the same error message :/

            @Mykle1
            Just tried npm install and it gave out:

            npm WARN cannot run in wd @magicmirror2.1.1 cd vendor && npm install (wd=/home/pi/MagicMirror)
            npm WARN cannot run in wd @magicmirror2.1.1 sh installers/postinstall/postinstall.sh (wd=/home/pi/MagicMirror)
            

            I then did npm update and that gave out:

            /
            > electron@1.6.7 postinstall /home/pi/MagicMirror/node_modules/electron
            > node install.js
            
            electron@1.6.7 node _modules/electron
            >extract-zip@1.6.0 (debug@0.7.4, yauz1@2.4.1, mkdirp@0.5.0, concat-stream@1.5.0)
            >electron-download@3.3.0 (semver@5.3.0, home-path@1.0.5, minimist@1.2.0, rc@1.2.1, debug@2.6.4, path-exists@2.1.0, sumchecker@1.3.1, fs-extra@0.30.0, nugget@2.0.1)
            

            afterwards I ran npm start on the pi, and DISPLAY=0: npm start on SHH, and got the same original error messages.

            romainR strawberry 3.141S 2 Replies Last reply Reply Quote 0
            • romainR Offline
              romain @longod
              last edited by

              @longod what is your version of node ? node --version

              L 1 Reply Last reply Reply Quote 0
              • L Offline
                longod @romain
                last edited by

                @romain v4.2.1

                romainR 1 Reply Last reply Reply Quote 0
                • romainR Offline
                  romain @longod
                  last edited by

                  @longod I’m using the v7.9.0 . try to install an higher version of node

                  L 1 Reply Last reply Reply Quote 0
                  • strawberry 3.141S Offline
                    strawberry 3.141 Project Sponsor Module Developer @longod
                    last edited by

                    @longod try npm install --unsafe-perm

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

                    L 1 Reply Last reply Reply Quote 0
                    • L Offline
                      longod @romain
                      last edited by

                      @romain Okay I’ve updated to v7.7.1. I then tried DISPLAY=0: npm start and I got a similar message as before, however there is no longer a ERR! node v4.2.1 message, it skips over that part. Some progress!

                      1 Reply Last reply Reply Quote 0
                      • L Offline
                        longod @strawberry 3.141
                        last edited by

                        @strawberry-3.141 I gave that a go and checked npm -v, now its at 4.5.0 and is in the same boat as the node message that I was getting when I try to do DISPLAY=0: npm start. There still is the rest of the npm ERR! messages, just not the npm ERR! node v4.2.1 and npm ERR! npm v2.14.7

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 1 / 2
                        • First post
                          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