Unable to update sec rules on CloudLinux 7.4

Community support forums for the free/delayed modsecurity rules feed. There is no such thing as a bad question here as long as it pertains to using the delayed modsecurity rules feed. Newbies feel free to get help getting started or asking questions that may be obvious.
andreihn
New Forum User
New Forum User
Posts: 4
Joined: Wed Nov 29, 2017 4:14 am
Location: Romania

Unable to update sec rules on CloudLinux 7.4

Unread post by andreihn »

Hi,

Once install mod_sec on Plesk Onyx I get the bellow err. It is something with the URL ... can you suggest what need to be tweaked? Thanks.

Plesk 17.5.3 CentOS 7 1705170317.16
CloudLinux release 7.4 (Georgy Grechko)


Failed to install the ModSecurity rule set: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg: Signature made Tue Nov 28 13:07:08 2017 WET using RSA key ID 4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1818 66DF 9DAC A40E 5B42 9B08 FFBD 5D0A 4520 AFA9 TERM environment variable not set. One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: tortix-common/7.4/x86_64 Command '/bin/bash < /tmp/tmpQgMJyP/aum' returned non-zero exit status 1 Unable to download tortix rule set
jgodwin
Atomicorp Support Staff
Atomicorp Support Staff
Posts: 39
Joined: Mon Sep 14, 2009 12:15 pm

Re: Unable to update sec rules on CloudLinux 7.4

Unread post by jgodwin »

What are the contents of any of these files that you have present on your system:

/etc/centos-release
/etc/redhat-release
/etc/os-release
andreihn
New Forum User
New Forum User
Posts: 4
Joined: Wed Nov 29, 2017 4:14 am
Location: Romania

Re: Unable to update sec rules on CloudLinux 7.4

Unread post by andreihn »

It is /etc/redhat-release with the bellow content


CloudLinux release 7.4 (Georgy Grechko)
Post Reply