Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MySQL Wont Start

Discussion in 'Database Discussions' started by Mane Lira, Sep 6, 2017.

Tags:
  1. Mane Lira

    Mane Lira Registered

    Joined:
    Sep 6, 2017
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    MEX
    cPanel Access Level:
    Root Administrator
    Hello,

    Any one can help with this isseu please.

    Code:
    Waiting for “mysql” to start ……[2017-09-06 18:19:19 -0500] warn [restartsrv_mysql] The system encountered an error while starting the “mysql” service with the command “/etc/init.d/mysql start”: The subprocess reported error number 1 when it ended. at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1358. Cpanel::ServiceManager::Base::warn(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "The system encountered an error while starting the \x{e2}\x{80}\x{9c}mysql\x{e2}\x{80}"...) called at /usr/local/cpanel/Cpanel/ServiceManager/Manager/Initd.pm line 103 Cpanel::ServiceManager::Manager::Initd::start(Cpanel::ServiceManager::Manager::Initd=HASH(0x15dc5b8), Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 828 Cpanel::ServiceManager::Base::start(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Services/Mysql.pm line 56 Cpanel::ServiceManager::Services::Mysql::start(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 703 Cpanel::ServiceManager::Base::restart(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "graceful", undef) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 537 Cpanel::ServiceManager::Base::run_from_argv(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "--verbose", "--html", "--wait", "--verbose") called at bin/restartsrv_base.pl line 72 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 98 eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 89 Try::Tiny::try(CODE(0x15c25e0), Try::Tiny::Catch=REF(0xb99ce0)) called at bin/restartsrv_base.pl line 107 …[2017-09-06 18:19:25 -0500] warn [restartsrv_mysql] The system encountered an error while starting the “mysql” service with the command “/etc/init.d/mysql start”: The subprocess reported error number 1 when it ended. at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1358. Cpanel::ServiceManager::Base::warn(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "The system encountered an error while starting the \x{e2}\x{80}\x{9c}mysql\x{e2}\x{80}"...) called at /usr/local/cpanel/Cpanel/ServiceManager/Manager/Initd.pm line 103 Cpanel::ServiceManager::Manager::Initd::start(Cpanel::ServiceManager::Manager::Initd=HASH(0x15dc5b8), Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 828 Cpanel::ServiceManager::Base::start(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Services/Mysql.pm line 56 Cpanel::ServiceManager::Services::Mysql::start(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 703 Cpanel::ServiceManager::Base::restart(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "graceful", undef) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 537 Cpanel::ServiceManager::Base::run_from_argv(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "--verbose", "--html", "--wait", "--verbose") called at bin/restartsrv_base.pl line 72 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 98 eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 89 Try::Tiny::try(CODE(0x15c25e0), Try::Tiny::Catch=REF(0xb99ce0)) called at bin/restartsrv_base.pl line 107 …[2017-09-06 18:19:31 -0500] warn [restartsrv_mysql] The system encountered an error while starting the “mysql” service with the command “/etc/init.d/mysql start”: The subprocess reported error number 1 when it ended. at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1358. Cpanel::ServiceManager::Base::warn(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "The system encountered an error while starting the \x{e2}\x{80}\x{9c}mysql\x{e2}\x{80}"...) called at /usr/local/cpanel/Cpanel/ServiceManager/Manager/Initd.pm line 103 Cpanel::ServiceManager::Manager::Initd::start(Cpanel::ServiceManager::Manager::Initd=HASH(0x15dc5b8), Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 828 Cpanel::ServiceManager::Base::start(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Services/Mysql.pm line 56 Cpanel::ServiceManager::Services::Mysql::start(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 703 Cpanel::ServiceManager::Base::restart(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "graceful", undef) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 537 Cpanel::ServiceManager::Base::run_from_argv(Cpanel::ServiceManager::Services::Mysql=HASH(0x15c8208), "--verbose", "--html", "--wait", "--verbose") called at bin/restartsrv_base.pl line 72 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 98 eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 89 Try::Tiny::try(CODE(0x15c25e0), Try::Tiny::Catch=REF(0xb99ce0)) called at bin/restartsrv_base.pl line 107 …failed.
    
    Cpanel::Exception::Services::StartError Service Status
    
    Service Error
    (XID d8nqb4) The “mysql” service failed to start.
    
    Startup Log
    Starting MySQL.170906 18:19:30 mysqld_safe Logging to '/var/lib/mysql/server2.example.org.err'.
    170906 18:19:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     ERROR!
    
    Log Messages
    170906 18:19:31 mysqld_safe mysqld from pid file /var/lib/mysql/server2.example.org.pid ended
    InnoDB: To fix the problem and start mysqld:
    170906 18:19:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    170906 18:19:24 mysqld_safe mysqld from pid file /var/lib/mysql/server2.example.org.pid ended
    InnoDB: To fix the problem and start mysqld:
    170906 18:19:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    170906 18:19:18 mysqld_safe mysqld from pid file /var/lib/mysql/server2.example.org.pid ended
    
    mysql has failed. Contact your system administrator if the service does not automagically recover.
    
    
     
  2. Eminds

    Eminds Well-Known Member

    Joined:
    Nov 10, 2016
    Messages:
    204
    Likes Received:
    12
    Trophy Points:
    18
    Location:
    India
    cPanel Access Level:
    Root Administrator
    Login to the server with root and check the logs at /var/lib/mysql/server2.example.org.err and post them here.
     
  3. webhostuk

    webhostuk Well-Known Member

    Joined:
    Sep 11, 2013
    Messages:
    106
    Likes Received:
    10
    Trophy Points:
    18
    cPanel Access Level:
    Website Owner
    It seems to be a InnoDB issue I guess. As suggested can you past the error logs while it fails.
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,165
    Likes Received:
    1,371
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    The previous posts are correct. We'll need to see the output from the MySQL error log to better troubleshoot the issue. Also, if it does turn out to be InnoDB corruption, we provide a guide on that at:

    InnoDB Corruption Repair Guide

    Thank you.
     
Loading...

Share This Page