Fresh install but pm2 error

Hubschra01 · Jan 16, 2020, 9:44 AM

Hi,
I do a fresh install of the MagicMirror 2. The Mirror seem to work if i look in the logs of pm2 there is show an error.
I searched the forum but found nothing suitableI.
What kind of error is this?
The Hardware is a Pi 3B+ with SD card.

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 ]

Thanks André

sdetweil · Jan 16, 2020, 1:09 PM

@Hubschra01 if you do the start manually what happens

pm2 stop 0
cd ~/MagicMirror
npm start

Hubschra01 · Jan 17, 2020, 6:37 AM

I think there are no Errors…


> magicmirror@2.10.1 start /home/pi/MagicMirror
> ./run-start.sh

[07:31:12.357] [LOG]    Starting MagicMirror: v2.10.1
[07:31:12.375] [LOG]    Loading config ...
[07:31:12.387] [LOG]    Loading module helpers ...
[07:31:12.389] [LOG]    No helper found for module: alert.
[07:31:12.465] [LOG]    Initializing new module helper ...
[07:31:12.466] [LOG]    Module helper loaded: updatenotification
[07:31:12.468] [LOG]    No helper found for module: clock.
[07:31:13.307] [LOG]    Initializing new module helper ...
[07:31:13.308] [LOG]    Module helper loaded: calendar
[07:31:13.309] [LOG]    No helper found for module: currentweather.
[07:31:13.310] [LOG]    No helper found for module: weatherforecast.
[07:31:13.367] [LOG]    Initializing new module helper ...
[07:31:13.368] [LOG]    Module helper loaded: newsfeed
[07:31:13.369] [LOG]    All module helpers loaded.
[07:31:13.371] [LOG]    Starting server on port 8080 ...
[07:31:13.393] [LOG]    Server started ...
[07:31:13.395] [LOG]    Connecting socket for: updatenotification
[07:31:13.397] [LOG]    Connecting socket for: calendar
[07:31:13.398] [LOG]    Starting node helper for: calendar
[07:31:13.399] [LOG]    Connecting socket for: newsfeed
[07:31:13.401] [LOG]    Starting module: newsfeed
[07:31:13.401] [LOG]    Sockets connected & modules started ...
[07:31:13.625] [LOG]    Launching application.
[07:31:16.629] [LOG]    Create new calendar fetcher for url: https://calendar.google.com/calendarX - Interval: 30000
[07:31:16.654] [LOG]    Create new calendar fetcher for url: https://calendar.google.com/XX - Interval: 30000
[07:31:16.762] [LOG]    Create new news fetcher for url: http://www.tagesschau.de/xml/rss2 - Interval: 300000
^C

But on the Mirror there is only the Desktop from Buster shown, not the Mirror Screen

sdetweil · Jan 17, 2020, 12:19 PM

@Hubschra01 how are you connecting to the pi? over ssh?

did u set DISPLAY=:0

Hubschra01 · Jan 20, 2020, 4:06 AM

@sdetweil
sorry i forget this.
This is the CLI output i tried now.

pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start

> magicmirror@2.10.1 start /home/pi/MagicMirror
> ./run-start.sh

[23:11:47.885] [LOG]    Starting MagicMirror: v2.10.1
[23:11:47.902] [LOG]    Loading config ...
[23:11:47.911] [LOG]    Loading module helpers ...
[23:11:47.914] [LOG]    No helper found for module: alert.
[23:11:48.008] [LOG]    Initializing new module helper ...
[23:11:48.010] [LOG]    Module helper loaded: updatenotification
[23:11:48.012] [LOG]    No helper found for module: clock.
[23:11:48.875] [LOG]    Initializing new module helper ...
[23:11:48.876] [LOG]    Module helper loaded: calendar
[23:11:48.877] [LOG]    No helper found for module: currentweather.
[23:11:48.878] [LOG]    No helper found for module: weatherforecast.
[23:11:48.935] [LOG]    Initializing new module helper ...
[23:11:48.936] [LOG]    Module helper loaded: newsfeed
[23:11:48.937] [LOG]    All module helpers loaded.
[23:11:48.939] [LOG]    Starting server on port 8080 ...
[23:11:48.962] [LOG]    Server started ...
[23:11:48.964] [LOG]    Connecting socket for: updatenotification
[23:11:48.966] [LOG]    Connecting socket for: calendar
[23:11:48.967] [LOG]    Starting node helper for: calendar
[23:11:48.969] [LOG]    Connecting socket for: newsfeed
[23:11:48.970] [LOG]    Starting module: newsfeed
[23:11:48.971] [LOG]    Sockets connected & modules started ...
[23:11:49.186] [LOG]    Launching application.
[23:11:52.113] [LOG]    Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/XXX/basic.ics - Interval: 30000
[23:11:52.265] [LOG]    Create new calendar fetcher for url: https://calendar.google.com/calendar/XXXX - Interval: 30000
[23:11:52.331] [LOG]    Create new news fetcher for url: http://www.tagesschau.de/xml/rss2 - Interval: 300000

sdetweil · Jan 20, 2020, 4:06 AM

@Hubschra01 good, thank you

last time you said

But on the Mirror there is only the Desktop from Buster shown, not the Mirror Screen

did the mirror app display correctly on the display this time? looks like it should have

Hubschra01 · Jan 20, 2020, 8:59 AM

Yes it did.
I Start the Mirror again with

pm2 restart MagicMirror

and it works.
Next step i flush the pm2 log and restart pm2 again.
All works fine no errors.

But if i reboot the pi the error appear again in the pm2 log…

sdetweil · Jan 20, 2020, 1:25 PM

@Hubschra01

ok do

pm2 start  MagicMirror
pm2 save

Hubschra01 · Jan 20, 2020, 2:16 PM

@sdetweil
OK i did it. what else?
if i reboot pm2 log show this.

pi@raspberrypi:~ $ pm2 log
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2        | 2020-01-20T15:12:28: PM2 log: PM2 version          : 4.2.1
PM2        | 2020-01-20T15:12:28: PM2 log: Node.js version      : 10.18.1
PM2        | 2020-01-20T15:12:28: PM2 log: Current arch         : arm
PM2        | 2020-01-20T15:12:28: PM2 log: PM2 home             : /home/pi/.pm2
PM2        | 2020-01-20T15:12:28: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
PM2        | 2020-01-20T15:12:28: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
PM2        | 2020-01-20T15:12:28: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
PM2        | 2020-01-20T15:12:28: PM2 log: Application log path : /home/pi/.pm2/logs
PM2        | 2020-01-20T15:12:28: PM2 log: Worker Interval      : 30000
PM2        | 2020-01-20T15:12:28: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
PM2        | 2020-01-20T15:12:28: PM2 log: Concurrent actions   : 2
PM2        | 2020-01-20T15:12:28: PM2 log: SIGTERM timeout      : 1600
PM2        | 2020-01-20T15:12:28: PM2 log: ===============================================================================
PM2        | 2020-01-20T15:12:28: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2020-01-20T15:12:28: PM2 log: App [MagicMirror:0] online

/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-20T14_12_10_107Z-debug.log

/home/pi/.pm2/logs/MagicMirror-out.log last 15 lines:
0|MagicMir | [15:12:38.792] [LOG]    Initializing new module helper ...
0|MagicMir | [15:12:38.793] [LOG]    Module helper loaded: newsfeed
0|MagicMir | [15:12:38.794] [LOG]    All module helpers loaded.
0|MagicMir | [15:12:38.795] [LOG]    Starting server on port 8080 ...
0|MagicMir | [15:12:38.819] [LOG]    Server started ...
0|MagicMir | [15:12:38.820] [LOG]    Connecting socket for: updatenotification
0|MagicMir | [15:12:38.822] [LOG]    Connecting socket for: calendar
0|MagicMir | [15:12:38.823] [LOG]    Starting node helper for: calendar
0|MagicMir | [15:12:38.825] [LOG]    Connecting socket for: newsfeed
0|MagicMir | [15:12:38.826] [LOG]    Starting module: newsfeed
0|MagicMir | [15:12:38.827] [LOG]    Sockets connected & modules started ...
0|MagicMir | [15:12:39.460] [LOG]    Launching application.
0|MagicMir | [15:12:43.347] [LOG]    Create new calendar fetcher for url: https:

sdetweil · Jan 20, 2020, 2:23 PM

@Hubschra01 said in Fresh install but pm2 error:

/home/pi/.npm/_logs/2020-01-20T14_12_10_107Z-debug.log

weird…

can u show that log
/home/pi/.npm/_logs/2020-01-20T14_12_10_107Z-debug.log