• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Issue Apache update stuck behind unresolved installation processes?

fuzzylines

New Pleskian
Trying to update Apache after the 500 error fiasco. I got it to 2.4.49, but can't get to 2.4.51 as is recommended for security. The update (and others) is queued in SSH Terminal:

2021-10-14 11_14_41-SSH Terminal_ root - Plesk Obsidian 18.0.39.png

But I can't pull it up in the Plesk System Updates (saw that updating via terminal is not recommended/supported). I get the "The System Updates tool is already installing updates in automatic mode. Please try later." error when I check for updates:

2021-10-14 11_15_59-Plesk Obsidian 18.0.39.png

I'm mostly a noob, but I was able to figure out that this is caused by simultaneous install processes happening at once. By using

Code:
ps -aux | grep installer

I see I've got some stuff backed up in the pipes, but no amount of searching told me what this is or what to do about it:

2021-10-14 11_18_10-SSH Terminal_ root - Plesk Obsidian 18.0.39.png

I tried updating Plesk with

Code:
plesk installer

That made the above processes go away for a moment and only show the last line in the image, but then they came back.

I used the

Code:
sudo add-apt-repository ppa:ondrej/apache2
sudo apt install apache2

commands to revert my site back into working condition after getting the 500 error. Can't figure out if that has anything to do with it and I just need to un-add the repository or what. If it's a problem I can't see anything about removing it.

Any tips on how to resolve whatever is happening here? Am I down the wrong rabbit hole and I don't know it? Thank you very much!
 
Back
Top