Read the statement by Michael Teeuw here.
Failed at the magicmirror@2.7.1 start script.
-
Hi, I am running Ubuntu Touch on a Nexus 7 (2013) I am stuck here and have tried everything and I have no idea what the problem is?
magicmirror@2.7.1 start /home/phablet/MagicMirror
sh run-start.shnpm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.7.1 start: ‘sh run-start.sh’
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.7.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in:
npm ERR! /home/phablet/.npm/_logs/2019-06-25T21_41_02_288Z-debug.log -
This post is deleted! -
Can u tell us the versions of node and npm?
node -v
npm -vYou did an npm install after the git clone or file unzip, right?
-
Hi,
Yes I did an npm install after git clonenode version - v10.16.
npm version - 6.9.0 -
@vdotjay does this file contain any additional info
/home/phablet/.npm/_logs/2019-06-25T21_41_02_288Z-debug.log
-
@vdotjay also, did u install any other modules prior to starting the mirror app?
-
@sdetweil
Hi, this is from the log0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/local/bin/node’, ‘/usr/local/bin/npm’, ‘start’ ]
2 info using npm@6.9.0
3 info using node@v10.16.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.7.1~prestart: magicmirror@2.7.1
6 info lifecycle magicmirror@2.7.1~start: magicmirror@2.7.1
7 verbose lifecycle magicmirror@2.7.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.7.1~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/phablet/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
9 verbose lifecycle magicmirror@2.7.1~start: CWD: /home/phablet/MagicMirror
10 silly lifecycle magicmirror@2.7.1~start: Args: [ ‘-c’, ‘sh run-start.sh’ ]
11 silly lifecycle magicmirror@2.7.1~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.7.1~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.7.1 start:sh run-start.sh
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid magicmirror@2.7.1
15 verbose cwd /home/phablet/MagicMirror
16 verbose Linux 3.4.0-6-flo
17 verbose argv “/usr/local/bin/node” “/usr/local/bin/npm” “start”
18 verbose node v10.16.0
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.7.1 start:sh run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.7.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ] -
ok, looking thru search results i find this process
https://stackoverflow.com/questions/42308879/npm-err-code-elifecycle114 (upvotes) (from the MagicMirror folder) Step 1: $ npm cache clean --force Step 2: Delete node_modules by $ rm -rf node_modules folder or delete it manually by going into the directory and right-click > delete. Step 2a: Delete package-lock.json file too. Step 3: npm install To start again, $ npm start -
@sdetweil Okay thank you i’ll try it now
-
Hi, I get the same error this is the log file
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@6.9.0
3 info using node@v10.16.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.7.1~prestart: magicmirror@2.7.1
6 info lifecycle magicmirror@2.7.1~start: magicmirror@2.7.1
7 verbose lifecycle magicmirror@2.7.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.7.1~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/phablet/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
9 verbose lifecycle magicmirror@2.7.1~start: CWD: /home/phablet/MagicMirror
10 silly lifecycle magicmirror@2.7.1~start: Args: [ ‘-c’, ‘sh run-start.sh’ ]
11 silly lifecycle magicmirror@2.7.1~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.7.1~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.7.1 start:sh run-start.sh
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid magicmirror@2.7.1
15 verbose cwd /home/phablet/MagicMirror
16 verbose Linux 3.4.0-6-flo
17 verbose argv “/usr/local/bin/node” “/usr/local/bin/npm” “start”
18 verbose node v10.16.0
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.7.1 start:sh run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.7.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ] -
@vdotjay ok, does sh exist? and electron?
ls ~/MagicMirror/node_modules/electron/dist -
sh is a command which is runing on unix systems (such as macos, linux) do you try that on a windows machine?
-
@nischi he is running ubuntu linux
-
@sdetweil oh i only read the error, my fault, sorry.
-
@sdetweil Hi.
Electron is there but Sh isn’t -
-
Hi, sorry yes lowercase sh
-
also, looks like a known restriction
https://askubuntu.com/questions/646655/ubuntu-touch-executable-files-wont-launch-in-home-directory
-
u can also try changing package.json
"scripts": { "start": "sh run-start.sh", //< --- to "start": "bash run-start.sh",if the security thing is right
-
Okay thank you I will try it
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login