Read the statement by Michael Teeuw here.
Standard module Calendar hangs on events
-
@sdetweil I will try to make ping permanent to these addresses (if Google allows ping) or contact the Internet provider.
-
@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… -
@sdetweil Before rebooting.
-
@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!
-
@sdetweil Perhaps the error is not related to the availability of Google servers?
-
@Laz the 1st error
internal server erroris 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
-
@sdetweil I sent some messages today. But only the latter got here. There are a little oddities there. Have you read them?))
Today, too, calendars have hung, but I have not seen any network errors. -
@Laz no messages pending
I see the links in the posts below but not in the pending list. weird… sorry for the delaythese errors are outside of MagicMirror control.some may be recoverable, some may not. we don’t control the network stack
-
@sdetweil After tomorrow I will try to repeat briefly…))