• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

httpdmng taking all sites down for a few minutes

brainforge

Basic Pleskian
/usr/local/psa/admin/bin/httpdmng --reconfigure-domain mydomain.com
(a) This command took all sites down while it was running - not just mydomain.com
(b) It took a few minutes - I seem to recall the old /usr/local/psa/admin/bin/websrvmng was a lot faster (but I had not used it for a few weeks before upgrading to Plesk 10).

The same thing happens when adding a customer through the Plesk panel.
Again I cannot recall this happening with Plesk 9.
Looking at the processes it is running things like:
/usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/sbin/httpdmng --reconfigure-batch /usr/local/psa/tmp/httpdmng-batch-g1qYgq
 
I had created a tech ticket with Parallels
They were able to see that it is a problem more with servers that have quite a few domains
and expecially if they have custom vhosts.conf files.

I only have 300 domains and if i add an alias or domain to the server i can expect HELL for the next 20 min.

They said they are now aware of the issue and it will be fixed in some future update.
 
I solved this problem.

1. Go into the the subdomains table in the psa database and delete any problematic subdomain records.

2. Then rename the subdomain file folders to subdomain_temp and then recreate the subdomain in Plesk.

3. Go back and delete the new subdomain folder that is created and rename the original one back to the proper name.

Everything should work.

I must also note my dissatisfaction having to waste a few hours every time I have to upgrade Plesk. Paying $35/month for this should be flawless. Please do more internal testing before releasing patches.
 
Back
Top