@sdetweil
I do NOT think the sd card is the reason here. I tried the following.
Took a completely new second 32GB card, on which I installed MM 2.13.0 in december 2020. This card did only run for some hours in december. Pi came up and MM runs manually started with
DISPLAY=:0 npm start
for about half an hour.
Then I decided to update MM (this was the fault here… :-( )
After Upgrading MM to 2.15.0 (and updating all modules) the same problem occurs with this card!
pi@mirror:~/MagicMirror $ DISPLAY=:0 npm start
> magicmirror@2.15.0 start /home/pi/MagicMirror
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
[23.04.2021 00:04.37.808] [LOG] Starting MagicMirror: v2.15.0
[23.04.2021 00:04.37.827] [LOG] Loading config ...
[23.04.2021 00:04.46.211] [LOG] Starting node helper for: MMM-Remote-Control
[23.04.2021 00:04.46.259] [LOG] MMM-MQTT: Starting node helper
[23.04.2021 00:04.46.264] [LOG] Starting node_helper for module: MyCovid19
[23.04.2021 00:05.18.598] [LOG] MMM-MQTT: Starting client for: {
*** skipped same lines here ***
}
[23.04.2021 00:05.18.626] [LOG] MMM-MQTT: Connecting to mqtt://moon.fritz.box:1883
[23.04.2021 00:05.22.193] [LOG] MMM-MQTT connected to mqtt://moon.fritz.box:1883
[23.04.2021 00:05.22.202] [LOG] MMM-MQTT: subscribing to sensor/wemos-schuppen-temp
[23.04.2021 00:05.22.563] [ERROR] Failed to fetch git data for MyCovid19: Error: block timeout reached
[23.04.2021 00:05.23.732] [ERROR] Failed to fetch git data for MMM-homeassistant-sensors: Error: block timeout reached
[23.04.2021 00:05.25.023] [ERROR] Failed to fetch git data for MMM-MQTT: Error: block timeout reached
[23.04.2021 00:05.26.530] [ERROR] Failed to fetch git data for MMM-PIR-Sensor: Error: block timeout reached
[23.04.2021 00:05.34.347] [ERROR] Failed to fetch git data for MMM-Remote-Control: Error: block timeout reached
[23.04.2021 00:05.35.557] [ERROR] Failed to fetch git data for default: Error: block timeout reached
<--- Last few GCs --->
[7523:0x77c8000] 113993 ms: Scavenge 210.7 (221.1) -> 210.2 (221.6) MB, 29.0 / 0.0 ms (average mu = 0.795, current mu = 0.754) task
[7523:0x77c8000] 114350 ms: Scavenge (reduce) 211.9 (221.9) -> 211.3 (220.1) MB, 103.9 / 0.0 ms (average mu = 0.795, current mu = 0.754) allocation failure
[7523:0x77c8000] 114759 ms: Scavenge (reduce) 212.8 (220.6) -> 212.3 (220.9) MB, 134.6 / 0.0 ms (average mu = 0.795, current mu = 0.754) allocation failure
<--- JS stacktrace --->
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.15.0 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/pi/.npm/_logs/2021-04-22T22_06_32_848Z-debug.log
and the log
pi@mirror:~/MagicMirror $ cat /home/pi/.npm/_logs/2021-04-22T22_06_32_848Z-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.14.8
3 info using node@v10.23.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.15.0~prestart: magicmirror@2.15.0
6 info lifecycle magicmirror@2.15.0~start: magicmirror@2.15.0
7 verbose lifecycle magicmirror@2.15.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.15.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.15.0~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.15.0~start: Args: [ '-c',
10 silly lifecycle 'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js' ]
11 silly lifecycle magicmirror@2.15.0~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.15.0~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.15.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: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.15.0
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 5.4.79-v7+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v10.23.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
22 error Exit status 1
23 error Failed at the magicmirror@2.15.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 ]
Sorry, but this is no accident.
Is there a way to go back to MM 2.13.0?
