Calendar failed to load - check the logs

Richard238

Noticed neither of my two calendars were working on my MM over the weekend.
Not having time to investigate, I left it for another day.
Then one calendar worked but not the other, then they swapped over!
Now they’re both working.
On checking the logs, there are a lot of these timeout errors:

[2025-12-07 16:11:33.349] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/#################group.calendar.google.com/private-5##############################/basic.ics TypeError: fetch failed
    at node:internal/deps/undici/undici:13510:13
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: calendar.google.com:443, timeout: 30000ms)
      at onConnectTimeout (/home/pi/MagicMirror/node_modules/undici/lib/core/util.js:876:19)
      at Immediate._onImmediate (/home/pi/MagicMirror/node_modules/undici/lib/core/util.js:845:11)
      at process.processImmediate (node:internal/timers:485:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
  }

Looks like a timeout error at calendar_dot_google_dot_com and nothing to do with MM.
However, a more user friendly error message in place of the failed calendar would be nice to see.

sdetweil

@Richard238 good point…

what is more friendly for you?

 Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/#################group.calendar.google.com/private-5##############################/basic.ics TypeError: fetch failed, timeout

Richard238

If perhaps it could show the nature of the error?
And the route to the logs, because most of us have to look up where they are! ;-)

sdetweil

@Richard238 said in Calendar failed to load - check the logs:

about a minute ago

If perhaps it could show the nature of the error?

what does that mean?

we requested the ics data from the calendar provider using the URL you provided in the config

and the request failed, timeout… we don’t know why or anything more
and we gave you all that in the messages we produced.

And the route to the logs, because most of us have to look up where they are! ;-)

you are LOOKING at the logs… so you must have found the route

---- as always — the logs IS the output of the MM start command,

npm start
node --run start 
npm runs server
node --run server

whatever you used

now, you can do it manually in some terminal window
OR
you can code it into the system startup
OR
you can use a pgm that does that FOR you, aka pm2

WHERE that data is stored is up to that implementation
as I do the install script, I use pm2, as it insulates me from the OS details…
my script last lines is see the help

        echo please see the help for the pm2 command, pm2 --help
	echo pm2 status will show the running apps, and their runtime status

SO… one could/should detect that the command is pm2
and so do pm2 --help

and one core learning thing on linux
ALL terminal commands , by agreed convention, provide a general help using the parameter --help

so pm2 --help
will tell you all the things it can do

SOME commands ALSO provide a manual page (pm2 does not)
which can be viewed with the man command
man ls
will show you the detailed help for the ls command

Yes, there is a LOT to learn here…