Standard module Calendar hangs on events

Laz

@sdetweil To update the calendar after hanging, I used just a raspberry reboot. Then my friend helped me make a script to reboot only the mirror software itself.
And I connected the button to the GPIO raspberry.
The script is like this -

sdetweil

@Laz so you are using pm2

Laz

@sdetweil I set it according to this instruction -

https://github.com/sdetweil/MagicMirror_scripts

sdetweil

@Laz yes, that is my set of scripts…

anyhow, pm2’s job is to keep MM (or any other app it manages) running…

but it also collects the output from those apps…

SO you can use the pm2 command to print out the content it has already saved

pm2 --help
shows you all the things the command can do .

pm2 logs

will dump out the info saved
the --lines=nn parameter will control how many lines of output to display… the default is just 15… so you may have to increase the number to get more of the output

pm2 logs --lines=50 or --lines=100

Laz

@sdetweil Thanks a lot!!!
Not everything is clear (Google translator…;))))))))))))))))
But I will try today or over the weekend to do everything you wrote and show you the results.

Laz

@sdetweil But I am afraid that the log file may not show an error at a particular moment. Because the hanging events of the blue calendar occur chaotically, not every day…
The pink calendar barely freezes in event updates.
I changed the arrangement of these calendars (one above the other), but it didn’t help for the blue calendar.

sdetweil

@Laz the info, if any, will be in the log

you can also see the files holding the log info

in the ~/.pm2/logs folder (note the . in front of pm2 here)

Laz

@sdetweil Good afternoon!
I did not succeed in doing everything on your advice.
But I noticed that the blue calendar had not been updated for several days. And I looked at the log file.
It shows that until April 2, two calendars are being updated to 20.56.41. And after 21.01.28, only one calendar began to be updated. And so it was until I overloaded the mirror today.
I attach screenshots from the log file.

sdetweil

@Laz thanks. that’s the good info. how about the error log? I’m pretty sure there was a timeout error, and once errored, it never recovers.

but you should see the timeout error reported on the error log

Laz

@sdetweil

Good afternoon!
I couldn’t find any calendar related errors.
I can’t insert a txt file here. Changing the extension to a picture also does not go away.

sdetweil

@Laz pic post is the image 3rd from the right on the ioc list above the reply editor

u can paste the text

please use code blocks around
paste
select all the text you just pasted
press the </> button

Laz

@sdetweil I wanted to insert the file. I copied a large piece from the error file into a separate file. It turned out 311 KB.
If you insert this here by copying, then there will be a lot.

sdetweil

@Laz yeh. forum is a pain some times…

email to me, same userid at gmail

Laz

@sdetweil Yes, OK )

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.