Read the statement by Michael Teeuw here.
MM funktioniert nicht mehr nach Update
-
@NickOne said in MM funktioniert nicht mehr nach Update:
Nach dem Upgrade des Knotens müssen Sie npm install erneut ausführen.cd ~/MagicMirror rm -rf node_modules rm package-lock.json npm install -
Habe mein Backup nochmals zurück gespielt. Da funktioniert auch noch alles. Habe danach das alles ausgeführt was Sie mir geschrieben hatten. Updates laufen durch, aber danach startet MM wieder nicht. Zumindestens nicht optisch. Wenn ich mir aber die Auslastung anschaue, sieht es schon so aus als wäre MM gestartet.
0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@8.19.3 2 info using node@v16.19.0 3 timing npm:load:whichnode Completed in 1ms 4 timing config:load:defaults Completed in 11ms 5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 10ms 6 timing config:load:builtin Completed in 12ms 7 timing config:load:cli Completed in 11ms 8 timing config:load:env Completed in 4ms 9 timing config:load:file:/home/pi/MagicMirror/.npmrc Completed in 0ms 10 timing config:load:project Completed in 9ms 11 timing config:load:file:/home/pi/.npmrc Completed in 1ms 12 timing config:load:user Completed in 2ms 13 timing config:load:file:/usr/etc/npmrc Completed in 1ms 14 timing config:load:global Completed in 2ms 15 timing config:load:validate Completed in 2ms 16 timing config:load:credentials Completed in 8ms 17 timing config:load:setEnvs Completed in 7ms 18 timing config:load Completed in 82ms 19 timing npm:load:configload Completed in 83ms 20 timing npm:load:mkdirpcache Completed in 8ms 21 timing npm:load:mkdirplogs Completed in 2ms 22 verbose title npm start 23 verbose argv "start" 24 timing npm:load:setTitle Completed in 9ms 25 timing config:load:flatten Completed in 20ms 26 timing npm:load:display Completed in 27ms 27 verbose logfile logs-max:10 dir:/home/pi/.npm/_logs 28 verbose logfile /home/pi/.npm/_logs/2023-01-15T14_41_15_770Z-debug-0.log 29 timing npm:load:logFile Completed in 82ms 30 timing npm:load:timers Completed in 0ms 31 timing npm:load:configScope Completed in 1ms 32 timing npm:load Completed in 221ms 33 silly logfile start cleaning logs, removing 1 files 34 silly logfile done cleaning log files 35 timing command:run-script Completed in 913ms 36 timing command:start Completed in 941ms 37 verbose exit 127 38 timing npm Completed in 1200ms 39 verbose code 127 -
-
@sdetweil ja ich benutze den Autostart.
Aber MM von Hand starten bringt aber auch nichts. Was mir aber aufgefallen ist, das wenn ich MM über die Console starte, hinten in der Tabelle bei “Watching” disable ausgegeben wird.
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────── ─┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ N/A │ 2.22.0 │ fork │ 8302 │ 0s │ 10 │ online │ 0% │ 2.5mb │ pi │ disabled -
@NickOne said in MM funktioniert nicht mehr nach Update:
Das Überwachen von Dateiänderungen wird nicht auf allen Plattformen unterstützt. (Wenn Sie config.js ändern und speichern, wird mm neu gestartet) …
Wie gesagt, ich muss die Ausgabe der Protokolle sehen.
Bitte
pm2 stop all pm2 flush pm2 start MagicMirror 20 Sekunden warten pm2 logs --lines=100 >somefile.txt ctrl-c und Beispiel somefile.txt -
Meinen Sie das hier?
0|MagicMirror | /home/pi/MagicMirror/node_modules/electron/dist/electron: symbol lookup error: /home/pi/MagicMirror/node_modules/electron/dist/electron: undefined symbol: gbm_bo_get_modifier
PM2 | App [MagicMirror:0] exited with code [127] via signal [SIGINT]
PM2 | App [MagicMirror:0] starting in -fork mode-
PM2 | TypeError [ERR_INVALID_ARG_TYPE]: The “data” argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number (16302)
PM2 | at Object.writeFileSync (node:fs:2195:5)
PM2 | at /usr/lib/node_modules/pm2/lib/God/ForkMode.js:258:12
PM2 | at wrapper (/usr/lib/node_modules/pm2/node_modules/async/internal/once.js:12:16)
PM2 | at next (/usr/lib/node_modules/pm2/node_modules/async/waterfall.js:96:20)
PM2 | at /usr/lib/node_modules/pm2/node_modules/async/internal/onlyOnce.js:12:16
PM2 | at WriteStream. (/usr/lib/node_modules/pm2/lib/Utility.js:186:13)
PM2 | at WriteStream.emit (node:events:513:28)
PM2 | at WriteStream.emit (node:domain:552:15)
PM2 | at node:internal/fs/streams:75:16
PM2 | at FSReqCallback.oncomplete (node:fs:192:23)
PM2 | App [MagicMirror:0] online -
@NickOne said in MM funktioniert nicht mehr nach Update:
0|MagicMirror | /home/pi/MagicMirror/node_modules/electron/dist/electron: symbol lookup error: /home/pi/MagicMirror/node_modules/electron/dist/electron: undefined symbol: gbm_bo_get_modifier
thank you
one more command
lsb_release -a
but likely
-
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.11 (stretch)
Release: 9.11
Codename: stretch -
@NickOne yes, latest MM release will not run on stretch.
only fix is to flash a new sd card and re-setup the mirror
my backup/restore scripts could help minimize the work …
https://github.com/sdetweil/MagicMirror-backup-restoreyou can run them from the web, save the changes to github and then restore from there
(after installing MM on a new sd card)
https://github.com/sdetweil/MagicMirror_scriptsI have just updated my upgrade script to NOT upgrade on stretch systems
at least give u time to figure out what to do , not break your MM setup -
Okay, vielen Dank für Ihre Hilfe. Dann werde ich wohl alles neu machen dürfen. Danke für die Links zum backup-restore script. Mal schauen ob ich das alles hinbekomme.
Schön Abend Ihnen!
