Cannot determine your distribution's major version error

[ags-hcs]

Hello everyone,

Recently i have performed update WHM from CENTOS 7.5 [*****] v76.0.7 to 76.08, the update process was successful but when I log in WHM it showed error message :

"[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 with the RPM database. You can rebuild the RPM database using WHM’s ([URL]https://****************/scripts/dialog?dialog=rebuildrpmdb[/URL]) interface (Home » Software » Rebuild RPM Database).”

And also on the WHM I saw no name of our software, it just shown “Unknown”

- Removed -

Please advice for this case.

Thank you and warm regards,

 

[Infopro]

Did you do as suggested in the error?

 

[ags-hcs]

Hi,

Thank you for the reply.

I've not run the suggested on error message. and later, i found on the e-mail, notification from the server

During a recent attempt to run /scripts/upcp, the system detected that your RPM database is unstable. The system cannot install any RPMs, so the upcp script cannot proceed.

FAIL: RPM DB error: error: rpmdb: BDB0113 Thread/process 2243/140717292877888 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
error: rpmdb: BDB0113 Thread/process 2243/140717292877888 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 database in /var/lib/rpm
package glibc is not installed (exit code 1)

For more information on how to troubleshoot this problem, read our Troubleshooting RPM Database Errors documentation.

Could you advice, which one should i do run first for troubleshoot ?

Thanks and regards,

 

[Infopro]

I think I'd run this one first:

You can rebuild the RPM database using WHM’s interface (Home » Software » Rebuild RPM Database).”

 

[ags-hcs]

Hi,

Thanks for the advice.
I've run the first troubleshoot and found no issue.
Thanks for the suggestion.

 

[cPanelLauren]

Hello @ags-hcs


Just to clarify are you indicating that you repaired the RPM database and the issue is no longer occurring?

Thanks!

 

[ags-hcs]

Hi,

Sorry for late reply.

I've tried to repair RPM database, the first issue has solved, it's able to detect current version CENTOS 7.5 v76.0.8 (previously was unknown status) and the error message was disappear but i'm still receiving e-mail notification about RPM database is unstable.

During a recent attempt to run /scripts/upcp, the system detected that your RPM database is unstable. The system cannot install any RPMs, so the upcp script cannot proceed.

 FAIL: RPM DB error: error: rpmdb: BDB0113 Thread/process 2534/140573487233088 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
error: rpmdb: BDB0113 Thread/process 2534/140573487233088 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 database in /var/lib/rpm
package glibc is not installed (exit code 1)

For more information on how to troubleshoot this problem, read our Troubleshooting RPM Database Errors documentation.

Do you have any suggestion for the issue ? Because right now there is an update for cPanel&WH to Version “76.0.9”

Thanks and regards,

 

[cPanelLauren]

Hi @ags-hcs


I need the exact steps you've taken so far. If you rebuilt the rpm database through the UI I need to know the specific output it gave you near the end and if there were any issues. You might also want to open a ticket which you can do with the link in my signature. This way we can look at it more closely. Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved.


Thanks!