• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Auto update failed - can't restart update

SuperElf

New Pleskian
Hi,

Auto update failed and Plesk "crashed". I was able to restart Plesk via SSH and when I logged in it offered to repair the failed update so I tried that. A few moments later I was able to log back in again but I could not run the update manually to try to resolve the problem. When I go to Server Management -> Tools & Settings -> Updates and Upgrades the connection just times out.

I see that the update failed because"Package mod_python-3.3.1-14.el6.1.x86_64 already installed and latest version". Seems silly to fail the update because a module is already up-to-date but anyway...

I want to know how to resolve this issue. I was thinking that I could use yum to uninstall the python package and then try to run the updater again but at this point I can not even run the updater at all.

A quick check with "ps" shows that the "/usr/local/psa/admin/bin/autoinstaller" is running so I'm not sure how to proceed.

The currently installed version is 11.0.9 Update #35.

Any advice would be appreciated.
 
OK, I found instructions and ran the following:
/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair

I said "Congratulations! All stages of the upgrade were successful."

But it still shows the same version number and it still times out when trying to go to Server Management -> Tools & Settings -> Updates and Upgrades.

I suppose it will crash again the next time it tries to perform an auto update?
 
That was very helpful and I am able to get into the updater.

I had planned to remove the mod_python via "yum erase" and let the autoupdater install it. Yum lists a lot of dependancies for mod_python and wants to remove 22 packages. Is it safe to uninstall this package and let the updater re-install it? Will autoupdate try to install the mod_python again or will it wait for the *next* update release and skip the failed one?

Thanks!
 
I do not recommend to remove mod_python and especially all required dependences. It can lead to unpredictable consequences.
 
Hello,

I followed the instructions above and everything worked fine for about one week but the very next Plesk update failed again. Same error message. Same result. I followed the steps above again to run "bootstrapper repair" and all is good but I am still at the same version 11.0.9 Update #35 and it looks like I am now stuck and can never update again.

It seems that Plesk will not update anymore because "mod_python-3.3.1-14.el6.1.x86_64 already installed and latest version". I don't want to have to fix Plesk every week. How can I get back on track with normal updates?

Thanks!
 
Back
Top