Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34342

The repository 'https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/ubuntu jammy InRelease' is no longer signed

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.11.8
    • N/A
    • OTHER
    • None

    Description

      E: Failed to fetch http://downloads.mariadb.com/Tools/ubuntu/dists/jammy/InRelease 403 Forbidden [IP: 2606:4700::6812:8718 80]
      E: The repository 'http://downloads.mariadb.com/Tools/ubuntu jammy InRelease' is no longer signed.
      N: Updating from such a repository can't be done securely, and is therefore disabled by default.
      N: See apt-secure(8) manpage for repository creation and user configuration details.
      E: Failed to fetch https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/ubuntu/dists/jammy/InRelease 403 Forbidden [IP: 2606:4700::6812:8718 443]
      E: The repository 'https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/ubuntu jammy InRelease' is no longer signed.
      N: Updating from such a repository can't be done securely, and is therefore disabled by default.
      N: See apt-secure(8) manpage for repository creation and user configuration details.

      Attachments

        Issue Links

          Activity

            bryan Bryan Alsdorf added a comment -

            Can you let me know what IP this is from so I can trace the request in our logs?

            We have seen some abusive traffic recently and implemented some filtering which may be impacting you.

            bryan Bryan Alsdorf added a comment - Can you let me know what IP this is from so I can trace the request in our logs? We have seen some abusive traffic recently and implemented some filtering which may be impacting you.
            AlexP Alexander Palm added a comment - - edited

            Because I have the same issue, my VPS-Provider is Strato and Hetzner which are completely not work. But via curl I get an answer. But with apt update 403 Forbidden.
            The strato servers are in the net 217.160.0.0/16AS8560, 87.106.0.0/16AS8560 and 82.165.0.0/16AS8560 in my case. At hetzner I only try with a temporary VM which was already deleted, but there was the same issue.

            I think this should be the strato/ionos net: https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=ionos&source=RIPE

            And this for Hetzner: https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=hetzner&source=RIPE

            AlexP Alexander Palm added a comment - - edited Because I have the same issue, my VPS-Provider is Strato and Hetzner which are completely not work. But via curl I get an answer. But with apt update 403 Forbidden. The strato servers are in the net 217.160.0.0/16AS8560, 87.106.0.0/16AS8560 and 82.165.0.0/16AS8560 in my case. At hetzner I only try with a temporary VM which was already deleted, but there was the same issue. I think this should be the strato/ionos net: https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=ionos&source=RIPE And this for Hetzner: https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=hetzner&source=RIPE

            I have done a try right now from one of this ips:
            inet 217.160.173.32
            inet6 fe80::250:56ff:fe20:7e0f

            AlexP Alexander Palm added a comment - I have done a try right now from one of this ips: inet 217.160.173.32 inet6 fe80::250:56ff:fe20:7e0f
            bryan Bryan Alsdorf added a comment -

            Those networks did get caught up in some rules. Please try now and I'm sorry for the inconvenience.

            Also, can you please provide the output of the following command from several of your systems?

            `systemctl list-timers apt-daily.timer`

            The reason I ask is for the past few weeks around 0420 UTC we are seeing a huge increase in traffic from a few networks, including hetzner and ionos. We believe there are thousands of systems setup to check for updates in the same window of time (which is not the ubuntu default).

            We have added increased capacity for our downloads system and are in the process of adding even more, but would also like to get to the root of the cause.

            bryan Bryan Alsdorf added a comment - Those networks did get caught up in some rules. Please try now and I'm sorry for the inconvenience. Also, can you please provide the output of the following command from several of your systems? `systemctl list-timers apt-daily.timer` The reason I ask is for the past few weeks around 0420 UTC we are seeing a huge increase in traffic from a few networks, including hetzner and ionos. We believe there are thousands of systems setup to check for updates in the same window of time (which is not the ubuntu default). We have added increased capacity for our downloads system and are in the process of adding even more, but would also like to get to the root of the cause.
            acs-ferreira acsfer added a comment -

            # systemctl list-timers apt-daily.timer
            NEXT                         LEFT     LAST                         PASSED    UNIT            ACTIVATES
            Mon 2024-06-10 00:11:42 CEST 16h left Sun 2024-06-09 07:11:19 CEST 30min ago apt-daily.timer apt-daily.service
             
            1 timers listed.
            

            acs-ferreira acsfer added a comment - # systemctl list-timers apt-daily.timer NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2024-06-10 00:11:42 CEST 16h left Sun 2024-06-09 07:11:19 CEST 30min ago apt-daily.timer apt-daily.service   1 timers listed.

            The apt update works without errors now.

            The command output:

             
            systemctl list-timers apt-daily.timer
            NEXT                         LEFT    LAST                         PASSED       UNIT            ACTIVATES        
            Sun 2024-06-09 16:08:16 CEST 7h left Sun 2024-06-09 04:12:39 CEST 4h 54min ago apt-daily.timer apt-daily.service
             
            1 timers listed.
            Pass --all to see loaded but inactive timers, too.
            

            On my System I have a corn job which runs every hour to check for updates and send me a email with the diff output of a apt upgrade dry output if any diff was found. I hope every hour is not a problem, this runs on all my 3 servers for years now. No problems since this issue….

            Thanks for your quick help!

            AlexP Alexander Palm added a comment - The apt update works without errors now. The command output:   systemctl list-timers apt-daily.timer NEXT LEFT LAST PASSED UNIT ACTIVATES Sun 2024-06-09 16:08:16 CEST 7h left Sun 2024-06-09 04:12:39 CEST 4h 54min ago apt-daily.timer apt-daily.service   1 timers listed. Pass --all to see loaded but inactive timers, too. On my System I have a corn job which runs every hour to check for updates and send me a email with the diff output of a apt upgrade dry output if any diff was found. I hope every hour is not a problem, this runs on all my 3 servers for years now. No problems since this issue…. Thanks for your quick help!

            People

              bryan Bryan Alsdorf
              acs-ferreira acsfer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.