# Collector-Sidecar for RHEL 9?

**URL:** <https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330>\
**Category:** Graylog Central (peer support)\
**Tags:** sidecar\
**Created:** [June 15, 2022, 6:53pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330 "2022-06-15T18:53:58Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![SalC](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SalC](https://community.graylog.org/u/SalC)\
**Post date:** [June 15, 2022, 6:53pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/1 "2022-06-15T18:53:58Z")

</div>

**1. Describe your incident:**  
Trying to install the Collector-Sidecar 1.2.0-1 on RHEL9 and getting “Error: GPG check FAILED” after installing the repository RPM. I tried ignoring the GPG check (yum --nogpgcheck install graylog-sidecar) however that fails with “package graylog-sidecar-1.2.0-1.x86\_64 does not verify: Header V4 RSA/SHA1 Signature, key ID b1606f22: BAD”

**2. Describe your environment:**  
RHEL 9

**4. How can the community help?**  
Anyone else had this issue and found a solution?

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [June 15, 2022, 6:58pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/2 "2022-06-15T18:58:05Z")

</div>

Try an older version just in case it’s a problem with the current?

---

<div class="post-metadata">

**Author:** ![SalC](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SalC](https://community.graylog.org/u/SalC)\
**Post date:** [June 15, 2022, 7:18pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/3 "2022-06-15T19:18:14Z")

</div>

Good idea, thanks! I don’t see any older versions available through the repository though, when I did:  
yum --showduplicates list graylog-sidecar

it only shows 1.2.0-1

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [June 15, 2022, 7:22pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/4 "2022-06-15T19:22:17Z")

</div>

It should be possible to pull older versions here: [Graylog Package Repository](https://packages.graylog2.org/packages)

---

<div class="post-metadata">

**Author:** ![SalC](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SalC](https://community.graylog.org/u/SalC)\
**Post date:** [June 15, 2022, 7:46pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/5 "2022-06-15T19:46:55Z")

</div>

Thanks! I was trying to browse the URL from the docs, but it was throwing a 404:  
[https://packages.graylog2.org/repo/packages/](https://packages.graylog2.org/repo/packages/)

I installed the older version of the repository: graylog-sidecar-repository-1-1.noarch

Then I tried installing graylog-sidecar 1.0.2-1, however it threw the same error.

Thinking maybe something changed between RHEL 8 and 9 with how it handles GPG keys?

I didn’t find any useful logs.

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [June 15, 2022, 8:12pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/6 "2022-06-15T20:12:46Z")

</div>

> [@SalC](#):
>
> but it was throwing a 404:

Grrr… docs are wrong - try: [Graylog Package Repository](https://packages.graylog2.org/packages) (without “repo” in the path) (@dscryber can fix that with the doc dudes)

Or the version at GitHub here: [Releases · Graylog2/collector-sidecar · GitHub](https://github.com/Graylog2/collector-sidecar/releases)

---

<div class="post-metadata">

**Author:** ![SalC](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SalC](https://community.graylog.org/u/SalC)\
**Post date:** [June 15, 2022, 8:31pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/7 "2022-06-15T20:31:00Z")

</div>

Thanks! I grabbed the file itself (graylog-sidecar-1.2.0-1.x86\_64.rpm) instead of using the repository, and it installs fine. There must be something different with RHEL9 and GPG key verifications with repositories. (I’m testing out RHEL 9, so this is good to know!)

– I found this link, which seems to indicate that RHEL 9 wants stronger GPG keys, which might be why it’s happening:

> <https://github.com/rpm-software-management/rpm/issues/1977>
>
> The \[GPG public key\](https://extras.getpagespeed.com/RPM-GPG-KEY-GETPAGESPEED) c…annot be installed with RPM version 4.16.1.3, found in CentOS Stream 9.
> 
> All prior OS versions had installed it just fine.
> 
> But with RPM 4.16.1.3 there's indeed an unhelpful error message (see https://github.com/rpm-software-management/rpm/issues/1974).
> 
> I did my due search, and the only relevant thread I've found was at 1password community about \[critical bits being set\](https://1password.community/discussion/123891/rpm-gpg-key-is-not-accepted-by-new-rpm-versions) in some data, however, listing packets with \`gpg --list-packets\` reveals nothing critical...
> 
> Any help? I observe exactly the same issue with some keys pre-installed (but not imported) on CentOS 9 stream. For example:
> 
> \`\`\`console
> \[root@12ef34b385a2 rpm-gpg\]# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Extras
> error: /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Extras: key 1 import failed.
> \`\`\`
> 
> But
> 
> \`\`\`console
> \[root@12ef34b385a2 rpm-gpg\]# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Extras-SHA512
> \# import fine, no error
> \`\`\`

— according to poster pmatilai:  
_This is due to RHEL 9 openssl outlawing SHA1 use in signatures. Nothing rpm can do about it._

I found a (temporary) fix before companies update their key to not use SHA-1 signatures:

> **[SHA-1 deprecation in Red Hat Enterprise Linux 9 - Red Hat Customer Portal](https://access.redhat.com/articles/6846411)**
>
> SHA-1 deprecation in the Red Hat Enterprise Linux 9

- update-crypto-policies --set LEGACY
- (reboot)

( this can be reverted down the road by running the same command with `DEFAULT` as the name of the policy.)

PS - I previously needed to do this also on my Graylog server(s) running RHEL 8 to get Active Directory authentication working, since the certificates the Domain Controllers are using don’t meet the “default” crypto requirements

---

<div class="post-metadata">

**Author:** ![jack](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jack/32/8525_2.png) [@jack](https://community.graylog.org/u/jack)\
**Post date:** [June 18, 2022, 9:31am UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/8 "2022-06-18T09:31:02Z")

</div>

Setting the default crypto policy to Legacy is a working but unfavorable solution in my opinion. This lowers the acceptable cryptographic requirements for the entire system.

Is Graylog working on updating it’s repo to support the latest RHEL requirements - SHA256 for example?

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [June 21, 2022, 1:32pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/9 "2022-06-21T13:32:44Z")

</div>

> [@jack](#):
>
> Is Graylog working on updating it’s repo to support the latest RHEL requirements - SHA256 for example?

@dscryber - Can we get a Sidecar Dev to chime in here?

---

<div class="post-metadata">

**Author:** ![SalC](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SalC](https://community.graylog.org/u/SalC)\
**Post date:** [June 21, 2022, 1:58pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/10 "2022-06-21T13:58:54Z")

</div>

Allowing just SHA1 might fix it to, like the RH link mentions:

update-crypto-policies --set DEFAULT:SHA1

… I did it system wide, since in my case the servers are in an isolated network and I wasn’t too worried:

---

<div class="post-metadata">

**Author:** ![dscryber](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/dscryber/32/14178_2.png) [@dscryber](https://community.graylog.org/u/dscryber)\
**Post date:** [June 21, 2022, 5:28pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/11 "2022-06-21T17:28:44Z")

</div>

I’m on it, @tmacgbay . Thanks for asking.

---

<div class="post-metadata">

**Author:** ![dscryber](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/dscryber/32/14178_2.png) [@dscryber](https://community.graylog.org/u/dscryber)\
**Post date:** [June 22, 2022, 4:44pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/12 "2022-06-22T16:44:50Z")

</div>

To @SalC

**From our DEV team:** We are currently not working on updating the repository format to support the latest RHEL requirements. It would be great if @SalC could open a GitHub issue with the details. [GitHub - Graylog2/fpm-recipes: Graylog package build recipes](https://github.com/Graylog2/fpm-recipes)  
Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [July 6, 2022, 4:45pm UTC](https://community.graylog.org/t/collector-sidecar-for-rhel-9/24330/13 "2022-07-06T16:45:24Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
