Skip to main content

MariaDB 10.2 to 10.3: mysqldump failed -- database may be corrupt

Comments

6 comments

  • jonh
    Als0, when trying to open phpmyadmin in a capnel account, it just gets stuck in a what appears to be a loop, i never get into phpmyadmin. Was working fine before the upgrade.
    0
  • jonh
    Phpmyadmin works fine when accessing through WHM, just not through cpanel account area.
    0
  • cPanelLauren
    Hi @jonh Do you have any errors in the cPanel error logs that give some further insight into the issue? You can find them here: /usr/local/cpanel/logs/error_log
    0
  • jonh
    [2019-03-06 22:12:25 -0500] warn [cpanel] Encountered error in Cgi::phpmyadminlink: Cgi::phpmyadminlink failed: (XID kc44wy) Failed to setup the temp session user at bin/admin/Cpanel/session_call.pl line 113. at /usr/local/cpanel/Cpanel/EventHandler.pm line 112. Cpanel::EventHandler::post_event(1, "post", "Cgi", "phpmyadminlink", ARRAY(0x20bdf20), ARRAY(0x20c0540)) called at cpanel.pl line 1440 cpanel::cpanel::__ANON__(Cpanel::Exception=HASH(0x21d1f98)) called at cpanel.pl line 1889 cpanel::cpanel::_api1("Cgi", "cgi", "phpmyadminlink()", "phpmyadminlink", ARRAY(0x20bdf20), "safe_html_encode") called at /usr/local/cpanel/Cpanel/Template/Plugin/Api1.pm line 93 eval {...} called at /usr/local/cpanel/Cpanel/Template/Plugin/Api1.pm line 93 Cpanel::Template::Plugin::Api1::_api1_exec(0, "Cgi", "phpmyadminlink", ARRAY(0x20bdf20)) called at /usr/local/cpanel/Cpanel/Template/Plugin/Api1.pm line 47 Cpanel::Template::Plugin::Api1::_captured_api1_exec("Cgi", "phpmyadminlink", ARRAY(0x20bdf20)) called at /var/cpanel/template_compiles//usr/local/cpanel/base/frontend/paper_lantern/sql/PhpMyAdmin.html.tt line 1 eval {...} called at /var/cpanel/template_compiles//usr/local/cpanel/base/frontend/paper_lantern/sql/PhpMyAdmin.html.tt line 1 eval {...} called at /var/cpanel/template_compiles//usr/local/cpanel/base/frontend/paper_lantern/sql/PhpMyAdmin.html.tt line 1 Template::Provider::__ANON__(Template::Context=HASH(0x20bce30)) called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template/Document.pm line 162 eval {...} called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template/Document.pm line 160 Template::Document::process(Template::Document=HASH(0x20bef70), Template::Context=HASH(0x20bce30)) called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template/Context.pm line 357 eval {...} called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template/Context.pm line 327 Template::Context::process(Template::Context=HASH(0x20bce30), Template::Document=HASH(0x20bef70)) called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template/Service.pm line 94 eval {...} called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template/Service.pm line 91 Template::Service::process(Template::Service=HASH(0x20bc9f8), "/usr/local/cpanel/base/frontend/paper_lantern/sql/PhpMyAdmin."..., HASH(0x20b9578)) called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/Template.pm line 64 Template::process(Template=HASH(0x20bc680), "/usr/local/cpanel/base/frontend/paper_lantern/sql/PhpMyAdmin."..., HASH(0x20b9578), SCALAR(0x1408d30)) called at /usr/local/cpanel/Cpanel/Template.pm line 477 Cpanel::Template::process_template("cpanel", HASH(0x20b9578), HASH(0x1434aa0)) called at cpanel.pl line 1058 cpanel::cpanel::cptt_exectag("/usr/local/cpanel/base/frontend/paper_lantern/sql/PhpMyAdmin."..., 1) called at cpanel.pl line 4409 cpanel::cpanel::run_standard_mode() called at cpanel.pl line 878 cpanel::cpanel::script("cpanel::cpanel", "./frontend/paper_lantern/sql/PhpMyAdmin.html.tt") called at cpanel.pl line 321
    0
  • cPanelLauren
    Hi @jonh What's in the MySQL error logs? Usually, these can be found at /var/lib/mysql/hostname.err? My Assumption at this point is that mysql_upgrade didn't complete properly and needs to be run. Thanks!
    0
  • jonh
    Re-ran the upgrade in whm and now all works fine. Thanks!
    0

Please sign in to leave a comment.