update_db_cache errors after update to cPanel 70
Hi,
After the recent update from cPanel 68 to 70, we receive the following error on one of our cPanel servers multiple times a day:
Cron /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr/local/cpanel/scripts/update_db_cache :
Any advise would be appreciated. Thanks.
Cpanel::Exception::Database::Error/(XID qv4dmw) The system received an error from the "MySQL" database "mysql": 1143 (SELECT command denied to user ''@'localhost' for column 'sid' in table 'webform_submitted_data')
at /usr/local/cpanel/Cpanel/Exception/CORE.pm line 336.
Cpanel::Exception::create("Database::Error", ARRAY(0x2fabc78)) called at /usr/local/cpanel/Cpanel/Exception.pm line 61
Cpanel::Exception::__ANON__(__CPANEL_HIDDEN__, ARRAY(0x2fabc78)) called at /usr/local/cpanel/Cpanel/DBI.pm line 200
Cpanel::DBI::_create_exception(Cpanel::DBI::Mysql::st=HASH(0x2f8a2d8), "DBD::mysql::st execute failed: SELECT command denied to user "..., undef) called at /usr/local/cpanel/Cpanel/DBI.pm line 188
Cpanel::DBI::_error_handler("DBD::mysql::st execute failed: SELECT command denied to user "..., Cpanel::DBI::Mysql::st=HASH(0x2f8a2d8), undef) called at bin/update_db_cache.pl line 336
Script::Update::DB::Cache::can_get_mysql_usage(HASH(0xd8a8b8), HASH(0xe1ab28), Cpanel::DB::Map::Collection::Index=HASH(0x2f744f0)) called at bin/update_db_cache.pl line 63
Script::Update::DB::Cache::script("Script::Update::DB::Cache") called at bin/update_db_cache.pl line 36
Any advise would be appreciated. Thanks.
-
Hello @Bdzzld, Are you able to access cPanel for the account associated with the database referenced in that error message? If so, browse to cPanel >> MySQL Databases and remove the referenced MySQL user from that database, and then re-add that user to the database. Let me know if that helps. Thank you. 0 -
@cPanelMichael : There is no MySQL user mentioned in the error message as far as I can tell. 0 -
@cPanelMichael: The ticket was opened as requested: [quote] Your Support Request ID is: 9659401 0 -
Hello @Bdzzld, Thanks, I'm monitoring the support ticket and will update this thread with the outcome once it's complete. 0 -
Hello, To update, it looks like this was the result of an improperly added security definer on the view associated with one of the database users on the system. Thank you. 0
Please sign in to leave a comment.
Comments
6 comments