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

Latest plesk update killed everything//

HunterY

New Pleskian
Server load is 100% After update..
47.66 47.78 42.57


Sites take 5 min to load which are just plain HTML sites. Including the plesk panel which barely even loads.

What now? Things were fine up until upgrade.

1TB of files are at risk here...
 
Have you tried to restart it at least and run

# plesk repair installation

?
 
It works, but load is extremely high and speeds are godawful. Yes i've tried restarting lol. Restarting is what actually made it sort of work, but its extremity high load.
 
Any results of troubleshooting? Any related error messages from logs?
 
Any results of troubleshooting? Any related error messages from logs?

No clue cannot access anything to it being so slow lol and on top of that I need to get up in a few hours. BUT did seem disableing apache made the Plesk panel work normally.. So the update has somehow borked Apache seems like.
 
New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: httpd stop failed 18 /usr/sbin/httpd processes are killed Service /etc/init.d/httpd failed to start httpd stop failed 4 /usr/sbin/httpd processes are killed Service /etc/init.d/httpd failed to start . Detailed error descriptions were sent to you by email. Please resolve the issues and clickto generate broken configuration files once again or to generate all configuration files.
 
Checking Plesk version .............................................. [OK]

Checking for custom configuration templates

Some custom configuration templates have been found. The custom
templates have higher priority than default templates in case of
configs generation.
Please check documentation for details:
http://download1.parallels.com/Plesk/PP11/11.0/Doc/en-US/online/plesk-linux-ad vanced-administration-guide/68693.htm[WARNING]

Checking for the JkWorkersFile directive in the Apache configuration [OK]

Checking associations between domains and IP addresses .............. [OK]

Checking for corrupted reference between IP collections and IP
addresses ........................................................... [OK]

Checking for links between APS applications and subscriptions ....... [OK]

Checking for the Zend extension declaraion in php.ini ............... [OK]

Check symbolic links for latest virtual host config files ........... [OK]

Checking for system users home directories consistency .............. [OK]

Checking for records with empty name field in the Configurations table[OK]

Checking for nginx ULIMIT value ..................................... [OK]

Checking for extra configurations in database not owned by any object [OK]

Repairing web server configuration

Reinstall SSL certificates and set the default SSL certificate for all IP addr esses? [Y/n] y
Reinstalling SSL certificates ................................... [OK]
Applying the default SSL certificate to all IP addresses ........ [OK]

Repair server-wide configuration parameters for web servers? [Y/n] y
Repairing server-wide configuration parameters for web servers .. [OK]

Update the file of sharing passwords and permissions of users according to act ual information? [Y/n] n

Repair web server configuration for all domains? [Y/n] y
Repairing web server configuration for all domains .............. [OK]

Checking the usage of PHP handlers .................................. [OK]

Error messages: 0; Warnings: 1; Errors resolved: 0

[root@ns516818 ~]#
 
Strangely, another reboot, and rebooting of apache and Nginx after that reboot seems to have brought everything back up!
 
Back
Top