MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. longod
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    L
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 9
    • Groups 0

    longod

    @longod

    0
    Reputation
    619
    Profile views
    9
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    longod Unfollow Follow

    Latest posts made by longod

    • RE: How I got my Magic Mirror working on a Raspberry Pi 0 (zero)

      Hi! I have followed this guide step by step and so precisely, however I am still getting an error when I type in DISPLAY=:0 npm start through SSH. This is the output:

      pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start
      
      > magicmirror@2.1.1 start /home/pi/MagicMirror
      > sh run-start.sh
      
      /home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
      
      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
      

      Any help on what to do to solve this would be greatly appreciated!

      posted in Tutorials
      L
      longod
    • RE: MagicMirror fails to start after fresh install

      @Wippo Hey! I’m having a similar error message to you. What did you do to solve it?

      posted in Troubleshooting
      L
      longod
    • RE: npm start error?

      I realized that it is telling me to go to a different log now when I do npm start, which is npm ERR! /home/pi/.npm/_logs/2017-04-27T15_23_04_547Z-debug.log. In there it gives me this message:

      0 info it worked if it ends with ok
      1 verbose cli [ '/opt/nodejs/bin/node', '/usr/local/bin/npm', 'start' ]
      2 info using npm@4.5.0
      3 info using node@v7.7.1
      4 verbose run-script [ 'prestart', 'start', 'poststart' ]
      5 info lifecycle magicmirror@2.1.1~prestart: magicmirror@2.1.1
      6 silly lifecycle magicmirror@2.1.1~prestart: no script for prestart, continuing
      7 info lifecycle magicmirror@2.1.1~start: magicmirror@2.1.1
      8 verbose lifecycle magicmirror@2.1.1~start: unsafe-perm in lifecycle true
      9 verbose lifecycle magicmirror@2.1.1~start: PATH: /opt/nodejs/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/$
      10 verbose lifecycle magicmirror@2.1.1~start: CWD: /home/pi/MagicMirror
      11 silly lifecycle magicmirror@2.1.1~start: Args: [ '-c', 'sh run-start.sh' ]
      12 info lifecycle magicmirror@2.1.1~start: Failed to exec start script
      13 verbose stack Error: magicmirror@2.1.1 start: `sh run-start.sh`
      13 verbose stack spawn ENOENT
      13 verbose stack     at ChildProcess. (/opt/nodejs/lib/node_modules/npm/lib/utils/spawn.js:33:16)
      13 verbose stack     at emitTwo (events.js:106:13)
      13 verbose stack     at ChildProcess.emit (events.js:194:7)
      13 verbose stack     at maybeClose (internal/child_process.js:899:16)
      13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
      14 verbose pkgid magicmirror@2.1.1
      15 verbose cwd /home/pi/MagicMirror
      16 verbose Linux 4.4.50+
      17 verbose argv "/opt/nodejs/bin/node" "/usr/local/bin/npm" "start"
      18 verbose node v7.7.1
      19 verbose npm  v4.5.0
      20 error file sh
      21 error code ELIFECYCLE
      22 error errno ENOENT
      23 error syscall spawn
      24 error magicmirror@2.1.1 start: `sh run-start.sh`
      24 error spawn ENOENT
      25 error Failed at the magicmirror@2.1.1 start script 'sh run-start.sh'.
      25 error Make sure you have the latest version of node.js and npm installed.
      25 error If you do, this is most likely a problem with the magicmirror package,
      25 error not with npm itself.
      25 error Tell the author that this fails on your system:
      25 error     sh run-start.sh
      25 error You can get information on how to open an issue for this project with:
      

      I’m lost on what to do next…

      posted in Troubleshooting
      L
      longod
    • RE: npm start error?

      @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

      posted in Troubleshooting
      L
      longod
    • RE: npm start error?

      @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!

      posted in Troubleshooting
      L
      longod
    • RE: npm start error?

      @romain v4.2.1

      posted in Troubleshooting
      L
      longod
    • RE: npm start error?

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

      posted in Troubleshooting
      L
      longod
    • npm start error?

      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!

      posted in Troubleshooting
      L
      longod