• 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

ERROR: PleskMainDBException

Status
Not open for further replies.

simonbmadsen

New Pleskian
Hello

I have encountered an error in a troubleshooting session on Paralells Plesk panel 11.0.9 , Centos 5.9

When i go to a customers -> control panel -> mail tab and try to click "Change Settings" it displays the following error:

Code:
ERROR: PleskMainDBException
MySQL query failed: Table 'psa.GL_settings' doesn't exist
0: common_func.php3:220
db_query(string 'SELECT `value` FROM GL_settings WHERE param = 'enabled'')
1: common_func.php3:307
db_query_ex(string 'SELECT `value` FROM GL_settings WHERE param = '?(paramName)'', array)
2: GreyListManager.php:1067
GreyListManager->_getSetting(string 'enabled', string 'false')
3: GreyListManager.php:112
GreyListManager->isCheckingEnabled()
4: class.MailPreferencesForm.php:81
MailPreferencesForm->assign(array, array, object of type BsDomain, object of type DSMail, string 'censored@mail', object of type PleskUserException)
5: client.domain.mail.properties.php:143
plesk__client__domain__mail__properties->accessItem(string 'GET', NULL null)
6: UIPointer.php:595
UIPointer->access(string 'GET')
7: plesk.php:45

The reason why i want to change mail settings is because i have a customer who has an external mail server to handle their mail for their domain. When they try to use a PHP function from their hosted page it sends to the plesk server itself somehow.
 
Looks like your psa database is not correctly updated. You can find SQL query for creation missing GL_settings table in file - /usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/db/psa_db.sql

CREATE TABLE `GL_settings` (
`param` varchar(255) character set ascii COLLATE ascii_bin NOT NULL UNIQUE,
`value` varchar(255) character set ascii COLLATE ascii_bin NOT NULL,
PRIMARY KEY `param` (`param`)
) ENGINE=InnoDB DEFAULT CHARSET utf8;
 
Hey

Thank you for your reply.

Can you think of any reason this table should not be there? could it be caused by a bug or could it be on purpose? could there be any consequences by adding it ?
 
Who knows? Maybe it was uncompleted upgrade or something else.
 
Status
Not open for further replies.
Back
Top