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

Plesk massively slow after recent update.

Slavik

Basic Pleskian
Since the latest update my plesk panel has been horribly slow.

For example, creating a new subscription today took over 90 seconds to do!

Have tried restarting the PSA service, and failing that, tried a full server reboot to no avail.

Any suggestions?
 
Latest security microupdate delivered only one psa-suexec file and nothing else.
Try to troubleshoot the problem in Plesk logs with help of article http://kb.parallels.com/111283


The only recent error was

2013-04-20T21:37:21+02:00 CRIT (2): Smb_Exception_NotFound: File specified by cd028ec0-28b8-1522-d870-1fb708962427 was not found
file: /usr/local/psa/admin/plib/CommonPanel/Update/LogFile.php
line: 36
code: 0

However, I ran

mysql -uadmin -p`cat /etc/psa/.psa.shadow`;
use psa
delete from longtasks where type="panel-update";
reboot

and then the update installed.


All the other logs show nothing to suggest this sudden slowness, all the websites on the server, and running scripts form CLI are as quick as usual, its just Plesk itself which is crawling so slowly I could manually create vhosts faster...
 
Managed to locate and fix the error, seems that the failed update was still attempting to run... killing the PID instantly fixed everything back to normal...
 
Back
Top