Is it just me, or have the RPMs created yesterday (Graylog 4.1.4, …) been generated incorrectly? It seems there are several with one or more 0-byte files in them, breaking things…
- The “repository RPMs” seem to be missing the GPG key (the file in the RPM is 0 bytes), making key verification fail. See eg https://packages.graylog2.org/repo/packages/graylog-4.1-repository_latest.rpm
- The graylog 4.1.4 RPM (https://packages.graylog2.org/repo/el/stable/4.1/x86_64/graylog-server-4.1.4-1.noarch.rpm) has an empty systemd unit file in it, which obviously causes the service to fail
For what it’s worth, I’m deploying to CentOS via Ansible.
For now I work around this by overriding the repository RPM and installing an older version of Graylog…
Also, I noted that Graylog 4.1.4 seems not to be announced anywhere, it’s also not on the releases page (but there is a release on Github, and obviously there are the RPMs in the repository).
It appears that the Graylog 4.1.4 RPMs have just been removed from the repository, but the issue with the missing GPG key in the repository RPM still persists.