MagicMirror fails to start after fresh install
-
Hi,
after doing a fresh install, MagicMirror fails to install.Using:
- Pi 3
- Raspbian Jessie with PIXEL (Kernel 4.4, release date 2017-04-10)
- Automatic install
Starting using
pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start
results inmagicmirror@2.1.1 start /home/pi/MagicMirror
sh run-start.shnpm ERR! Linux 4.4.50-v7+
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “start”
npm ERR! node v6.10.2
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! magicmirror@2.1.1 start:sh run-start.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.1.1 start script ‘sh run-start.sh’.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, 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 information on how to open an issue for this project with:
npm ERR! npm bugs magicmirror
npm ERR! Or if that isn’t available, 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.lognpm-debug.log contains:
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/nodejs’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@3.10.10
3 info using node@v6.10.2
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: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
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 silly lifecycle magicmirror@2.1.1~start: Returned: code: 1 signal: null
13 info lifecycle magicmirror@2.1.1~start: Failed to exec start script
14 verbose stack Error: magicmirror@2.1.1 start:sh run-start.sh
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:886:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid magicmirror@2.1.1
16 verbose cwd /home/pi/MagicMirror
17 error Linux 4.4.50-v7+
18 error argv “/usr/bin/nodejs” “/usr/bin/npm” “start”
19 error node v6.10.2
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error magicmirror@2.1.1 start:sh run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.1.1 start script ‘sh run-start.sh’.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the magicmirror package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error sh run-start.sh
23 error You can get information on how to open an issue for this project with:
23 error npm bugs magicmirror
23 error Or if that isn’t available, you can get their info via:
23 error npm owner ls magicmirror
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]Hoping for help
Wippo -
@Wippo said in MagicMirror fails to start after fresh install:
Hoping for help
Starting using
pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm startImportant:
npm startdoes not work via SSH, useDISPLAY=:0 nohup npm start &instead. This starts the mirror on the remote display.Are you starting the mirror via SSH? If you are then the command is
DISPLAY=:0 nohup npm start &in yourMagicMirrordirectory.If you are directly connected to your Pi3 then the command is simply
npm startin yourMagicMirrordirectory. -
Thanks for your advice, but that’s not the reason. I checked it again and the results are the same, independent of starting via SSH or directly.
Now solved.
“npm start” has to be executed after starting the graphic desktopWippo
-
This post is deleted! -
@Wippo Hey! I’m having a similar error message to you. What did you do to solve it?
-
@longod Hi, you have to start the graphic desktop before execution of “npm start” (or similar) from a console. My error was to stop system start at console level.
Wippo
-
@wippo Hi - can you be more detailed when you say “you have to start the graphic desktop before execution”? I am pretty new to this and have no idea what you mean. I have the exact same errors on the same set up you have. Thank you.
-
Hi,
after powering on the Raspi and waiting a while, you have either a “console” (white letters on a black screen) or graphic desktop (colors and symbols like “Windows”). What you need for the Magic Mirror is the desktop. You can change the boot behavior using “sudo raspi-config”.Wippo
-
Thank you. I actually did a new complete install from scratch and got MM to work!
