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

Failure 7.5.2 -> 7.5.3 on FULLTEXT index

J

jdstevens

Guest
There was a FULLTEXT index on a table in the psa database that cause the database conversion to InnoDB to fail on my system. I was able to drop the index and manually run the updgrade. However, I could not get qmail to run again.

I finally used rsync from a backup server to recover a working system.

DON'T TRY TO UPGRADE WITHOUT A FULL BACKUP THAT CAN PUT YOU BACK WHERE YOU WERE!
 
You must log in or register to reply here.

Similar threads

R
Question Copy Fail, can't update my kernel
Replies
3
Views
3K
scsa20
scsa20
T
Resolved On MariaDB update: "mariadb-dump: Got error: 1932: "Table 'psa.module_dnssec_dnsZone' doesn't exist in engine" when using LOCK TABLES"
Replies
2
Views
2K
TalkBuildHost
T
hume1991
Issue plesk repair fs -verbose failed
Replies
6
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
M
Resolved How to rename database prefix for a single database on a user account
Replies
3
Views
2K
MHC_1
M
Bitpalast
Input How to fix "After APS Catalog removal, removing apps might cause orphaned database (not easily removable)"
Replies
0
Views
2K
Bitpalast
Bitpalast
Back
Top