MMM-MyCommute

sdetweil · Sep 5, 2019, 12:49 PM

@CyruS1337 what does ‘does not run’ mean?

did u open the developers console and look for any errors reported?

CyruS1337 · Sep 6, 2019, 7:13 AM

If I access the MagicMirror directly via Putty do I have to enter npm start dev or how?

sdetweil · Sep 6, 2019, 12:21 PM

cd ~/MagicMirror
export DISPLAY=:0
npm start dev

CyruS1337 · Sep 7, 2019, 5:47 AM

@sdetweil said in MMM-MyCommute:

export DISPLAY=:0

That comes out when I enter npm start dev

> magicmirror@2.8.0 start /home/pi/MagicMirror
> sh run-start.sh "dev"

Starting MagicMirror: v2.8.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
Initializing new module helper ...
Module helper loaded: MMM-WatchDog
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: MMM-SystemStats
Initializing new module helper ...
Module helper loaded: newsfeed
Initializing new module helper ...
Module helper loaded: MMM-MyCommute
Initializing new module helper ...
Module helper loaded: MMM-GoogleMapsTraffic
Initializing new module helper ...
Module helper loaded: MMM-DarkSkyForecast
Initializing new module helper ...
Module helper loaded: MMM-MyCalendar
All module helpers loaded.
Starting server on port 8080 ...
Server started ...
Connecting socket for: updatenotification
Connecting socket for: MMM-WatchDog
Starting module helper: MMM-WatchDog
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-SystemStats
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-MyCommute
====================== Starting node_helper for module [MMM-MyCommute]
Connecting socket for: MMM-GoogleMapsTraffic
Starting node_helper for module: MMM-GoogleMapsTraffic
Connecting socket for: MMM-DarkSkyForecast
====================== Starting node_helper for module [MMM-DarkSkyForecast]
Connecting socket for: MMM-MyCalendar
Starting node helper for: MMM-MyCalendar
Sockets connected & modules started ...
Whoops! There was an uncaught exception...
{ Error: listen EADDRINUSE 0.0.0.0:8080
    at Server.setupListenHandle [as _listen2] (net.js:1330:14)
    at listenInCluster (net.js:1378:12)
    at doListen (net.js:1492:7)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:755:11)
    at startup (internal/bootstrap/node.js:241:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:579:3)
  errno: 'EADDRINUSE',
  code: 'EADDRINUSE',
  syscall: 'listen',
  address: '0.0.0.0',
  port: 8080 }
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
Launching application.

sdetweil · Sep 7, 2019, 12:15 PM

@CyruS1337 said in MMM-MyCommute:

EADDRINUSE 0.0.0.0:8080

already an instance running with pm2…

pm2 list

pm2 stop 0

pm2 start 0

CyruS1337 · Sep 7, 2019, 12:57 PM

@sdetweil said in MMM-MyCommute:

@CyruS1337 said in MMM-MyCommute:

EADDRINUSE 0.0.0.0:8080

already an instance running with pm2…

pm2 list

pm2 stop 0

pm2 start 0

I did, unfortunately it still does not show me the module

pi@raspberrypi3:~/MagicMirror/modules/MMM-MyCommute $ pm2 list
┌──────┬────┬──────┬────────┬───┬─────┬──────────┐
│ Name │ id │ mode │ status │ ↺ │ cpu │ memory   │
├──────┼────┼──────┼────────┼───┼─────┼──────────┤
│ mm   │ 0  │ fork │ online │ 5 │ 0%  │ 2.6 MB   │
└──────┴────┴──────┴────────┴───┴─────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@raspberrypi3:~/MagicMirror/modules/MMM-MyCommute $ pm2 stop 0
[PM2] Applying action stopProcessId on app [0](ids: 0)
[PM2] [mm](0) ✓
┌──────┬────┬──────┬─────────┬───┬─────┬────────┐
│ Name │ id │ mode │ status  │ ↺ │ cpu │ memory │
├──────┼────┼──────┼─────────┼───┼─────┼────────┤
│ mm   │ 0  │ fork │ stopped │ 5 │ 0%  │ 0 B    │
└──────┴────┴──────┴─────────┴───┴─────┴────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@raspberrypi3:~/MagicMirror/modules/MMM-MyCommute $ pm2 start 0
[PM2] Applying action restartProcessId on app [0](ids: 0)
[PM2] [mm](0) ✓
[PM2] Process successfully started
┌──────┬────┬──────┬────────┬───┬─────┬──────────┐
│ Name │ id │ mode │ status │ ↺ │ cpu │ memory   │
├──────┼────┼──────┼────────┼───┼─────┼──────────┤
│ mm   │ 0  │ fork │ online │ 5 │ 0%  │ 2.6 MB   │
└──────┴────┴──────┴────────┴───┴─────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

sdetweil · Sep 7, 2019, 1:12 PM

ok, and pm2 logs to show the logging output

CyruS1337 · Sep 7, 2019, 1:22 PM

The module once worked on the PI. Do I have to do something now @sdetweil?

sdetweil · Sep 7, 2019, 1:25 PM

@CyruS1337 i don’t know anything about the module… so just looking for debugging info…

pm2 logs should show something

CyruS1337 · Sep 7, 2019, 2:08 PM

That would be my logs

pi@raspberrypi3:~ $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lin                                                                                                         es option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2        | [2019-09-07T14:54:17.446Z] PM2 log: Stopping app:mm id:0
PM2        | [2019-09-07T14:54:17.944Z] PM2 log: pid=17526 msg=failed to kill -                                                                                                          retrying in 100ms
PM2        | [2019-09-07T14:54:18.048Z] PM2 log: pid=17526 msg=failed to kill -                                                                                                          retrying in 100ms
PM2        | [2019-09-07T14:54:18.145Z] PM2 log: pid=17526 msg=failed to kill -                                                                                                          retrying in 100ms
PM2        | [2019-09-07T14:54:18.224Z] PM2 log: App [mm] with id [0] and pid [1                                                                                                         7526], exited with code [0] via signal [SIGINT]
PM2        | [2019-09-07T14:54:18.245Z] PM2 log: pid=17526 msg=process killed
PM2        | [2019-09-07T14:54:27.372Z] PM2 log: Starting execution sequence in                                                                                                          -fork mode- for app name:mm id:0
PM2        | [2019-09-07T14:54:27.383Z] PM2 log: App name:mm id:0 online
PM2        | [2019-09-07T15:18:47.949Z] PM2 log: Process 0 in a stopped status,                                                                                                          starting it
PM2        | [2019-09-07T15:18:47.954Z] PM2 log: Stopping app:mm id:0
PM2        | [2019-09-07T15:18:48.369Z] PM2 log: pid=597 msg=failed to kill - re                                                                                                         trying in 100ms
PM2        | [2019-09-07T15:18:48.372Z] PM2 log: App [mm] with id [0] and pid [5                                                                                                         97], exited with code [0] via signal [SIGINT]
PM2        | [2019-09-07T15:18:48.469Z] PM2 log: pid=597 msg=process killed
PM2        | [2019-09-07T15:18:48.473Z] PM2 log: Starting execution sequence in                                                                                                          -fork mode- for app name:mm id:0
PM2        | [2019-09-07T15:18:48.493Z] PM2 log: App name:mm id:0 online

/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by                                                                                                          environment.
0|mm       | libGL error: MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by                                                                                                          environment.
0|mm       | libGL error: MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by                                                                                                          environment.
0|mm       | libGL error: MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | MESA-LOADER: failed to retrieve device information
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by                                                                                                          environment.

/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm       | Connecting socket for: MMM-MyCommute
0|mm       | ====================== Starting node_helper for module [MMM-MyCommu                                                                                                         te]
0|mm       | Connecting socket for: MMM-GoogleMapsTraffic
0|mm       | Starting node_helper for module: MMM-GoogleMapsTraffic
0|mm       | Connecting socket for: MMM-DarkSkyForecast
0|mm       | ====================== Starting node_helper for module [MMM-DarkSky                                                                                                         Forecast]
0|mm       | Connecting socket for: MMM-MyCalendar
0|mm       | Starting node helper for: MMM-MyCalendar
0|mm       | Sockets connected & modules started ...
0|mm       | Launching application.
0|mm       | Create new news fetcher for url: https://api.20min.ch/rss/view/1 -                                                                                                          Interval: 300000
0|mm       | WatchDog started. Maximum timeout: 10s.
0|mm       | Create new news fetcher for url: https://api.20min.ch/rss/view/67 -                                                                                                          Interval: 300000
0|mm       | Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-                                                                                                         GET payload:  { style: 'standard' }
0|mm       | Create new calendar fetcher for url: https://calendar.google.com/ca                                                                                                         lendar/ical/XXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/b                                                                                                         asic.ics - Interval: 300000