Regular problems with rpm base
Hi,
I regularly receive such email messages:
ERROR: The system cannot update the /var/cpanel/sysinfo.config file because it cannot determine your distribution's major version.
Run the following command: rpm -qf --queryformat '%{VERSION}\n' /etc/redhat-release
Output other than the numbers 6 or 7 indicates a problem. Open a support ticket or resolve the issue manually.
After that, I fix it in CLI with: # rm -rf /var/lib/rpm/__* # rpm --rebuilddb
After some time it is repeated again. Could you someone tell me what is wrong with my cPanel instance? How can I fix it permanently? Thanks.
After that, I fix it in CLI with: # rm -rf /var/lib/rpm/__* # rpm --rebuilddb
After some time it is repeated again. Could you someone tell me what is wrong with my cPanel instance? How can I fix it permanently? Thanks.
-
Hello, It looks like your RPM database becomes corrupted based on the information you have provided. Have you noticed any issues with the completion of package installations or updates on this system? Are you able to successfully run the "yum clean all" and "yum update" commands? Thank you. 0 -
Are you able to successfully run the "yum clean all" and "yum update" commands?
I see following errors again:# yum clean all error: rpmdb: BDB0113 Thread/process 17537/140184988993344 failed: BDB1507 Thread died in Berkeley DB library error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main: Error: rpmdb open failed
Tried to fix with:# rm -f /var/lib/rpm/__* # rpm --rebuilddb # yum clean all Loaded plugins: fastestmirror, langpacks, tsflags, universal-hooks Cleaning repos: EA4 cpanel-addons-production-feed base extras imunify360 imunify360-alt-php imunify360-ea-php-hardened updates Cleaning up everything Cleaning up list of fastest mirrors # yum update Loaded plugins: fastestmirror, langpacks, tsflags, universal-hooks EA4 | 2.9 kB 00:00:00 cpanel-addons-production-feed | 2.9 kB 00:00:00 base | 3.6 kB 00:00:00 extras | 3.4 kB 00:00:00 imunify360 | 2.6 kB 00:00:00 http://SSlLukA1wSyNNxxG:GDfVwjKV6hsVzyPee48KfNrH@repo.alt.cloudlinux.com/centos/alt-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 alt-php repository for CentOS 7 - x86_64), 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=imunify360-alt-php ... 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 imunify360-alt-php or subscription-manager repos --disable=imunify360-alt-php 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=imunify360-alt-php.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-alt-php: [Errno 256] No more mirrors to try. http://SSlLukA1wSyNNxxG:GDfVwjKV6hsVzyPee48KfNrH@repo.alt.cloudlinux.com/centos/alt-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 401 - Unauthorized
Looks like something wrong with imunify360 repository, right?0 -
Hello, Yes, the error message suggests an issue with your Imunify360 YUM Repo. Are you using the latest available version of the Imunify360 software on your system? I found a similar issue in a previous support ticket where updating to the latest Imunify360 version addressed the issue. Thank you. 0
Please sign in to leave a comment.
Comments
3 comments