Newly converted to Alma Linux from a predominantly CentOS shop here. We’ve got a bunch of CentOS 7 servers which we intend to use into their eventual end-of-support date, but some CentOS 6 servers that we need to migrate, and figure that for at least some of them, we might as well get them started off on the right foot with Alma Linux 8.
So I’m building a base Alma Linux 8 VM template, and I want it to have an unconfigured Zabbix Agent on it, and I’m following the instructions on this page. When I type the command rpm -Uvh https://repo.zabbix.com/zabbix/5.0/rhel/8/x86_64/zabbix-release-5.0-1.el8.noarch.rpm, I get the MOST peculiar error:
This makes no sense to me, since network connectivity is working. I’m able to ping hosts both on my local AND to remote (internet) networks, and when I try a wget from another machine to that same URL, it downloads just fine. I’ve checked and my NetworkManager.service is running (obviously), and while there DID seem to be an issue with systemd-resolve.service, it is now running as well – still no dice!
I can’t answer that question, but I can note that there is no need to use rpm for that.
The yum in CentOS 7 can take an URL, perhaps even before, and dnf in Alma definitely can.
The dnf probably uses curl to download packages. I have no idea how the rpm does it. If they do use different tool and there is some HTTPS/SSL/TLS magick …
Many installation instructions continue to write ‘rpm -Uvh’ even though there is no need for it any more. Worse yet, yum/dnf keeps history of transactions and use of rpm adds no record to it. The only thing that I do use rpm for is to query metadata from installed packages. Never to modify the system.
Your original screenshot lists zabbix-release-5.0.1.el8.noarch.rpm. The file on the site is zabbix-release-5.0-1.el8.noarch.rpm. (The dash??) That would cause the 404 error.