@tosti007 Thanks!

@mochman

Thanks, I do see a inet6 address with the command ifconfig.

I tried to add 10.0.0.95 to the config with no success :-(

But @xer0design’s tip worked!

@Cato is not feeling good these days and is in recovery. (Please get well!)

In the mean time, note that the module MMM-Entur does a good job of competing with MMM-Ruter.

https://github.com/Arve/MMM-Entur-tavle

@shbatm Just want to tell you that I’ve googled this thread every single time I’ve setup a new mirror from scratch, and still love it. Thanks for making a post almost 6 years ago that still has all the info and works!

@bugsounet Thank you! If it crashes again, I’ll start by disabling 1/2 of the modules until I find the problem. This could take days, hope I don’t have to 😐

I just did a

git pull && npm install

To see if it makes a difference.

Hi!

My mirror crashes every day. It just goes black and works again if I manually quit it (pm2 will then restart it).

I checked the logs by doing

pm2 logs mm

Which gives me:

[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm       | rning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
0|mm       | [16.06.2021 10:58.04.258] [ERROR] (node:939) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
0|mm       | [16.06.2021 19:30.11.075] [WARN]  (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
0|mm       | [17.06.2021 05:30.22.142] [ERROR] (node:8664) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 NOTIFY listeners added to [EventSource]. Use emitter.setMaxListeners() to increase limit
0|mm       | [17.06.2021 05:30.22.155] [ERROR] (node:8664) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 STATUS listeners added to [EventSource]. Use emitter.setMaxListeners() to increase limit
0|mm       | [17.06.2021 05:30.22.159] [ERROR] (node:8664) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 EVENT listeners added to [EventSource]. Use emitter.setMaxListeners() to increase limit
0|mm       | [8713:0617/083204.668041:FATAL:memory.cc(22)] Out of memory. size=88473600
0|mm       | [17.06.2021 12:59.20.996] [WARN]  (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
0|mm       | [13452:0617/205251.489565:FATAL:memory.cc(22)] Out of memory. size=88473600
0|mm       | [18.06.2021 14:24.55.633] [WARN]  (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
0|mm       | [18.06.2021 14:33.07.564] [WARN]  (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
0|mm       | [19.06.2021 00:33.15.146] [ERROR] (node:19706) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 NOTIFY listeners added to [EventSource]. Use emitter.setMaxListeners() to increase limit
0|mm       | [19.06.2021 00:33.15.156] [ERROR] (node:19706) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 STATUS listeners added to [EventSource]. Use emitter.setMaxListeners() to increase limit
0|mm       | [19.06.2021 00:33.15.159] [ERROR] (node:19706) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 EVENT listeners added to [EventSource]. Use emitter.setMaxListeners() to increase limit
0|mm       | [19755:0619/134817.487939:FATAL:memory.cc(22)] Out of memory. size=88473600

/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm       | [19.06.2021 20:07.22.143] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:12.32.306] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:17.42.082] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:22.51.820] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:28.01.490] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:33.11.508] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:38.21.877] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:43.32.020] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:48.41.909] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:53.52.000] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 20:59.02.028] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 21:04.12.077] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 21:09.22.303] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 21:14.32.500] [INFO]  Calendar-Fetcher: Broadcasting 12 events.
0|mm       | [19.06.2021 21:19.42.322] [INFO]  Calendar-Fetcher: Broadcasting 12 events.

Any ideas on how I could fix this?

@sdetweil

It works now! And it seems to be due to debugging being turned off. Thank you so much for your help!

And there… without me doing anything. It suddenly is showing events in Magic Mirror! Could it be that the calendar is just to darn big, and that it takes 10-15 minutes for it to process it?

@sdetweil said in Calendar not loading after update:

// change language
language: “en”,
// remove ,“DEBUG”
logLevel: [“INFO”, “LOG”, “WARN”, “ERROR”,“DEBUG”],

Thanks again. I tuned down DEBUG, and the log file made it easier to spot this:

| Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/SECRETSTRING/basic.ics - Interval: 300000
0|mm     | [31.03.2021 21:11.19.188] [LOG]   
0|mm     | received: SECRETSTRINGn0=
0|mm     | [31.03.2021 21:11.22.778] [LOG]   
0|mm     | MMM-Ring at (31.3.2021, 21:11:22): Refresh Token Updated
0|mm     | [31.03.2021 21:11.36.837] [INFO]  
0|mm     | Calendar-Fetcher: Broadcasting 12 events.

Anything useful to get out of that?

@sdetweil Thanks for the reply!

I did the manual check of visiting the calendar URL directly from the browser on the pi, and it successfully downloaded the .ics file.

I haven’t ever been able to se much errors via my setup, but learning the pm2 logs --lines=15 command from you know was interesting. It actually shows me stuff like this:

0|mm       | event={"type":"VEVENT","params":[],"start":"2013-11-21T15:00:00.000Z","datetype":"date-time","end":"2013-11-21T19:45:00.000Z","dtstamp":"2021-03-31T18:39:55.000Z","uid":"E627EC7E-6FA4-4E8A-801C-03D26F093F70","created":"2013-11-20T11:01:17.000Z","description":"","lastmodified":"2013-11-20T11:01:22.000Z","location":"","sequence":"2","status":"CONFIRMED","summary":"Loolz is visting ROFL","transparency":"OPAQUE"}
0|mm       | [31.03.2021 20:40.53.545] [DEBUG]  start=Thu Nov 21 2013 16:00:00 GMT+0100 (sentraleuropeisk normaltid) end=Thu Nov 21 2013 20:45:00 GMT+0100 (sentraleuropeisk normaltid)
0|mm       | [31.03.2021 20:40.53.548] [DEBUG] have entries 
0|mm       | [31.03.2021 20:40.53.551] [DEBUG] 

• It’s an event in the calendar from back in 2013.
• There are multiple events like this in the log file, (if I do pm2 logs --lines=100 I get a lot more.
• And I see a lot of information is passed in Norwegian. So I redid the setup wizard on the Pi and choose to ‘Use English langauge’. Restarted hoping it would work, but it didn’t.

Keeping the rest the same, I tried replacing the calendar URL with another calendar URL I had, and I was able to get it to work. So it seems that my calendar could be the problem. But it (still) works on my previous Magic Mirror setup, just not the new one that it freshly installed.

I just did a fresh install of Raspberry Pi OS and Magic Mirror, and moved my modules, config and css. Everything works, except the Calendar module. This is my code.

{
			module: 'calendar',
			header: '',
			position: 'top_left',
			config: {
				maximumEntries: '12',
				maximumNumberOfDays: '31',
				maxTitleLength: '57',
				hidePrivate: true,
				fade: false,
				displaySymbol: false,
				calendars: [
					{
						symbol: 'calendar-check-o ',
						url: 'URLTOMYPRIVATECALENDAR'
					}
					
						
				]
			}
		},		

It’s just stock at Loading… now. So I tried to redo the code based on the documentation, which unfortunately doesn’t have a complete code snippet example with a calendar URL that I’ve been able to successfully use. I tried based on the sample code to add piece by piece of my old config but it stops at loading everything I try to add something.

Does anybody see anything wrong with my code?

@Cato is not feeling good these days and is in recovery. (Please get well!)

In the mean time, note that the module MMM-Entur does a good job of competing with MMM-Ruter.

https://github.com/Arve/MMM-Entur-tavle