Fresh install but pm2 error

sdetweil

@Hubschra01 that looks good now, right?

Hubschra01

@sdetweil
I think so, if this below is not an Error.
But what caused the error or what was the mistake?

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | + arch=armv7l
0|MagicMir | + false=false
0|MagicMir | ++ grep -i serveronly:
0|MagicMir | ++ awk '{print tolower($2)}'
0|MagicMir | ++ tr -d ',"'\'''
0|MagicMir | ++ grep -v '^\s//' config/config.js
0|MagicMir | + serveronly=
0|MagicMir | + serveronly=false
0|MagicMir | ++ pgrep Xorg
0|MagicMir | + xorg=429
0|MagicMir | ++ uname
0|MagicMir | + mac=Linux
0|MagicMir | + '[' false. '!=' false. -o armv7l == armv6l ']'
0|MagicMir | + '[' 429. == . -a Linux '!=' Darwin ']'
0|MagicMir | + electron js/electron.js

sdetweil

@Hubschra01 u can remove the -x from run-start.sh 1st line.

That is just debugging

Hubschra01

@sdetweil
Strange…
I flushed the log and i remove the -x from the run-start.sh.
after reboot i see this in the log again.

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | npm ERR! code ELIFECYCLE
0|MagicMir | npm ERR! errno 1
0|MagicMir | npm ERR! magicmirror@2.10.1 start: `./run-start.sh`
0|MagicMir | npm ERR! Exit status 1
0|MagicMir | npm ERR!
0|MagicMir | npm ERR! Failed at the magicmirror@2.10.1 start script.
0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
0|MagicMir |
0|MagicMir | npm ERR! A complete log of this run can be found in:
0|MagicMir | npm ERR!     /home/pi/.npm/_logs/2020-01-21T16_37_02_810Z-debug.log

/home/pi/.npm/_logs/2020-01-21T16_37_02_810Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@6.13.4
3 info using node@v10.18.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.10.1~prestart: magicmirror@2.10.1
6 info lifecycle magicmirror@2.10.1~start: magicmirror@2.10.1
7 verbose lifecycle magicmirror@2.10.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.10.1~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.10.1~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.10.1~start: Args: [ '-c', './run-start.sh' ]
11 silly lifecycle magicmirror@2.10.1~start: Returned: code: 1  signal: null
12 info lifecycle magicmirror@2.10.1~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.10.1 start: `./run-start.sh`
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:198:13)
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: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.10.1
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 4.19.75-v7+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v10.18.1
19 verbose npm  v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.10.1 start: `./run-start.sh`
22 error Exit status 1
23 error Failed at the magicmirror@2.10.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 ]

weird:pouting_face:

sdetweil

@Hubschra01 and the mirror did not start?

Hubschra01

@sdetweil
The Mirror start an work fine now. :-) Thanks to you
So i have to consider the error in the log as normal?

sdetweil

@Hubschra01 i wonder if that is the shutdown log, on the reboot…

but there should be more on restart

Hubschra01

@sdetweil
if i understand you right your oppinion is that this error meassage is the shutdown message and not a start up error?

sdetweil

@Hubschra01 yes
do

pm2 logs --lines=100

Hubschra01

@sdetweil
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)