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

WordPress Toolkit: updates do not start

Mario ITN

New Pleskian
After a failed automatic upgrade from 12.0.18 to 12.5.30 it is impossible to use the WordPress toolkit update features (for plugins, themes, ecc.).

Starting an update within WordPress Toolikit will lead to a 0% progress bar for hours with the task never really started. Cancelling the update will result in a proper delete of the task from the Plesk's mySQL long tasks tables.

Sheduled backups are also not performed with no error notice. Manual Backups are performed without any problems.

I cleared the long tasks tables following http://kb.odin.com/en/120209

I also checked /etc/cron.d/plesk-backup-manager-task and it appears as


-rw-r--r-- 1 root root 111 set 26 2013 plesk-backup-manager-task




and contains 1 line:

14,29,44,59 * * * * root [ -x /opt/psa/admin/sbin/backupmng ] && /opt/psa/admin/sbin/backupmng >/dev/null 2>&1


Anything else I could check?
 
First of all I'd suggest you fix your Plesk with

# plesk repair installation
 
Thank you for your answer.

Does it work on 12.0.18#70? I thought it was a 12.5 feature... I would have run
# plesk repair all -n
for a check first in that case.

Anyway because everything else it is working fine I would like to be sure not to break anything trying to repair this.
 
Sorry it was probably my English.... when I wrote "failed automatic upgrade from 12.0.18 to 12.5.30" I meant that the upgrade was not performed for some error. It was attempt by Plesk automatic updates but failed and when I logged in Plesk panel I just found the old version with a red notice about the upgrade attempted.


I hope it is clear now... sorry again for the misunderstanding.
 
For Plesk 12.0.18 you can use

# /usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair

for repairing your Plesk.
 
Back
Top