• 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 doesn't start after upgrade

LordH

New Pleskian
After upgrade from 8.3.0 to 8.4.0 i couldn't start plesk. It gives me these error
> /etc/init.d/psa start
Starting xinetd service... done
Starting named service... done
Starting mysql service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... not installed
Starting psa-spamassassin service... done
Syntax OK
ERROR 1175 (HY000) at line 1: You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
Starting Plesk... done
System ist Suse 10.2 i586
 
At least I managed to get the PCP running again.

I discovered, that

/usr/local/psa/admin/conf/httpsd.conf

had only 1 byte. The error_log showed a port conflict (that's why I tried to check the port configured). I restored an old backup saved by PSA and httpsdctl could start the PSA server again.

The update routine obviously badly failed and Parallels yet found NO WAY to help their users.
 
Thank you so much! This was the reason why i couldn't start plesk. But i have to stop plesk with the command /etc/init.d/psa stop before, because status said "psa dead but subsys locked". So it didn't start before i stopped it.
And second thing was a MySQL-Error. In the config of MySQL (my.cnf) i used safe-updates and when i commented out everything worked fine for me.
 
Back
Top