Read the statement by Michael Teeuw here.
Fresh install but pm2 error
-
@Hubschra01 i wonder if that is the shutdown log, on the reboot…
but there should be more on restart
-
@sdetweil
if i understand you right your oppinion is that this error meassage is the shutdown message and not a start up error? -
@Hubschra01 yes
dopm2 logs --lines=100
-
@sdetweil
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)/home/pi/.pm2/logs/MagicMirror-error.log last 100 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/.pm2/logs/MagicMirror-out.log last 100 lines:
0|MagicMir |
0|MagicMir | > magicmirror@2.10.1 start /home/pi/MagicMirror
0|MagicMir | > ./run-start.sh
0|MagicMir |
0|MagicMir |
0|MagicMir | > magicmirror@2.10.1 start /home/pi/MagicMirror
0|MagicMir | > ./run-start.sh
0|MagicMir |
0|MagicMir | [17:37:28.657] [LOG] Starting MagicMirror: v2.10.1
0|MagicMir | [17:37:28.673] [LOG] Loading config …
0|MagicMir | [17:37:28.686] [LOG] Loading module helpers …
0|MagicMir | [17:37:28.689] [LOG] No helper found for module: alert.
0|MagicMir | [17:37:28.825] [LOG] Initializing new module helper …
0|MagicMir | [17:37:28.827] [LOG] Module helper loaded: updatenotification
0|MagicMir | [17:37:28.829] [LOG] No helper found for module: clock.
0|MagicMir | [17:37:30.081] [LOG] Initializing new module helper …
0|MagicMir | [17:37:30.082] [LOG] Module helper loaded: calendar
0|MagicMir | [17:37:30.083] [LOG] No helper found for module: currentweather.
0|MagicMir | [17:37:30.084] [LOG] No helper found for module: weatherforecast.
0|MagicMir | [17:37:30.172] [LOG] Initializing new module helper …
0|MagicMir | [17:37:30.173] [LOG] Module helper loaded: newsfeed
0|MagicMir | [17:37:30.173] [LOG] All module helpers loaded.
0|MagicMir | [17:37:30.175] [LOG] Starting server on port 8080 …
0|MagicMir | [17:37:30.199] [LOG] Server started …
0|MagicMir | [17:37:30.201] [LOG] Connecting socket for: updatenotification
0|MagicMir | [17:37:30.202] [LOG] Connecting socket for: calendar
0|MagicMir | [17:37:30.204] [LOG] Starting node helper for: calendar
0|MagicMir | [17:37:30.205] [LOG] Connecting socket for: newsfeed
0|MagicMir | [17:37:30.206] [LOG] Starting module: newsfeed
0|MagicMir | [17:37:30.207] [LOG] Sockets connected & modules started …
0|MagicMir | [17:37:30.821] [LOG] Launching application. -
@Hubschra01 said in Fresh install but pm2 error:
yeh,
there are two launches,1 ended at 2020-01-21T16_37_02_810Z
1 still running, -
@sdetweil
I restart the Mirror again an no there are no Errors in the Log. :-)
I can´t post the log because Akismet mark this as span… wierdThanks Sam
-
@Hubschra01 no problem… glad we got it working…
–lines=nnn only shows the last nnn lines, so old errors could be above that
-
I Think the errors come if i reboot the Mirror by
sudo reboot
without to stop the mirror.
the log showPM2| 2020-01-22T17:48:05: PM2 log: Stop watching MagicMirror PM2| 2020-01-22T17:48:05: PM2 log: Stopping app:MagicMirror id:0 PM2| 2020-01-22T17:48:05: PM2 log: pid=802 msg=failed to kill - retrying in 100ms PM2| 2020-01-22T17:48:05: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2| 2020-01-22T17:48:05: PM2 log: pid=802 msg=process killed PM2| 2020-01-22T17:48:06: PM2 log: PM2 successfully stopped
If i do this
pm2 stop MagicMirror sudo reboot
after reboot the log show this
PM2| 2020-01-22T17:51:13: PM2 log: pm2 has been killed by signal, dumping process list before exit... PM2| 2020-01-22T17:51:13: PM2 log: Exited peacefully
I can´t post the log because Akismet mark this as spam… wierd
-
@Hubschra01 yes, askimet is a pain…
thanks for your information…
I suspect the other bad failure info is reboot after just npm start