MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Standard module Calendar hangs on events

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    30 Posts 2 Posters 3.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sdetweil @Laz
      last edited by

      @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

      Sam

      How to add modules

      learning how to use css

      L 5 Replies Last reply Reply Quote 0
      • L
        Laz @sdetweil
        last edited by

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

        1 Reply Last reply Reply Quote 0
        • L
          Laz @sdetweil
          last edited by

          @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.

          2c535ae6-6c9d-418a-b01e-915fe430f309-image.png

          cc78b64d-0ee3-44e4-a5d2-2196ca679359-image.png

          [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)

          3d9b9ab8-2b3f-4bad-9e83-75f8fc5bccaf-image.png

          06d66287-d43e-480c-be2b-c45b3cbccd3a-image.png

          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…

          1 Reply Last reply Reply Quote 0
          • L
            Laz @sdetweil
            last edited by

            @sdetweil Before rebooting.

            d95072e4-2394-45cc-9094-926b969f97e4-image.png

            1 Reply Last reply Reply Quote 0
            • L
              Laz @sdetweil
              last edited by

              @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… (

              5da241cb-eb1c-44fd-92dc-4980781d25ee-image.png

              957f4475-8751-4804-a4bc-9dcaebc653dc-image.png

              [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!

              69adc98a-d301-4a2c-803a-6d33cb22725f-image.png

              1 Reply Last reply Reply Quote 0
              • L
                Laz @sdetweil
                last edited by

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

                S 1 Reply Last reply Reply Quote 0
                • S
                  sdetweil @Laz
                  last edited by 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

                  Sam

                  How to add modules

                  learning how to use css

                  L 1 Reply Last reply Reply Quote 0
                  • L
                    Laz @sdetweil
                    last edited by

                    @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.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      sdetweil @Laz
                      last edited by sdetweil

                      @Laz no messages pending
                      I see the links in the posts below but not in the pending list. weird… sorry for the delay

                      these errors are outside of MagicMirror control.some may be recoverable, some may not. we don’t control the network stack

                      Sam

                      How to add modules

                      learning how to use css

                      L 1 Reply Last reply Reply Quote 0
                      • L
                        Laz @sdetweil
                        last edited by

                        @sdetweil After tomorrow I will try to repeat briefly…))

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 3 / 3
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy