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

Plesk 8.1.0 and Mysql 5 post-upgrade problem

L

linuxcrazy

Guest
Hi,
I upgraded my CentOS 4 using "yum upgrade" and everything went fine. With other updates Mysql version was upgraded to 5.0.51 as shown by execution of command

rpm -qa mysql
mysql-5.0.51-1.el4.art

logon to mysql database server via command prompt works fine but logging on to Plesk admin panel is yielding the following error:

ERROR: PleskFatalException
bad column in table: `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',

0: /usr/local/psa/admin/plib/common_func.php3:153
psaerror(string 'bad column in table: `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',')
1: /usr/local/psa/admin/plib/SQLParser.php:119
SQLParser->parseError(string ' `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',')
2: /usr/local/psa/admin/plib/SQLParser.php:105
SQLParser->_parseLineInTable(string ' `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',')
3: /usr/local/psa/admin/plib/SQLParser.php:52
SQLParser::parseLine(string ' `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',', integer '7')
4: :
array_walk(array, array)
5: /usr/local/psa/admin/plib/SQLParser.php:23
SQLParser->getArray(array)
6: /usr/local/psa/admin/plib/SQLParser.php:30
SQLParser->handleDatabase()
7: /usr/local/psa/admin/plib/MySQL5FixBinaryColumns.php:36
MySQL5FixBinaryColumns::run()
8: /usr/local/psa/admin/auto_prepend/auth.php3:93

I tried to google for similar error and solution but no luck.

Can anybody suggests the reason and possible solution to this problem? Your help is highly appreciated.

Thanks
 
Solved

Finally i was able to solve this issue. For people who encounter the same issue and instead of striking their head with pain here is what i did to solve:

dropped the psa db in mysql and re-created with the dump i took prior to upgrade.

So rule of thumb is make backup before you are bold enough to proceed with upgrade :).

Thanks
 
Back
Top