Unsatisfied dependencies - WHM/Cpanel won't touch it
Technical support at cPanel/WHM can't seem to help with this so as a last resort I'm asking here. Server is actually running fine, but last nights pack updates produced errors.
When I run: 'rpm -Va --nofiles --nodigest' (which was suggested by cpanel/WHM tech support as a solution to the error message) for me to get an insight into what's wrong, I am receiving the following error message:
Unsatisfied dependencies for remi-release-7.9-5.el7.remi.noarch:
epel-release = 7 is needed by (installed) remi-release-7.9-5.el7.remi.noarch
I find it odd that whm/cpanel support is telling me this is a database corruption issue and does not want to try to fix it, when it was their software update process that seems to be having trouble.
They are directing me to: https://rpm.org/user_doc/db_recovery.html
Which I'm averse to doing - looks like some heavy lifting there and whereas the server is serving sites, I feel this is above my pay grade. Any suggestions appreciated.
-
The database that they are referring to is the RPM database, not a MySQL/Postgress database. They also (prob.) won't deal with this because the Remi repository is not needed by cPanel/WHM. A guess is this is all related to CentOS V7 EOL and the repositories no longer being available?
0 -
Here is another failure that just appeared. What is going on with cpanel/WHM here? Can someone interpret this so I can take appropriate action? Thanks kindly.
Update log preview: ...
...
[2024-07-06 22:30:09 -0400] E [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages” command (process 767953) reported error number 1 when it ended.
...
[2024-07-06 22:31:05 -0400] Processing: Checking CloudLinux installation
[2024-07-06 22:31:05 -0400] - Processing command `/usr/local/cpanel/bin/cloudlinux_update`
[2024-07-06 22:31:05 -0400] - Finished command `/usr/local/cpanel/bin/cloudlinux_update` in 0.258 seconds
[2024-07-06 22:31:05 -0400] Processing: Updating plugins data cache
[2024-07-06 22:31:05 -0400] - Processing command `/usr/local/cpanel/bin/refresh_plugin_cache`
[2024-07-06 22:31:05 -0400] - Finished command `/usr/local/cpanel/bin/refresh_plugin_cache` in 0.166 seconds
[2024-07-06 22:31:05 -0400] Processing: Ensuring SSL certificate information for CCS is up to date.
[2024-07-06 22:31:05 -0400] - Processing command `/usr/local/cpanel/scripts/ccs-check --run --ssl`
[2024-07-06 22:31:05 -0400] - Finished command `/usr/local/cpanel/scripts/ccs-check --run --ssl` in 0.025 seconds
[2024-07-06 22:31:05 -0400] Processing: Ensure cpanel-plugins yum repo exists
[2024-07-06 22:31:06 -0400] - Finished in 0.652 seconds
[2024-07-06 22:31:06 -0400] Processing: Checking Addon Licenses
[2024-07-06 22:31:06 -0400] - Finished in 0.013 seconds
[2024-07-06 22:31:06 -0400] Processing: Updating Public Suffix List
[2024-07-06 22:31:06 -0400] Processing: Checking End Of Life for current version.
[2024-07-06 22:31:06 -0400] - Finished in 0.240 seconds
[2024-07-06 22:31:06 -0400] Processing:
[2024-07-06 22:31:06 -0400] Maintenance complete.
=> Log closed Sat Jul 6 22:31:06 2024
----------------------------------------------------0 -
/usr/local/cpanel/scripts/update-packages command also use yum therefore if it's not working due to 3rd party repos then the update will fail.
Andrew N. - cPanel Plesk VMWare Certified Professional
Do you need immediate assistance? 20 minutes response time!* Open a ticket
EmergencySupport - Professional Server Management and One-time Services0 -
SOLVED by level 2 cpanel tech who was thorough and clear in what was happening:
It appears that the
epel-release
package on the server was partially corrupted, and interactions regarding it resulting in dnf errorsTo diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue.
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.This is also why the cPanel update was failing.
What I did was manually remove the package from the installed list, and then re-installed it:
rpm -v -e --nodeps --justdb epel-release
dnf install epel-release
Transaction Summary
Install 1 PackageTotal size: 24 k
Installed size: 34 k
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] epel-release-8-20.el8.noarch.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : epel-release-8-20.el8.noarch 1/1
Running scriptlet: epel-release-8-20.el8.noarch 1/1
Many EPEL packages require the CodeReady Builder (CRB) repository.
It is recommended that you run /usr/bin/crb enable to enable the CRB repository.Verifying : epel-release-8-20.el8.noarch 1/1
Installed:
epel-release-8-20.el8.noarchComplete!
0
Please sign in to leave a comment.
Comments
4 comments