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!

The mysql service failed to start error

Discussion in 'Database Discussion' started by CompWebStudio, Feb 24, 2019.

  1. CompWebStudio

    CompWebStudio Registered

    Feb 24, 2019
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator

    I have a problem with a server MySQL after update Cpanel to v78.0.11 on CENTOS 7.6.
    After update but not yet restart serwer my service SQL goes down and all website are whitout database. Service don't start after restart this and full restart server.

    Lower is my problem:

    Waiting for “mysql” to start ………Unrecognized configuration options may have caused the MySQL startup errors. The system has attempted to auto-update your MySQL configuration file for your MySQL version. This should resolve any errors that stem from an outdated MySQL configuration file. …Unrecognized configuration options may have caused the MySQL startup errors. The system has attempted to auto-update your MySQL configuration file for your MySQL version. This should resolve any errors that stem from an outdated MySQL configuration file. …failed.
    Cpanel::Exception::Services::StartError Service Status
    Service Error
    (XID q58dv7) The “mysql” service failed to start.
    Startup Log
    Feb 24 14:36:15 systemd[1]: Starting MySQL Server...
    Log Messages
    mysql has failed. Contact your system administrator if the service does not automagically recover.
    And here is some part of log mysqld.log:
    2019-02-24T18:02:01.309162Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
    2019-02-24T18:02:01.309575Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.25) starting as process 10712 ...
    2019-02-24T18:02:01.312557Z 0 [Note] InnoDB: PUNCH HOLE support available
    2019-02-24T18:02:01.312593Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2019-02-24T18:02:01.312598Z 0 [Note] InnoDB: Uses event mutexes
    2019-02-24T18:02:01.312603Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    2019-02-24T18:02:01.312607Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2019-02-24T18:02:01.312610Z 0 [Note] InnoDB: Using Linux native AIO
    2019-02-24T18:02:01.312993Z 0 [Note] InnoDB: Number of pools: 1
    2019-02-24T18:02:01.313100Z 0 [Note] InnoDB: Using CPU crc32 instructions
    2019-02-24T18:02:01.314672Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    2019-02-24T18:02:01.321980Z 0 [Note] InnoDB: Completed initialization of buffer pool
    2019-02-24T18:02:01.323919Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
    2019-02-24T18:02:01.335810Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-02-24T18:02:01.337347Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 209214260698
    2019-02-24T18:02:01.337399Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 209214316726
    2019-02-24T18:02:01.338117Z 0 [Note] InnoDB: Database was not shutdown normally!
    2019-02-24T18:02:01.338127Z 0 [Note] InnoDB: Starting crash recovery.
    2019-02-24T18:02:01.345281Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
    2019-02-24T18:02:01.345308Z 0 [Note] InnoDB: Trx id counter is 163592960
    2019-02-24T18:02:01.345396Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percent: 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
    2019-02-24T18:02:01.852711Z 0 [Note] InnoDB: Apply batch completed
    2019-02-24T18:02:01.952998Z 0 [Note] InnoDB: Cleaning up trx with id 52968641
    2019-02-24T18:02:02.097048Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
    2019-02-24T18:02:02.097069Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2019-02-24T18:02:02.097273Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2019-02-24T18:02:02.139788Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2019-02-24T18:02:02.142358Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
    2019-02-24T18:02:02.142387Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
    2019-02-24T18:02:02.143322Z 0 [Note] InnoDB: Waiting for purge to start
    2019-02-24 19:02:02 0x7f0a0a7fc700  InnoDB: Assertion failure in thread 139681102546688 in file fut0lst.ic line 85
    InnoDB: Failing assertion: == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to [URL='']MySQL Bugs[/URL].
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: [URL='']MySQL :: MySQL 5.7 Reference Manual :: 14.21.2 Forcing InnoDB Recovery[/URL]
    InnoDB: about forcing recovery.
    18:02:02 UTC - mysqld got signal 6 ;
    This could be because you hit a bug. It is also possible that this binary
    or one of the libraries it was linked against is corrupt, improperly built,
    or misconfigured. This error can also be caused by malfunctioning hardware.
    Attempting to collect some information that could help diagnose the problem.
    As this is a crash and something is definitely wrong, the information
    collection process might fail.
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 206883 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
    Thread pointer: 0x7f0a04000900
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    stack_bottom = 7f0a0a7fbdb0 thread_stack 0x40000
    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (0): Connection ID (thread ID): 0
    Status: NOT_KILLED
    The manual page at [URL='']MySQL :: MySQL 8.0 Reference Manual :: B.6.3.3 What to Do If MySQL Keeps Crashing[/URL] contains
    information that should help you find out what is causing the crash.
    #1 CompWebStudio, Feb 24, 2019
    Last edited by a moderator: Feb 25, 2019
  2. Eminds

    Eminds Well-Known Member

    Nov 10, 2016
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Apr 11, 2011
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator
    Hello @CompWebStudio,

    The link provided in the previous post is a good place to start when troubleshooting InnoDB corruption. As far as why this happened after the update to version 78, can you share the contents of the /etc/my.cnf file on this system? EX:

    cat /etc/my.cnf
    Thank you.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice