Amazon Linux 2023's dnf runs into 404s when querying Erlang and RabbitMQ yum repos [Questions] #14332
-
Community Support Policy
RabbitMQ version used4.1.2 Erlang version used27.3.x Operating system (distribution) usedAmazon Linux 2023 How is RabbitMQ deployed?RPM package rabbitmq-diagnostics status outputSee https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics Logs from node 1 (with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 2 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 3 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location Steps to deploy RabbitMQ clusterI followed the guide here to setup the repos: https://www.rabbitmq.com/docs/install-rpm Steps to reproduce the behavior in question
advanced.configSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location Application code# PASTE CODE HERE, BETWEEN BACKTICKSKubernetes deployment file# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKSWhat problem are you trying to solve?Why is the repo giving 404 errors? Did the URL of the repo change? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
@austinleach-tcgplayer there was some work on those repos last night (ET) and it all should be good now. In fact, I can see multiple 200 metadata (.xml) and .rpm requests per second in the logs of both hosts. I suspect that you may be running into a Cloudflare cache. I will clear it once again. One recommendation I have is: update your repository file. There aren't any repo changes (yet, there will be in 1-3 months, we will migrate to new repos under new subdomains) but the source repo was removed from the docs. You don't need the source repo, and we likely won't provide one going forward (RabbitMQ source and the |
Beta Was this translation helpful? Give feedback.
-
|
On an x86-64 Fedora 42 host in a data centre in Ontario, I have: cat /etc/yum.repos.d/rabbitmq.repo
# In /etc/yum.repos.d/rabbitmq.repo
##
## Zero dependency Erlang RPM
##
[modern-erlang]
name=modern-erlang-el9
# Use a set of mirrors maintained by the RabbitMQ core team.
# The mirrors have significantly higher bandwidth quotas.
baseurl=https://yum1.rabbitmq.com/erlang/el/9/$basearch
https://yum2.rabbitmq.com/erlang/el/9/$basearch
repo_gpgcheck=1
enabled=1
gpgkey=https://github.com/rabbitmq/signing-keys/releases/download/3.0/cloudsmith.rabbitmq-erlang.E495BB49CC4BBE5B.key
gpgcheck=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
metadata_expire=300
pkg_gpgcheck=1
autorefresh=1
type=rpm-md
[modern-erlang-noarch]
name=modern-erlang-el9-noarch
# Use a set of mirrors maintained by the RabbitMQ core team.
# The mirrors have significantly higher bandwidth quotas.
baseurl=https://yum1.rabbitmq.com/erlang/el/9/noarch
https://yum2.rabbitmq.com/erlang/el/9/noarch
repo_gpgcheck=1
enabled=1
gpgkey=https://github.com/rabbitmq/signing-keys/releases/download/3.0/cloudsmith.rabbitmq-erlang.E495BB49CC4BBE5B.key
https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc
gpgcheck=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
metadata_expire=300
pkg_gpgcheck=1
autorefresh=1
type=rpm-md
##
## RabbitMQ Server
##
[rabbitmq-el9]
name=rabbitmq-el9
baseurl=https://yum2.rabbitmq.com/rabbitmq/el/9/$basearch
https://yum1.rabbitmq.com/rabbitmq/el/9/$basearch
repo_gpgcheck=1
enabled=1
# Cloudsmith's repository key and RabbitMQ package signing key
gpgkey=https://github.com/rabbitmq/signing-keys/releases/download/3.0/cloudsmith.rabbitmq-server.9F4587F226208342.key
https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc
gpgcheck=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
metadata_expire=300
pkg_gpgcheck=1
autorefresh=1
type=rpm-md
[rabbitmq-el9-noarch]
name=rabbitmq-el9-noarch
baseurl=https://yum2.rabbitmq.com/rabbitmq/el/9/noarch
https://yum1.rabbitmq.com/rabbitmq/el/9/noarch
repo_gpgcheck=1
enabled=1
# Cloudsmith's repository key and RabbitMQ package signing key
gpgkey=https://github.com/rabbitmq/signing-keys/releases/download/3.0/cloudsmith.rabbitmq-server.9F4587F226208342.key
https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc
gpgcheck=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
metadata_expire=300
pkg_gpgcheck=1
autorefresh=1
type=rpm-mdsudo dnf install -y erlang rabbitmq-serverthat produces So, the CDN cache is the only hypothesis I have. I've cleared the entire cache for |
Beta Was this translation helpful? Give feedback.
-
|
I've been getting the same 404 errors since Friday and still the same this morning. I'll try again in a bit once the cache has had a chance to fully clear. Regarding updating my repository file, I'm happy to do that but your link goes to the page that I followed initially. Is there something I need to change? |
Beta Was this translation helpful? Give feedback.
-
|
There was no maintenance of any kind last Friday or over the weekend. My recommendation was to replace your |
Beta Was this translation helpful? Give feedback.
-
|
@austinleach-tcgplayer in addition to the example above, I think I now see what's going on. Due to how Cloudsmith installation instructions and RPM repo mirroring work, you effectively have three repos configured even though you arguably need just one. I don't know why my So the path that 404s is
And some clients hit a path that has no architecture details at all. |
Beta Was this translation helpful? Give feedback.
-
|
I have tried one more thing to eliminate
So either you run into an older But the two repos that actually contain the packages have an Specifically for Amazon Linux 2023, I can see several kinds of requests: so yes, this host's
|
Beta Was this translation helpful? Give feedback.
-
|
I figured it out and it's completely on me. I didn't properly escape the repo URLs in the shell script I wrote to deploy this. So the Sorry for the confusion and thank you for your help. |
Beta Was this translation helpful? Give feedback.
I have tried one more thing to eliminate
dnf's caching:.repofile with what the RPM guide recommends on the same Fedora 42 hostmodern-erlang-*torabbitmq-erlang-*dnf update -ythen produces a warning that the signing keys are not available and fetches them from GitHubdnf install -y rabbitmq erlangthen works just like beforeSo either you run into an older
dnf/libdnfbehavior of sorts, or something was different in the RPM guide in the past.But the two repos that actually contain the packages have an
:architecturecomponent in their requested path, and both work just fine for me in several tests on two different hosts.Specifically for Amazon Linu…