Standard module Calendar hangs on events

Laz

sdetweil

@Laz got it…

there is the error

[04.04.2023 20:12.18.185] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/.....
internal server error

something happened at google…

and more importantly

[04.04.2023 20:06.53.607] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/....
...
failed, reason: getaddrinfo EAI_AGAIN calendar.google.com
    at ClientRequest.<anonymous> (/home/vova/MagicMirror/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:481:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'EAI_AGAIN',
  code: 'EAI_AGAIN'

we can’t find a path to the server for this…
all outside the pi… so no idea we can’t fix it…
but we keep trying (so that is good)

do you run a pihole ad blocker system? seen this a lot when pihole has a problem

Laz

@sdetweil Yes, I see mistakes now… (
They last more than an hour in the records and then apparently the requests stop.
There is no ad blocker on raspberries. There is just a standard image and then a mirror is installed with a minimum of additional modules.
I noticed in the errors that there is an error of my two calendars. Perhaps at some point really Google becomes unavailable…
Of course, I don’t turn to the calendar so often on my phone and computer.
But today, before loading the mirror, I noticed that the blue calendar has not been updated since April 4. Just the errors are dated April 4th. It turns out that when there are many errors, the module stops accessing the calendar? After all, it cannot be that Google was not available for so many days…

sdetweil

@Laz the EAI_AGAIN error is a networking error…

the library we use does the work , nothing in our code…
the code needs to get the IP address of the server to connect
it looks up the name to get the address
this failed… name not found

thats all we got… “we can’t look this up now, please try again”
no idea where in the network from the pi outward what error caused the failure

Laz

@sdetweil I will try to make ping permanent to these addresses (if Google allows ping) or contact the Internet provider.

Laz

@sdetweil Good afternoon
Here is another very strange situation. Now I see that there is no calendar update. View the error log file, but there are no errors. But the date of the error file is April 8th! Today is April 9th.
I’ll give you screenshots and try to overload the mirror.

[07.04.2023 10:54.57.922] [ERROR] Newsfeed Error. Could not fetch newsfeed:  http://tyumen-news.net/rss/news Error: Bad Gateway
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[07.04.2023 14:12.12.283] [ERROR] Newsfeed Error. Could not fetch newsfeed:  https://www.ixbt.com/export/utf8/hardnews.rss Error: Bad Gateway
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[08.04.2023 05:09.10.408] [ERROR] Newsfeed Error. Could not fetch newsfeed:  https://www.ixbt.com/export/utf8/hardnews.rss Error: Gateway Time-out
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[08.04.2023 05:14.10.782] [ERROR] Newsfeed Error. Could not fetch newsfeed:  https://www.ixbt.com/export/utf8/hardnews.rss Error: Bad Gateway
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
/home/vova/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[12318:0408/113452.405608:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
X connection to :0 broken (explicit kill or server shutdown).
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)

It can be seen that on the 8th at 18-00 the second calendar stopped being polled.
And at 21-15, the first calendar stopped being interviewed.
And there is still no poll.
I’m pinging Google right now, ping is great…

Laz

@sdetweil Before rebooting.

Laz

@sdetweil After the reboot. Both calendars were immediately updated.
And the error log file was immediately updated!
But I don’t see any network-related calendar errors in it… (

[07.04.2023 10:54.57.922] [ERROR] Newsfeed Error. Could not fetch newsfeed:  http://tyumen-news.net/rss/news Error: Bad Gateway
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[07.04.2023 14:12.12.283] [ERROR] Newsfeed Error. Could not fetch newsfeed:  https://www.ixbt.com/export/utf8/hardnews.rss Error: Bad Gateway
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[08.04.2023 05:09.10.408] [ERROR] Newsfeed Error. Could not fetch newsfeed:  https://www.ixbt.com/export/utf8/hardnews.rss Error: Gateway Time-out
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[08.04.2023 05:14.10.782] [ERROR] Newsfeed Error. Could not fetch newsfeed:  https://www.ixbt.com/export/utf8/hardnews.rss Error: Bad Gateway
    at NodeHelper.checkFetchStatus (/home/vova/MagicMirror/js/node_helper.js:120:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
/home/vova/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[12318:0408/113452.405608:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
X connection to :0 broken (explicit kill or server shutdown).
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[1374:0408/120432.325630:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[1374:0408/120432.326975:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[1374:0408/120435.597191:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
/home/vova/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: невозможно открыть разделяемый объектный файл: Отказано в доступе (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[6024:0409/124326.890535:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

Laz

@sdetweil Perhaps the error is not related to the availability of Google servers?

sdetweil

@Laz the 1st error
internal server error

is Google’s

the EAI_AGAIN
is not Google’s,

your request never made it there as the underlying code couldn’t get the IP address to use.

this is a network problem, somewhere