MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. kellogg76
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    K
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 32
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: MM on Pi Zero fails after being off for a few days

      @sdetweil

      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
      
      posted in Troubleshooting
      K
      kellogg76
    • RE: MM on Pi Zero fails after being off for a few days

      Everything was stopped.

      $ pm2 status
      ┌────┬────────────────────┬──────────┬──────┬──────────┬──────────┬──────────┐
      │ id │ name               │ mode     │ ↺    │ status   │ cpu      │ memory   │
      ├────┼────────────────────┼──────────┼──────┼──────────┼──────────┼──────────┤
      │ 0  │ mmstart            │ fork     │ 1780 │ stopped  │ 0%       │ 0b       │
      └────┴────────────────────┴──────────┴──────┴──────────┴──────────┴──────────┘
      
      posted in Troubleshooting
      K
      kellogg76
    • RE: MM on Pi Zero fails after being off for a few days

      @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.
      
      posted in Troubleshooting
      K
      kellogg76
    • RE: MM on Pi Zero fails after being off for a few days

      @sdetweil Thanks, i’ll check back later, I’m in Eastern Canada so if the time difference is a problem leave some instructions and I’ll reply with the outcomes.

      posted in Troubleshooting
      K
      kellogg76
    • MM on Pi Zero fails after being off for a few days

      I’ve had my MM running well for months, but I had to shut it down recently to move it and when I plugged everything in again afterwards it doesn’t load on the Pi’s screen. It does however load fine if i remotely connect to the url for my MM on another computer.

      i assumed it might be a problem with Chromium so I removed and re-installed that, but it made no difference.

      Next I tried re-installing again on top of my current installation (from here http://emmanuelcontreras.com/how-to/how-to-create-a-magic-mirror-2-with-pi-zero-w/) but have had no luck.

      The description of the problem is that the Pi boots to terminal then screen goes black and I see a mouse cursor, then it drops back to the terminal and just loops between the two every 30s or so.

      Is there a way to diagnose what’s going on as I really don’t want to start from scratch again.

      Cheers

      posted in Troubleshooting
      K
      kellogg76
    • RE: Something went wrong displaying this web page error

      @sdetweil
      The only non-default modules I have are
      MMM-BackgroundSlideshow
      MMM-DarkSkyForecast
      mmm-suncalc

      I’m going to remove them one by one from the config and see if that identifies which is the problem module.

      Edit: it looks like it’s the BackgroundSlideshow module, removing that from my config file makes everything stable again. Thanks for your help.

      posted in Troubleshooting
      K
      kellogg76
    • RE: Something went wrong displaying this web page error

      @sdetweil said in Something went wrong displaying this web page error:

      node installers/dumpactivemodules.js

      When I do that nothing appears on screen

      posted in Troubleshooting
      K
      kellogg76
    • RE: Something went wrong displaying this web page error

      @sdetweil
      Still the same error after doing the above and then rebooting.

      posted in Troubleshooting
      K
      kellogg76
    • RE: Something went wrong displaying this web page error

      @sdetweil

      Unfortunately it doesn’t seem to have made any difference.

      posted in Troubleshooting
      K
      kellogg76
    • RE: Something went wrong displaying this web page error

      @sdetweil

      I’ll give it a try with the force option.

      Thanks

      posted in Troubleshooting
      K
      kellogg76
    • 1 / 1