A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
Magic Mirror 2 won't start
-
Hey everyone…
I just did a complete Udpate of my pi
sudo apt-get update sudo apt full-upgrade sudo apt cleanI am now on “Raspbian GNU/Linux 9 (stretch)”.
After that i switched to the Magic Mirror Folder and did a
git pullEverything worked like a charm.
But now the Magic Mirror 2 won’t start…I also did a reinstall of pm2 (i used this -> https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror)
“pm2 show mm” gives me:
pi@mirrorpi:~/script $ pm2 show mm Describing process with id 1 - name mm ┌───────────────────┬─────────────────────────────────┐ │ status │ online │ │ name │ mm │ │ namespace │ default │ │ version │ N/A │ │ restarts │ 6845 │ │ uptime │ 0s │ │ script path │ /home/pi/mm.sh │ │ script args │ N/A │ │ error log path │ /home/pi/.pm2/logs/mm-error.log │ │ out log path │ /home/pi/.pm2/logs/mm-out.log │ │ pid path │ /home/pi/.pm2/pids/mm-1.pid │ │ interpreter │ bash │ │ interpreter args │ N/A │ │ script id │ 1 │ │ exec cwd │ /home/pi │ │ exec mode │ fork_mode │ │ node.js version │ N/A │ │ node env │ N/A │ │ watch & reload │ ✘ │ │ unstable restarts │ 0 │ │ created at │ 2020-07-26T14:26:42.028Z │ └───────────────────┴─────────────────────────────────┘ Divergent env variables from local env ┌────────────────┬──────────────────────┐ │ SSH_CONNECTION │ fe80::6d33:b8d3:9d81 │ │ PWD │ /home/pi/.pm2/module │ │ SSH_CLIENT │ fe80::6d33:b8d3:9d81 │ └────────────────┴──────────────────────┘ Add your own code metrics: http://bit.ly/code-metrics Use `pm2 logs mm [--lines 1000]` to display logs Use `pm2 env 1` to display environment variables Use `pm2 monit` to monitor CPU and Memory usage mm Describing process with id 2 - name mm ┌───────────────────┬─────────────────────────────────┐ │ status │ online │ │ name │ mm │ │ namespace │ default │ │ version │ N/A │ │ restarts │ 6841 │ │ uptime │ 0s │ │ script path │ /home/pi/mm.sh │ │ script args │ N/A │ │ error log path │ /home/pi/.pm2/logs/mm-error.log │ │ out log path │ /home/pi/.pm2/logs/mm-out.log │ │ pid path │ /home/pi/.pm2/pids/mm-2.pid │ │ interpreter │ bash │ │ interpreter args │ N/A │ │ script id │ 2 │ │ exec cwd │ /home/pi │ │ exec mode │ fork_mode │ │ node.js version │ N/A │ │ node env │ N/A │ │ watch & reload │ ✘ │ │ unstable restarts │ 0 │ │ created at │ 2020-07-26T14:32:37.082Z │ └───────────────────┴─────────────────────────────────┘ Divergent env variables from local env ┌────────────────┬──────────────────────┐ │ SSH_CONNECTION │ fe80::6d33:b8d3:9d81 │ │ PWD │ /home/pi │ │ SSH_CLIENT │ fe80::6d33:b8d3:9d81 │ └────────────────┴──────────────────────┘ Add your own code metrics: http://bit.ly/code-metrics Use `pm2 logs mm [--lines 1000]` to display logs Use `pm2 env 2` to display environment variables Use `pm2 monit` to monitor CPU and Memory usage mmIf i try to stop and start the mirror i get:
pi@mirrorpi:~/script $ pm2 start mm [PM2] Applying action restartProcessId on app [mm](ids: [ 1, 2 ]) [PM2] [mm](1) ✓ [PM2] [mm](2) ✓ [PM2] Process successfully started ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐ │ id │ name │ mode │ ↺ │ status │ cpu │ memory │ ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤ │ 1 │ mm │ fork │ 6905 │ online │ 0% │ 2.5mb │ │ 2 │ mm │ fork │ 6902 │ online │ 0% │ 2.6mb │ └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘ Module ┌────┬────────────────────┬──────────┬──────────┬──────────┐ │ id │ name │ status │ cpu │ mem │ ├────┼────────────────────┼──────────┼──────────┼──────────┤ │ 0 │ pm2-logrotate │ online │ 0% │ 48.1mb │ └────┴────────────────────┴──────────┴──────────┴──────────┘why do i have 2 id’s??
My startup script looks like this:
cd /~MagicMirror DISPLAY=:0 npm startIf i try to start the mirror manualy, i get:
pi@mirrorpi:~ $ cd ./MagicMirror pi@mirrorpi:~/MagicMirror $ npm start > magicmirror@2.12.0 start /home/pi/MagicMirror > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [2020-07-28 23:54:26.833] [ERROR] App threw an error during load [2020-07-28 23:54:26.861] [ERROR] TypeError: Bind must be called on a function at bind (<anonymous>) at /home/pi/MagicMirror/js/logger.js:32:38 at /home/pi/MagicMirror/js/logger.js:16:20 at Object.<anonymous> (/home/pi/MagicMirror/js/logger.js:21:3) at Object.<anonymous> (/home/pi/MagicMirror/js/logger.js:46:3) at Module._compile (internal/modules/cjs/loader.js:711:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10) at Module.load (internal/modules/cjs/loader.js:620:32) at tryModuleLoad (internal/modules/cjs/loader.js:559:12) at Function.Module._load (internal/modules/cjs/loader.js:551:3) A JavaScript error occurred in the main process Uncaught Exception: TypeError: Bind must be called on a function at bind (<anonymous>) at /home/pi/MagicMirror/js/logger.js:32:38 at /home/pi/MagicMirror/js/logger.js:16:20 at Object.<anonymous> (/home/pi/MagicMirror/js/logger.js:21:3) at Object.<anonymous> (/home/pi/MagicMirror/js/logger.js:46:3) at Module._compile (internal/modules/cjs/loader.js:711:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10) at Module.load (internal/modules/cjs/loader.js:620:32) at tryModuleLoad (internal/modules/cjs/loader.js:559:12) at Function.Module._load (internal/modules/cjs/loader.js:551:3)And now i am at a point where i just don’t know what to do…
Well i could try to update Javascript.The strange thing is: i did this a couple of times - and all the times everything just worked out of the box…
What is going on here?Plus i now have a steady cpu load around 50%…
what the hell?
Looking forward to any suggestions/ideas/etc.
thank you all
stefan
-
@Stef the release notes for this update says that in addition to the git pull, you must also do an npm install in the MagicMirror folder, see
https://forum.magicmirror.builders/topic/13182/v2-12-0in the future, please u the automated update script from here.
https://github.com/sdetweil/MagicMirror_scripts -
@sdetweil Sorry, i forgot about the Release notes…
I did this, the error is gone but i still have around 50% CPU load, the autostart is not working and i have a black screen when i start the mirror manually…
Any ideas?
-
@Stef show the output of
pm2 logs --lines=100
-
@sdetweil well… It did not stop… So I forced it
Linux mirrorpi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Jul 31 18:29:29 2020 from 192.168.0.199 pi@mirrorpi:~ $ pm2 logs --lines=100 [TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option) /home/pi/.pm2/pm2.log last 100 lines: PM2 | 2020-07-31T23:45:34: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:35: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:35: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:35: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:36: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:36: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:36: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:36: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:36: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:37: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:38: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:38: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:38: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:38: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:38: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:38: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:41: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:41: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:41: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:41: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:41: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:41: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:44: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:44: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:44: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:44: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:44: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:44: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:48: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:48: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:48: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:48: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:48: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:48: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:51: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:51: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:51: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:51: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:51: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:51: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:54: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:54: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:54: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:54: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:54: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:54: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:45:57: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:57: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:45:57: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:45:57: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:45:57: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:45:57: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:00: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:00: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:00: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:00: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:00: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:00: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:03: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:03: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:03: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:03: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:03: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:03: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:05: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:05: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:05: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:05: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:05: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:05: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:08: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:08: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:08: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:08: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:08: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:08: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:11: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:11: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:11: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:11: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:11: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:11: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:12: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:12: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:12: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:12: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:12: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:12: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:14: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:14: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:14: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:14: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:14: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:14: PM2 log: App [mm:2] online PM2 | 2020-07-31T23:46:17: PM2 log: App [mm:1] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:17: PM2 log: App [mm:2] exited with code [254] via signal [SIGINT] PM2 | 2020-07-31T23:46:17: PM2 log: App [mm:1] starting in -fork mode- PM2 | 2020-07-31T23:46:17: PM2 log: App [mm:2] starting in -fork mode- PM2 | 2020-07-31T23:46:17: PM2 log: App [mm:1] online PM2 | 2020-07-31T23:46:17: PM2 log: App [mm:2] online /home/pi/.pm2/logs/mm-out.log last 100 lines: /home/pi/.pm2/logs/pm2-logrotate-error.log last 100 lines: 0|pm2-logr | [Error: ENOENT: no such file or directory, unlink '/home/pi/.pm2/logs/mm-error__2020-07-15_00-00-00.log'] { 0|pm2-logr | errno: -2, 0|pm2-logr | code: 'ENOENT', 0|pm2-logr | syscall: 'unlink', 0|pm2-logr | path: '/home/pi/.pm2/logs/mm-error__2020-07-15_00-00-00.log' 0|pm2-logr | } 0|pm2-logr | [Error: ENOENT: no such file or directory, unlink '/home/pi/.pm2/logs/mm-error__2020-07-16_20-14-10.log'] { 0|pm2-logr | errno: -2, 0|pm2-logr | code: 'ENOENT', 0|pm2-logr | syscall: 'unlink', 0|pm2-logr | path: '/home/pi/.pm2/logs/mm-error__2020-07-16_20-14-10.log' 0|pm2-logr | } 0|pm2-logr | [Error: ENOENT: no such file or directory, unlink '/home/pi/.pm2/logs/mm-error__2020-07-17_00-01-34.log'] { 0|pm2-logr | errno: -2, 0|pm2-logr | code: 'ENOENT', 0|pm2-logr | syscall: 'unlink', 0|pm2-logr | path: '/home/pi/.pm2/logs/mm-error__2020-07-17_00-01-34.log' 0|pm2-logr | } 0|pm2-logr | [Error: ENOENT: no such file or directory, unlink '/home/pi/.pm2/logs/mm-error__2020-07-17_13-46-14.log'] { 0|pm2-logr | errno: -2, 0|pm2-logr | code: 'ENOENT', 0|pm2-logr | syscall: 'unlink', 0|pm2-logr | path: '/home/pi/.pm2/logs/mm-error__2020-07-17_13-46-14.log' 0|pm2-logr | } /home/pi/.pm2/logs/pm2-logrotate-out.log last 100 lines: 0|pm2-logr | "/home/pi/.pm2/logs/pm2-logrotate-out__2020-07-31_00-00-13.log" has been created 0|pm2-logr | "/home/pi/.pm2/logs/pm2-logrotate-error__2020-07-31_00-00-13.log" has been created 0|pm2-logr | "pm2-logrotate-out__2020-06-24_00-00-14.log" has been deleted 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_00-00-13.log" has been created 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_00-00-13.log" has been created 0|pm2-logr | "mm-error__2020-07-15_00-00-00.log" has been deleted 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_06-12-22.log" has been created 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_06-12-22.log" has been created 0|pm2-logr | "mm-error__2020-07-16_20-14-10.log" has been deleted 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_12-19-24.log" has been created 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_12-19-24.log" has been created 0|pm2-logr | "mm-error__2020-07-17_00-01-34.log" has been deleted 0|pm2-logr | "/home/pi/.pm2/pm2__2020-07-31_13-01-24.log" has been created 0|pm2-logr | "pm2__2020-06-17_14-07-43.log" has been deleted 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_18-29-27.log" has been created 0|pm2-logr | "/home/pi/.pm2/logs/mm-error__2020-07-31_18-29-27.log" has been created 0|pm2-logr | "mm-error__2020-07-17_13-46-14.log" has been deleted /home/pi/.pm2/logs/mm-error.log last 100 lines: 1|mm | npm ERR! enoent 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | 1|mm | 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_08_015Z-debug.log 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_08_015Z-debug.log 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | npm npm ERR! code ENOENT 1|mm | ERR! code ENOENT 1|mm | npm ERR! syscallnpm ERR! syscall open 1|mm | npm ERR! open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | ERR! errno -2 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | 1|mm | 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_10_895Z-debug.log 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_10_894Z-debug.log 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | npm ERR! code ENOENT 1|mm | npm ERR! syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | npm ERR! code ENOENT 1|mm | npm ERR! syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_12_794Z-debug.log 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_12_823Z-debug.log 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | npm ERR! code ENOENT 1|mm | npm ERR! code ENOENT 1|mm | npm ERR! syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | npm ERR! syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npmnpm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | 1|mm | 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR!npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_14_790Z-debug.log 1|mm | /home/pi/.npm/_logs/2020-07-31T21_46_14_793Z-debug.log 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | npm ERR! code ENOENT 1|mm | npm ERR! syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | npm ERR! code ENOENT 1|mm | npm ERR! npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 1|mm | 1|mm | 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_16_929Z-debug.log 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_16_923Z-debug.log 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | npm 2|mm | npm 1|mm | ERR! code ENOENT 1|mm | npm 1|mm | ERR! syscall open 1|mm | npm ERR! 1|mm | path /home/pi/package.json 2|mm | ERR! code ENOENT 2|mm | npm 1|mm | npm ERR! errno -2 2|mm | ERR! syscall open 2|mm | npm ERR! 2|mm | path /home/pi/package.json 2|mm | npm ERR! errno 2|mm | -2 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent 1|mm | This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 2|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 2|mm | npm ERR! enoent This is related to npm not being able to find a file. 2|mm | npm 2|mm | ERR! enoent 1|mm | npm ERR! A complete log of this run can be found in: 1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_21_246Z-debug.log 2|mm | npm ERR! A complete log of this run can be found in: 2|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_21_253Z-debug.log PM2 | App [mm:1] exited with code [254] via signal [SIGINT] PM2 | App [mm:2] exited with code [254] via signal [SIGINT] PM2 | App [mm:1] starting in -fork mode- PM2 | App [mm:2] starting in -fork mode- PM2 | App [mm:1] online PM2 | App [mm:2] online 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 2|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 1|mm | npm 2|mm | npm ERR! code 1|mm | ERR! code ENOENT 1|mm | npm ERR! syscall open 1|mm | npm ERR! path /home/pi/package.json 1|mm | npm ERR! errno -2 2|mm | ENOENT 2|mm | npm ERR! syscall open 2|mm | npm ERR! path /home/pi/package.json 2|mm | npm ERR! errno -2 2|mm | npm ERR! enoent 2|mm | ENOENT: no such file or directory, open '/home/pi/package.json' 2|mm | npm ERR! enoent This is related to npm not being able to find a file. 2|mm | npm ERR! 1|mm | npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' 1|mm | npm ERR! enoent This is related to npm not being able to find a file. 1|mm | npm ERR! enoent 2|mm | enoent 2|mm | npm ERR! A complete log of this run can be found in:2|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_23_904Z-debug.log 1|mm | npm ERR! A complete log of this run can be found in:1|mm | npm ERR! /home/pi/.npm/_logs/2020-07-31T21_46_23_900Z-debug.log PM2 | App [mm:1] exited with code [254] via signal [SIGINT] PM2 | App [mm:2] exited with code [254] via signal [SIGINT] PM2 | App [mm:1] starting in -fork mode- PM2 | App [mm:2] starting in -fork mode- PM2 | App [mm:1] online PM2 | App [mm:2] online 1|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden 2|mm | /home/pi/mm.sh: Zeile 1: cd: /~MagicMirror: Datei oder Verzeichnis nicht gefunden ^C pi@mirrorpi:~ $ -
@Stef pm2 stop all
pm2 info
for some reason some script is trying to do npm start in the users home folder.
pm2 remove that one (0 or 1)
pm2 save
pm2 flushthen pm2 info, and look at the script being run , examine and test the script.
then pm2 start (0/1 whatever is left)
-
I did all this.
pm2 remove did not work (not recognised as a command) so i did a pm2 delete on both instances.All i get now, is a black screen & an error with the Modul “MMM-DHT-Sensor”
[2020-08-02 17:45:35.346] [ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: The module '/home/pi/MagicMirror/modules/MMM-DHT-Sensor/node_modules/node-dht-sensor/build/Release/node_dht_sensor.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 64. This version of Node.js requires NODE_MODULE_VERSION 73. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`).If i remove the Folder from the modules, the Mirror boots up.
Since the Mirror is loading now, this Topic can be closed and i will open up another one.
Thanks!
-
@Stef great! I can never remember remove vs delete, but u got it, and found the actual problem.
I posted steps in the other topic
