MMM 2.18 - NPM? Electron? Silly lifecycle? no MMM

OberfragGER

@karsten13 I have used the “rguglar way” with

git pull && npm install

In which folder do i have to perform this coommands? Regular MagicMirror-Folder?

karsten13

@oberfragger yes, in the mm folder

kai

Hi @karsten13,
I had the same problem like @OberfragGER on one of my MMs and I did the clean reinstall you recommended.
It worked well for me, perfect! Thanks a lot! :thumbs_up_medium-light_skin_tone:

OberfragGER

@karsten13 I have reinstalled it.
Lets wait and cross fingers.

OberfragGER

@karsten13 Still problems.

Now the mirror hangs about 2-3 times a day… :(

|MagicMirror  | Invalid MIT-MAGIC-COOKIE-1 key
0|MagicMirror  | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP
0|MagicMirror  | npm
0|MagicMirror  |  ERR! code ELIFECYCLE
0|MagicMirror  | npm ERR! errno
0|MagicMirror  |  1
0|MagicMirror  | npm ERR!
0|MagicMirror  |  magicmirror@2.18.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
0|MagicMirror  | npm ERR! Exit status 1
0|MagicMirror  | npm ERR!
0|MagicMirror  | npm ERR! Failed at the magicmirror@2.18.0 start script.
0|MagicMirror  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
0|MagicMirror  | npm ERR! A complete log of this run can be found in:
0|MagicMirror  | npm ERR!     /home/pi/.npm/_logs/2022-01-14T11_11_15_580Z-debug.log
0|MagicMirror  | > magicmirror@2.18.0 start /home/pi/MagicMirror
0|MagicMirror  | > DISPLAY="${DISPLAY:=:0}" ./node_modules/

Thats in the log-File:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@6.14.15
3 info using node@v14.18.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.18.0~prestart: magicmirror@2.18.0
6 info lifecycle magicmirror@2.18.0~start: magicmirror@2.18.0
7 verbose lifecycle magicmirror@2.18.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.18.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/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
9 verbose lifecycle magicmirror@2.18.0~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.18.0~start: Args: [
10 silly lifecycle   '-c',
10 silly lifecycle   'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js'
10 silly lifecycle ]
11 silly lifecycle magicmirror@2.18.0~start: Returned: code: 1  signal: null
12 info lifecycle magicmirror@2.18.0~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.18.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:400:28)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:400:28)
13 verbose stack     at maybeClose (internal/child_process.js:1058:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid magicmirror@2.18.0
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 5.10.63-v7l+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v14.18.3
19 verbose npm  v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.18.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
22 error Exit status 1
23 error Failed at the magicmirror@2.18.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

mumblebaj

@oberfragger said in MMM 2.18 - NPM? Electron? Silly lifecycle? no MMM:

18 verbose node v14.18.3
19 verbose npm v6.14.15

You may want to update your node and npm versions.

karsten13

@mumblebaj

its worth a try …

could also caused by a module.