When Plesk fails to upgrade

- by

I’ve had this issue before: you get a new server, the image is a few revisions behind the current release and your first line of business is to upgrade the system.

A few minutes later you check and find that Plesk refuses to start. Bugger. Now what?

My Customer Support Gurus always know what to do, but in an effort to not disturb them at night here’s what they did to make it all work again. These instructions work on a CentOS 5 system with Plesk 9.0.1 installed.

/usr/local/psa/admin/sbin/autoinstaller --select-release-current --show-components | grep upgrade
tail -f /var/log/sw-cp-server/error_log
uname -a
cat /etc/redhat-release
wget -c http://kb.parallels.com/Attachments/12669/Attachments/sw-cp-server-1.0-6.201004011130.centos5.x86_64.rpm
rpm -Uhv sw-cp-server-1.0-6.201004011130.centos5.x86_64.rpm
/etc/init.d/psa stopall
/etc/init.d/psa start

Voila – Plesk works again πŸ˜‰

If you enjoy my content, please consider supporting me on Ko-fi. In return you can browse this whole site without any pesky ads! More details here.

2 thoughts on “When Plesk fails to upgrade”

  1. After spending hours looking through Parallel’s forums, this is the only post that’s actually worked.

    (One thing though, you missed the ‘t’ on ‘init’ on the last command).

    Thank you, thank you, thank you!

  2. Hi Andrew,

    Very glad this worked for you – especially considering that the post is several years old. And thanks for letting me know about the typo, I’ve amended the post.

    All the best–


Leave a Comment!

This site uses Akismet to reduce spam. Learn how your comment data is processed.