Read the statement by Michael Teeuw here.
MM on Pi Zero fails after being off for a few days
-
It does however load fine if i remotely connect to the url for my MM on another computer.
sounds like its trying to start a second time, and failing… (cause the 1st time is running , maybe in serveronly mode?_
use ssh into the pi, and use whatever mechanism to stop mirror app…
pm2, whatever autostart process…IF you reinstall, I suggest you use my install script…
see here
https://github.com/sdetweil/MagicMirror_scriptsdoes all the work.
what starts this? pm2? pm2 logs --lines=100 will show the logs
-
@sdetweil said in MM on Pi Zero fails after being off for a few days:
pm2 logs --lines=100
Here’s the last 100 lines of the pm2 log, with a few of the first PM2 lines removed as they were identical :-
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option) /home/pi/.pm2/pm2.log last 100 lines: PM2 | 2020-03-29T09:27:24: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:27:58: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:27:58: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:27:58: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:28:32: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:28:32: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:28:32: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:29:05: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:29:05: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:29:05: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:29:42: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:29:42: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:29:42: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:30:16: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:30:16: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:30:16: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:30:49: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:30:49: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:30:49: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:31:23: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:31:23: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:31:23: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:31:57: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:31:57: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:31:57: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:32:31: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:32:31: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:32:31: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:33:04: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:33:04: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:33:04: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:33:38: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:33:38: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:33:38: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:34:12: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:34:12: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:34:12: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:34:48: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:34:48: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:34:48: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:35:24: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:35:24: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:35:24: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:35:58: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:35:58: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:35:58: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:36:32: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:36:32: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:36:32: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:37:06: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:37:06: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:37:06: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:44:58: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:44:58: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:44:58: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:45:35: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:45:35: PM2 log: App [mmstart:0] starting in -fork mode- PM2 | 2020-03-29T09:45:35: PM2 log: App [mmstart:0] online PM2 | 2020-03-29T09:46:01: PM2 log: Stopping app:mmstart id:0 PM2 | 2020-03-29T09:46:02: PM2 log: App [mmstart:0] exited with code [0] via signal [SIGINT] PM2 | 2020-03-29T09:46:02: PM2 log: pid=27183 msg=process killed /home/pi/.pm2/logs/mmstart-error.log last 100 lines: 0|mmstart | at Function.Module.runMain (internal/modules/cjs/loader.js:832:11) 0|mmstart | at startup (internal/bootstrap/node.js:283:19) 0|mmstart | at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3) 0|mmstart | code: 'EADDRINUSE', 0|mmstart | errno: 'EADDRINUSE', 0|mmstart | syscall: 'listen', 0|mmstart | address: '0.0.0.0', 0|mmstart | port: 8080 } 0|mmstart | 0|mmstart | 0|mmstart | X.Org X Server 1.20.4 0|mmstart | X Protocol Version 11, Revision 0 0|mmstart | Build Operating System: Linux 4.15.0-48-generic armv8l Raspbian 0|mmstart | Current Operating System: Linux KitchenPi 4.19.75+ #1270 Tue Sep 24 18:38:54 BST 2019 armv6l 0|mmstart | Kernel command line: coherent_pool=1M bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:A6:3B vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 conso$ 0|mmstart | Build Date: 05 June 2019 12:49:54PM 0|mmstart | xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support) 0|mmstart | Current version of pixman: 0.36.0 0|mmstart | Before reporting problems, check http://wiki.x.org 0|mmstart | to make sure that you have the latest version. 0|mmstart | Markers: (--) probed, (**) from config file, (==) default setting, 0|mmstart | (++) from command line, (!!) notice, (II) informational, 0|mmstart | (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 0|mmstart | (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 29 09:44:21 2020 0|mmstart | (==) Using system config directory "/usr/share/X11/xorg.conf.d" 0|mmstart | /home/pi/chromium_start.sh: 7: /home/pi/chromium_start.sh: chromium-browser: not found 0|mmstart | xinit: connection to X server lost 0|mmstart | 0|mmstart | waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. 0|mmstart | 0|mmstart | [09:44:38.366] [ERROR] { Error: listen EADDRINUSE: address already in use 0.0.0.0:8080 0|mmstart | at Server.setupListenHandle [as _listen2] (net.js:1279:14) 0|mmstart | at listenInCluster (net.js:1327:12) 0|mmstart | at doListen (net.js:1460:7) 0|mmstart | at process._tickCallback (internal/process/next_tick.js:63:19) 0|mmstart | at Function.Module.runMain (internal/modules/cjs/loader.js:832:11) 0|mmstart | at startup (internal/bootstrap/node.js:283:19) 0|mmstart | at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3) 0|mmstart | code: 'EADDRINUSE', 0|mmstart | errno: 'EADDRINUSE', 0|mmstart | syscall: 'listen', 0|mmstart | address: '0.0.0.0', 0|mmstart | port: 8080 } 0|mmstart | 0|mmstart | 0|mmstart | X.Org X Server 1.20.4 0|mmstart | X Protocol Version 11, Revision 0 0|mmstart | Build Operating System: Linux 4.15.0-48-generic armv8l Raspbian 0|mmstart | Current Operating System: Linux KitchenPi 4.19.75+ #1270 Tue Sep 24 18:38:54 BST 2019 armv6l 0|mmstart | Kernel command line: coherent_pool=1M bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:A6:3B v$ 0|mmstart | Build Date: 05 June 2019 12:49:54PM 0|mmstart | xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support) 0|mmstart | Current version of pixman: 0.36.0 0|mmstart | Before reporting problems, check http://wiki.x.org 0|mmstart | to make sure that you have the latest version. 0|mmstart | Markers: (--) probed, (**) from config file, (==) default setting, 0|mmstart | (++) from command line, (!!) notice, (II) informational, 0|mmstart | (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 0|mmstart | (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 29 09:44:55 2020 0|mmstart | (==) Using system config directory "/usr/share/X11/xorg.conf.d" 0|mmstart | /home/pi/chromium_start.sh: 7: /home/pi/chromium_start.sh: chromium-browser: not found 0|mmstart | xinit: connection to X server lost 0|mmstart | 0|mmstart | waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. 0|mmstart | 0|mmstart | [09:45:20.571] [ERROR] { Error: listen EADDRINUSE: address already in use 0.0.0.0:8080 0|mmstart | at Server.setupListenHandle [as _listen2] (net.js:1279:14) 0|mmstart | at listenInCluster (net.js:1327:12) 0|mmstart | at doListen (net.js:1460:7) 0|mmstart | at process._tickCallback (internal/process/next_tick.js:63:19) 0|mmstart | at Function.Module.runMain (internal/modules/cjs/loader.js:832:11) 0|mmstart | at startup (internal/bootstrap/node.js:283:19) 0|mmstart | at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3) 0|mmstart | code: 'EADDRINUSE', 0|mmstart | errno: 'EADDRINUSE', 0|mmstart | syscall: 'listen', 0|mmstart | address: '0.0.0.0', 0|mmstart | port: 8080 } 0|mmstart | 0|mmstart | 0|mmstart | X.Org X Server 1.20.4 0|mmstart | X Protocol Version 11, Revision 0 0|mmstart | Build Operating System: Linux 4.15.0-48-generic armv8l Raspbian 0|mmstart | Current Operating System: Linux KitchenPi 4.19.75+ #1270 Tue Sep 24 18:38:54 BST 2019 armv6l 0|mmstart | Kernel command line: coherent_pool=1M bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:A6:3B v$ 0|mmstart | Build Date: 05 June 2019 12:49:54PM 0|mmstart | xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support) 0|mmstart | Current version of pixman: 0.36.0 0|mmstart | Before reporting problems, check http://wiki.x.org 0|mmstart | to make sure that you have the latest version. 0|mmstart | Markers: (--) probed, (**) from config file, (==) default setting, 0|mmstart | (++) from command line, (!!) notice, (II) informational, 0|mmstart | (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 0|mmstart | (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 29 09:45:29 2020 0|mmstart | (==) Using system config directory "/usr/share/X11/xorg.conf.d" 0|mmstart | /home/pi/chromium_start.sh: 7: /home/pi/chromium_start.sh: chromium-browser: not found 0|mmstart | xinit: connection to X server lost 0|mmstart | 0|mmstart | waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. 0|mmstart | /home/pi/.pm2/logs/mmstart-out.log last 100 lines: 0|mmstart | [09:44:04.467] [LOG] Initializing new module helper ... 0|mmstart | [09:44:04.475] [LOG] Module helper loaded: calendar 0|mmstart | [09:44:04.956] [LOG] Initializing new module helper ... 0|mmstart | [09:44:04.964] [LOG] Module helper loaded: newsfeed 0|mmstart | [09:44:04.970] [LOG] All module helpers loaded. 0|mmstart | [09:44:04.975] [LOG] Starting server on port 8080 ... 0|mmstart | [09:44:05.117] [INFO] ^[[33mYou're using a full whitelist configuration to allow for all IPs^[[39m 0|mmstart | [09:44:05.181] [LOG] Server started ... 0|mmstart | [09:44:05.191] [LOG] Connecting socket for: updatenotification 0|mmstart | [09:44:05.199] [LOG] Connecting socket for: MMM-DarkSkyForecast 0|mmstart | [09:44:05.207] [LOG] ====================== Starting node_helper for module [MMM-DarkSkyForecast] 0|mmstart | [09:44:05.213] [LOG] Connecting socket for: mmm-suncalc 0|mmstart | [09:44:05.219] [LOG] Starting node_helper for mmm-suncalc: 0|mmstart | [09:44:05.228] [LOG] Connecting socket for: calendar 0|mmstart | [09:44:05.234] [LOG] Starting node helper for: calendar 0|mmstart | [09:44:05.243] [LOG] Connecting socket for: newsfeed 0|mmstart | [09:44:05.249] [LOG] Starting module: newsfeed 0|mmstart | [09:44:05.251] [LOG] Sockets connected & modules started ... 0|mmstart | [09:44:05.254] [LOG] 0|mmstart | Ready to go! Please point your browser to: http://0.0.0.0:8080 0|mmstart | [09:44:05.328] [LOG] Whoops! There was an uncaught exception... 0|mmstart | [09:44:05.388] [LOG] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? 0|mmstart | [09:44:05.393] [LOG] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues 0|mmstart | [09:44:31.284] [LOG] Starting MagicMirror: v2.10.1 0|mmstart | [09:44:31.360] [LOG] Loading config ... 0|mmstart | [09:44:31.398] [LOG] Loading module helpers ... 0|mmstart | [09:44:31.413] [LOG] No helper found for module: alert. 0|mmstart | [09:44:31.758] [LOG] Initializing new module helper ... 0|mmstart | [09:44:31.768] [LOG] Module helper loaded: updatenotification 0|mmstart | [09:44:31.777] [LOG] No helper found for module: clock. 0|mmstart | [09:44:34.609] [LOG] Initializing new module helper ... 0|mmstart | [09:44:34.618] [LOG] Module helper loaded: MMM-DarkSkyForecast 0|mmstart | [09:44:34.649] [LOG] Initializing new module helper ... 0|mmstart | [09:44:34.657] [LOG] Module helper loaded: mmm-suncalc 0|mmstart | [09:44:34.663] [LOG] No helper found for module: calendar_monthly. 0|mmstart | [09:44:37.531] [LOG] Initializing new module helper ... 0|mmstart | [09:44:37.541] [LOG] Module helper loaded: calendar 0|mmstart | [09:44:37.947] [LOG] Initializing new module helper ... 0|mmstart | [09:44:37.955] [LOG] Module helper loaded: newsfeed 0|mmstart | [09:44:37.960] [LOG] All module helpers loaded. 0|mmstart | [09:44:37.965] [LOG] Starting server on port 8080 ... 0|mmstart | [09:44:38.049] [INFO] ^[[33mYou're using a full whitelist configuration to allow for all IPs^[[39m 0|mmstart | [09:44:38.114] [LOG] Server started ... 0|mmstart | [09:44:38.124] [LOG] Connecting socket for: updatenotification 0|mmstart | [09:44:38.134] [LOG] Connecting socket for: MMM-DarkSkyForecast 0|mmstart | [09:44:38.143] [LOG] ====================== Starting node_helper for module [MMM-DarkSkyForecast] 0|mmstart | [09:44:38.149] [LOG] Connecting socket for: mmm-suncalc 0|mmstart | [09:44:38.153] [LOG] Starting node_helper for mmm-suncalc: 0|mmstart | [09:44:38.159] [LOG] Connecting socket for: calendar 0|mmstart | [09:44:38.167] [LOG] Starting node helper for: calendar 0|mmstart | [09:44:38.176] [LOG] Connecting socket for: newsfeed 0|mmstart | [09:44:38.184] [LOG] Starting module: newsfeed 0|mmstart | [09:44:38.198] [LOG] Sockets connected & modules started ... 0|mmstart | [09:44:38.252] [LOG] 0|mmstart | Ready to go! Please point your browser to: http://0.0.0.0:8080 0|mmstart | [09:44:38.356] [LOG] Whoops! There was an uncaught exception... 0|mmstart | [09:44:38.418] [LOG] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? 0|mmstart | [09:44:38.423] [LOG] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues 0|mmstart | [09:45:06.640] [LOG] Starting MagicMirror: v2.10.1 0|mmstart | [09:45:06.856] [LOG] Loading config ... 0|mmstart | [09:45:06.930] [LOG] Loading module helpers ... 0|mmstart | [09:45:06.945] [LOG] No helper found for module: alert. 0|mmstart | [09:45:07.656] [LOG] Initializing new module helper ... 0|mmstart | [09:45:07.674] [LOG] Module helper loaded: updatenotification 0|mmstart | [09:45:07.689] [LOG] No helper found for module: clock. 0|mmstart | [09:45:13.291] [LOG] Initializing new module helper ... 0|mmstart | [09:45:13.310] [LOG] Module helper loaded: MMM-DarkSkyForecast 0|mmstart | [09:45:13.362] [LOG] Initializing new module helper ... 0|mmstart | [09:45:13.380] [LOG] Module helper loaded: mmm-suncalc 0|mmstart | [09:45:13.389] [LOG] No helper found for module: calendar_monthly. 0|mmstart | [09:45:19.079] [LOG] Initializing new module helper ... 0|mmstart | [09:45:19.087] [LOG] Module helper loaded: calendar 0|mmstart | [09:45:19.960] [LOG] Initializing new module helper ... 0|mmstart | [09:45:19.987] [LOG] Module helper loaded: newsfeed 0|mmstart | [09:45:20.007] [LOG] All module helpers loaded. 0|mmstart | [09:45:20.031] [LOG] Starting server on port 8080 ... 0|mmstart | [09:45:20.159] [INFO] ^[[33mYou're using a full whitelist configuration to allow for all IPs^[[39m 0|mmstart | [09:45:20.292] [LOG] Server started ... 0|mmstart | [09:45:20.303] [LOG] Connecting socket for: updatenotification 0|mmstart | [09:45:20.321] [LOG] Connecting socket for: MMM-DarkSkyForecast 0|mmstart | [09:45:20.331] [LOG] ====================== Starting node_helper for module [MMM-DarkSkyForecast] 0|mmstart | [09:45:20.339] [LOG] Connecting socket for: mmm-suncalc 0|mmstart | [09:45:20.343] [LOG] Starting node_helper for mmm-suncalc: 0|mmstart | [09:45:20.359] [LOG] Connecting socket for: calendar 0|mmstart | [09:45:20.369] [LOG] Starting node helper for: calendar 0|mmstart | [09:45:20.378] [LOG] Connecting socket for: newsfeed 0|mmstart | [09:45:20.394] [LOG] Starting module: newsfeed 0|mmstart | [09:45:20.397] [LOG] Sockets connected & modules started ... 0|mmstart | [09:45:20.410] [LOG] 0|mmstart | Ready to go! Please point your browser to: http://0.0.0.0:8080 0|mmstart | [09:45:20.554] [LOG] Whoops! There was an uncaught exception... 0|mmstart | [09:45:20.680] [LOG] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? 0|mmstart | [09:45:20.687] [LOG] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues 0|mmstart | [09:45:53.656] [LOG] Starting MagicMirror: v2.10.1 0|mmstart | [09:45:53.864] [LOG] Loading config ... 0|mmstart | [09:45:53.987] [LOG] Loading module helpers ... 0|mmstart | [09:45:54.028] [LOG] No helper found for module: alert. 0|mmstart | [09:45:55.278] [LOG] Initializing new module helper ... 0|mmstart | [09:45:55.292] [LOG] Module helper loaded: updatenotification 0|mmstart | [09:45:55.321] [LOG] No helper found for module: clock. -
-
Everything was stopped.
$ pm2 status ┌────┬────────────────────┬──────────┬──────┬──────────┬──────────┬──────────┐ │ id │ name │ mode │ ↺ │ status │ cpu │ memory │ ├────┼────────────────────┼──────────┼──────┼──────────┼──────────┼──────────┤ │ 0 │ mmstart │ fork │ 1780 │ stopped │ 0% │ 0b │ └────┴────────────────────┴──────────┴──────┴──────────┴──────────┴──────────┘ -
@kellogg76 pm2 info 0
-
Describing process with id 0 - name mmstart ┌───────────────────┬──────────────────────────────────────┐ │ status │ stopped │ │ name │ mmstart │ │ version │ N/A │ │ restarts │ 1780 │ │ uptime │ 0 │ │ script path │ /home/pi/mmstart.sh │ │ script args │ N/A │ │ error log path │ /home/pi/.pm2/logs/mmstart-error.log │ │ out log path │ /home/pi/.pm2/logs/mmstart-out.log │ │ pid path │ /home/pi/.pm2/pids/mmstart-0.pid │ │ interpreter │ bash │ │ interpreter args │ N/A │ │ script id │ 0 │ │ 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-03-28T19:51:14.338Z │ └───────────────────┴──────────────────────────────────────┘ Divergent env variables from local env ┌────────────────┬──────────────────────────────────────┐ │ SSH_CONNECTION │ 192.168.1.148 54823 192.168.1.166 22 │ │ XDG_SESSION_ID │ c2 │ │ SSH_CLIENT │ 192.168.1.148 54823 22 │ │ SSH_TTY │ /dev/pts/1 │ └────────────────┴──────────────────────────────────────┘ Add your own code metrics: http://bit.ly/code-metrics Use `pm2 logs mmstart [--lines 1000]` to display logs Use `pm2 env 0` to display environment variables Use `pm2 monit` to monitor CPU and Memory usage mmstart -
@kellogg76 said in MM on Pi Zero fails after being off for a few days:
/home/pi/mmstart.sh
can u show that file
-
#!/bin/bash cd ~/MagicMirror node serveronly & sleep 30 xinit /home/pi/chromium_start.sh -
@kellogg76 said in MM on Pi Zero fails after being off for a few days:
xinit /home/pi/chromium_start.sh
and that one?
-
#!/bin/sh unclutter & xset -dpms # disable DPMS (Energy Star) features. xset s off # disable screen saver xset s noblank # don’t blank the video device matchbox-window-manager & chromium-browser -–incognito --start-fullscreen -–kiosk http://localhost:8080/ -
@kellogg76 weird…
and if you do pm2 start 0 it works ok?
-
@sdetweil it works in as much as I can see the magic mirror on another computer when I point to the correct IP, but the pi itself does not display anything at all, it sits at a terminal prompt or if I reboot and let it try to start on its own it’ll switch from prompt to black screen with mouse pointer as if it’s trying to start, then it loops back to a prompt and cycles between the two states.
-
weird… seems like chrome is having trouble.
if you type
chromium-browser --app=https://cnn.comdoes it come up?
in 2.10, i created a similar script for
pi0w(armv6l) as electron doesn’t exist anymoretry this script
curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/run-start.sh >~/MagicMirror/run-start.sh chmod +x ~/MagicMirror/run-start.shthen
cd ~/MagicMirror ./run-start.sh -
@sdetweil said in MM on Pi Zero fails after being off for a few days:
./run-start.sh
When I run
chromium-browser --app=https://cnn.comI get command not found, so I tried
chromium --app=https://cnn.comand I get Illegal Instruction.
i tried your script, and I get the text on screen about no helper found etc, then it gets stuck when trying to fetch the calendar data. I can access it from another computer but the pi is still blank on screen
Edit: It does seem to go through the calendar step but just very slowly, still progressing to each successive calendar now. I’ll leave it running and see if it eventually successfully starts.
-
@kellogg76 no… its stuck with the chromium-browser not loading…
I think u need to reinstall the chromium browser…
this means there was an update , or there is an sd card problem…
-
@sdetweil looks like the quickest fix is to re-install again. It’s a pain as I probably have to do this about once or twice a year. It can be working great then either the power will unexpectedly go out or I’ll shut it down for some reason and then it takes a full wipe and re-install to get it working again.
-
@kellogg76 use my install script
see here
https://github.com/sdetweil/MagicMirror_scriptsrename existing MM folder out of the way
run the install script… it does everything…(well, not install chromium browser)
sudo apt-get install chromium-browser -
@kellogg76 i have a system that is like that… power messes up everything…
I have moved to boot from sd card, RUN from ssd…
https://jamesachambers.com/raspberry-pi-4-usb-boot-config-guide-for-ssd-flash-drives/
see starting here
USB Boot Instructions -
@sdetweil I renamed the old MM directory and ran your script
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"Everything went successfully, I can see the display from other computers but the pi just sits at a terminal prompt, is there something I need to do to start things off?
$ pm2 list ┌────┬─────────────────────────┬─────────┬─────────┬──────────┬────────┬──────┬──────────┬──────────┬──────────┬──────────┬──────────┐ │ id │ name │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ ├────┼─────────────────────────┼─────────┼─────────┼──────────┼────────┼──────┼──────────┼──────────┼──────────┼──────────┼──────────┤ │ 1 │ MagicMirror │ 2.10.1 │ fork │ 568 │ 2m │ 1 │ online │ 0% │ 2.5mb │ pi │ enabled │ └────┴─────────────────────────┴─────────┴─────────┴──────────┴────────┴──────┴──────────┴──────────┴──────────┴──────────┴──────────┘ -
@kellogg76 did u install chromium-browser
the run-start.sh script depends on it
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login