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

Ok, thanks for the explanation :) I can understand that reasonably. You are a genius

@Stoffbeuteluwe ok, aber was muss ich dort eingeben? Keine Ahnung…

Ich habe die 12% Variante genommen, passt für mich. Aber am besten ist wirklich, man geht mit einem Handy vorbei und testet jedes Glas

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

@sdetweil I do not really like the module any more. I’m trying to get it up and running for a year :)

Thank you very much for your great support

@sdetweil Ok, I did. I’ll watch that. Can you explain in one sentence what I just did here or where the mistake was?

I have disabled the module, but the mails are still not displayed :(

/*{
	module: 'MMM-SoccerLiveScore',
	position: 'top_right',
	header: 'Fussball Rangliste',
	config: {
		leagues: [215,399,1],
        showNames: true,
        showLogos: true,
        displayTime: 60 * 1000,
        showTables: true
	}
},*/

@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

@Stoffbeuteluwe hier -> https://www.glastroesch.ch/glas/82-spionspiegel.html

that would be the log files

pi@raspberrypi_1:~/MagicMirror $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2        | 2019-09-07T10:11:41: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:41: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T10:11:42: PM2 log: Process with pid 840 still alive after 1600ms, sending it SIGKILL now...
PM2        | 2019-09-07T10:11:42: PM2 log: App [mm:0] exited with code [0] via signal [SIGKILL]
PM2        | 2019-09-07T10:11:42: PM2 log: pid=840 msg=process killed
PM2        | 2019-09-07T10:11:42: PM2 log: App [mm:0] starting in -fork mode-
PM2        | 2019-09-07T10:11:43: PM2 log: App [mm:0] online

/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm       | All module helpers loaded.
0|mm       | Starting server on port 8080 ...
0|mm       | Server started ...
0|mm       | Connecting socket for: updatenotification
0|mm       | Connecting socket for: MMM-Remote-Control
0|mm       | Starting node helper for: MMM-Remote-Control
0|mm       | Connecting socket for: MMM-NowPlayingOnSpotify
0|mm       | Connecting socket for: MMM-MyCommute
0|mm       | ====================== Starting node_helper for module [MMM-MyCommute]
0|mm       | Connecting socket for: MMM-SystemStats
0|mm       | Connecting socket for: MMM-BackgroundSlideshow
0|mm       | Sockets connected & modules started ...
0|mm       | Launching application.
0|mm       | Refreshed access token because it has expired. Expired at: 10:12:00 now is: 10:12:01
0|mm       | Refreshed access token because it has expired. Expired at: 11:12:01 now is: 10:12:01

/home/pi/.pm2/logs/mm-error.log last 15 lines:
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       | 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       | (node:871) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
0|mm       | [960:0907/095911.730586:FATAL:memory.cc(22)] Out of memory. size=96002048
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       | (node:3175) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
0|mm       | [3214:0907/102404.493830:FATAL:memory.cc(22)] Out of memory. size=96002048

Sorry, it’s me again.

One of my PI’s actually ran for months without any problems. I updated the module MMM-BackgroundSlideshow 3 days ago. Since this update, my mirror is about 10min always dunek. When I enter pm2 start mm in the console, the picture comes back. I have also run the dependency in module folder npm install, without success.

What could be the reason for this?

How can I display the text on the entire width of the monitor. Do I have to change this in compliments.js or in custom.css?

@mumblebaj

Exactly, I replaced the password with the key. I have also installed npm.

cd MagicMirror/modules
cd email
npm install

npm WARN email@0.0.1 No repository field.
npm WARN email@0.0.1 No license field.

audited 24 packages in 2.521s
found 0 vulnerabilities

pm2 logs

pi@raspberrypi_LOL:~/MagicMirror/modules/email $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2        | 2019-09-07T04:30:05: PM2 log: App [mm:0] online
PM2        | 2019-09-07T07:40:45: PM2 log: Process 0 in a stopped status, starting it
PM2        | 2019-09-07T07:40:45: PM2 log: Stopping app:mm id:0
PM2        | 2019-09-07T07:40:46: PM2 log: pid=20666 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T07:40:46: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2        | 2019-09-07T07:40:46: PM2 log: pid=20666 msg=process killed
PM2        | 2019-09-07T07:40:46: PM2 log: App [mm:0] starting in -fork mode-
PM2        | 2019-09-07T07:40:46: PM2 log: App [mm:0] online
PM2        | 2019-09-07T07:55:09: PM2 log: Process 0 in a stopped status, starting it
PM2        | 2019-09-07T07:55:09: PM2 log: Stopping app:mm id:0
PM2        | 2019-09-07T07:55:10: PM2 log: pid=5504 msg=failed to kill - retrying in 100ms
PM2        | 2019-09-07T07:55:10: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2        | 2019-09-07T07:55:10: PM2 log: pid=5504 msg=process killed
PM2        | 2019-09-07T07:55:10: PM2 log: App [mm:0] starting in -fork mode-
PM2        | 2019-09-07T07:55:10: PM2 log: App [mm:0] online

/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm       | SyntaxError: Unexpected token u in JSON at position 0
0|mm       |     at JSON.parse (<anonymous>)
0|mm       |     at Request._callback (/home/pi/MagicMirror/modules/MMM-SoccerLiveScore/node_helper.js:146:29)
0|mm       |     at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
0|mm       |     at Request.emit (events.js:182:13)
0|mm       |     at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:881:8)
0|mm       |     at ClientRequest.emit (events.js:182:13)
0|mm       |     at TLSSocket.socketErrorListener (_http_client.js:382:9)
0|mm       |     at TLSSocket.emit (events.js:182:13)
0|mm       |     at emitErrorNT (internal/streams/destroy.js:82:8)
0|mm       |     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm       | (node:5525) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm       | (node:7860) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm       | Connecting socket for: email
0|mm       | email helper started ...
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       | [AVSTOCK] Initialized.
0|mm       | Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload:  { style: 'standard' }
0|mm       | listening for emails...
0|mm       | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/zeptrion%40gmail.com/private-75149d8982f910a209e0fe7d0363d75f/basic.ics - Interval: 300000
0|mm       | NEW MAIL
0|mm       | NEW MAIL
0|mm       | NEW MAIL
0|mm       | NEW MAIL
0|mm       | NEW MAIL

@sdetweil

That’s right, sorry

> 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
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: MMM-SystemStats
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: MMM-MyCommute
Initializing new module helper ...
Module helper loaded: MMM-AVStock
Initializing new module helper ...
Module helper loaded: MMM-GoogleMapsTraffic
Initializing new module helper ...
Module helper loaded: MMM-SoccerLiveScore
Initializing new module helper ...
Module helper loaded: email
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-SystemStats
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-MyCommute
====================== Starting node_helper for module [MMM-MyCommute]
Connecting socket for: MMM-AVStock
Connecting socket for: MMM-GoogleMapsTraffic
Starting node_helper for module: MMM-GoogleMapsTraffic
Connecting socket for: MMM-SoccerLiveScore
MMM-SoccerLiveScore helper started...
Connecting socket for: email
email helper started ...
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 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

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

If i enter npm start dev he following will come out:

npm ERR! path /home/pi/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-09-06T07_07_27_973Z-debug.log

Good Morning

So I activated the 2FA and replaced the generated key with my password. I also took your config and added my username and password from 2FA. Unfortunately, as before, there is still “load” and it does not show any emails.

I do not see it either. I see the same as sdetweil. I’ve also approved third-party apps with account access on this page below.

Can I do something that would help you? Post a log or something. You just have to tell me the command;)

no ideas? Or can I do something that can help you to find the mistake?