• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Software updates and restart of server

brownbag

Basic Pleskian
I'm just setting up my first plesk server on Ubuntu and it's in test/demo mode. I've applied software updates once and it was nice and simple.

But I presume that some software updates (such as an upgrade to a new Ubuntu version) would require a reboot or a restart of some essential services. How do I know the requirements for such an upgrade?

I'll need to inform my customers before applying such an upgrade so need to know before I upgrade software if any services will be unavailable for a period of time.
 
Indeed, the restart of some services may be required when upgrading. But usually, it takes very little time, downtime is very short. It all depends on the number of sites or mailboxes. In hundreds, it can reach several minutes, no more.
 
Is there any way to know if a restart of a server or a key service will occur when you upgrade? If I've got customers in different timezones, I can't just do an upgrade at nighttime.
 
Back
Top