• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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 filed 5.11.29 to 5.11.30

E

EduartK

New Pleskian
===> Upgrading database

Trying to start service mysqld... mysqld (pid 989) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 011005029
DATABASE ERROR!!!
Previous product version is 11.0.9, but previous database
version is 011005029. In most of cases it is result of
previous upgrade try failure. Please, restore previous version
from backup, and try again or contact technical support.

ERROR while trying to check database version
 
You must log in or register to reply here.

Similar threads

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
1K
TalkBuildHost
T
E
Resolved Made a mistake, changed server hostname, please advise
Replies
2
Views
2K
elliotpa04
E
enerspace
Plesk repair / constraint violation: 1062 Duplicate entry
Replies
6
Views
3K
Hangover2
Hangover2
Z
Issue Firewall stopped working after update to Plesk Obsidian v18.0.77 on Debian 11.11
Replies
12
Views
6K
Kaspar
K
Azurel
Issue MariaDB 11.8.8: STRICT_TRANS_TABLES suddenly enabled after reboot AlmaLinux 9.7 → 9.8
Replies
2
Views
706
Azurel
Azurel
Back
Top