php update failing

117434

Verified User
Joined
Nov 4, 2022
Messages
21
Earlier today I updated some packages using update all that I had not yet done.

Then I had 4 updates that needed doing. PHP was the one I really wanted to do but update failed 3 times and closed. I then rebooted the entire server in the hopes that might solve the problem.

I realize this is not enough info so please tell me what I need to provide so that you might help. I now have the entire log on local machine.

Alma-Linux server running the 5/16/26 1.70xx version of DA.
 
Hello,

What will you see if you run?

Bash:
da build list_removals

You might remove old libraries, in case they are shown by the first command.

Bash:
da build used_configs

You might review the custom/php/configure.php* files, if they are shown by the second command.

Other than that you might have dependencies issues and/or RAM, disk space related problems.
 
I just discovered that I don't know where to run either of those commands. I am guessing there is a command line option somewhere I never explored?
 
I just discovered that I don't know where to run either of those commands. I am guessing there is a command line option somewhere I never explored?

If this is the case, you'd better get someone to fix it for you. I won't guide you as well as anybody else on how to use SSH and run commands as "root".

If you still want to learn the basics, you might start with the following articles:

- https://docs.directadmin.com/operat...naging-with-ssh.html#managing-server-over-ssh
 
The removable items are also visible in the CustomBuild GUI. Server Management -> CustomBuild -> Remove. Example:

1779885265565.png
 
Thanks for the help. As I tend to agree with @zEitEr I won't add anything to this thread other than to say the answer was in the error log and you do have to what you need to do from root.

The error log showed this:
Public key for cpp-8.5.0-28.el8_10.alma.1.x86_64.rpm is not installed. Failing package is: cpp-8.5.0-28.el8_10.alma.1.x86_64

And what that meant was that on this older install I had not updated the public key. Google can help you with that.
 
Back
Top