• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Update from 7.52 - 7.53 error.

B

Bell Webs

Guest
I just tried an update of the Plesk package and nothing else from 7.52 to 7.53. This is the error that I received.

Trying to set up default qmail permissions... done

===> Installing Qmail server
Trying to set maillog file to /usr/local/psa/var/log/maillog... done
Configuring Qmail...
Trying to generate SSL certificates for TLS sessions... done
Trying to register service qmail... using /sbin/chkconfig
done
Trying to register qmail in alternatives... done
Trying to start Qmail services... Starting qmail: [ OK ]
done
Trying to define super-server internet daemon type... xinetd
Trying to check if xinetd daemon is running... done


START LOGGING: Wed Jun 15 10:04:52 EDT 2005
Trying to stop MySQL server... Stopping MySQL: [ OK ]
done
mysqld (pid 1911) is running...
mysqld is stopped
Making some checks before upgrading

Now BIND server shutting down...

Trying to stop BIND server... Stopping named: [ OK ]
done
Trying to start BIND server... Starting named: [ OK ]
done

BIND server starts Ok.

Trying to start MySQL server... Starting MySQL: [ OK ]
done
Trying to establish test connection... connected
mysqld (pid 2796) is running...
Trying to stop MySQL server... Stopping MySQL: [ OK ]
done
mysqld (pid 2796) is running...
mysqld is stopped

===> Checking for the necessary system accounts
Checking for the system groups and users necessary for Qmail...
Checking for the group 'nofiles'...
Group 'nofiles' already exists

Checking for the user 'alias'...
User 'alias' already exists

Checking for the user 'qmaild'...
User 'qmaild' already exists

Checking for the user 'qmaill'...
User 'qmaill' already exists

Checking for the user 'qmailp'...
User 'qmailp' already exists

Checking for the group 'qmail'...
Group 'qmail' already exists

Checking for the user 'qmailq'...
User 'qmailq' already exists

Checking for the user 'qmailr'...
User 'qmailr' already exists

Checking for the user 'qmails'...
User 'qmails' already exists

Checking for the group 'popuser'...
Group 'popuser' already exists

Checking for the user 'popuser'...
User 'popuser' already exists

Checking for the system groups and users necessary for MySQL...
Checking for the group 'mysql'...
Group 'mysql' already exists

Checking for the user 'mysql'...
User 'mysql' already exists

Checking for the system groups and users necessary for admin server...
Checking for the group 'psaadm'...
Group 'psaadm' already exists

Checking for the user 'psaadm'...
User 'psaadm' already exists

Checking for the system groups and users necessary for Apache...
Checking for the group 'apache'...
Group 'apache' already exists

Checking for the user 'apache'...
User 'apache' already exists

Checking for the group 'psaftp'...
Group 'psaftp' already exists

Checking for the user 'psaftp'...
User 'psaftp' already exists

Checking for the group 'psaserv'...
Group 'psaserv' already exists

Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'apache'... already there
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaftp'... already there
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
group psacln already exists
/usr/local/psa/bin/chrootsh already registered as a login shell
Trying to start MySQL server... Starting MySQL: [ OK ]
done
Trying to establish test connection... connected
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.dump.gz
Database integrity check failed: duplicate values of (action_id, component) exist in table log_components

ERROR while trying to

Aborting...


Has anyone else had this problem and if so, how did you correct it?
 
And now that t he error occured, I logged out the Plesk, then tried to log back in, but just get the logo and copyright info, and the rest of the page is all white.
 
Back
Top