• 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.

Updating the Plesk Server

M

marco114

Guest
I had many issues in the past updating my server with yum update with Plesk on the machine (back in 8.x versions). Things like DNS stopped working (some chroot problem) and locations of files moved which caused Plesk to break.

My server was recently compromised and it took me almost 3 days to get it fixed. I ended up re-installing and moving the data over to a new server.

So now I have a Plesk 9.2.2 box with CentOS 4.2. Since CentOS 4.8 is out and 100s of new packages, it would really be a good idea to update asap.

Is there a good procedure for updating packages so it does not affect Plesk's operation?

Thanks
marc
 
Hello,

Actually updating packages should not affect Parallels Plesk Panel installation if it is for this version of the OS distribution.
I can recommend you to create full server image before updating the system. This will allow you to revert the system back if any issues will occur.
 
There are very few packages that should ever conflict with Plesk. As you noted bind-chroot was one of them. Provided its no longer installed, regularly running:

yum upgrade

is all you need to do.
 
Back
Top