• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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