Skip to main content
cPanel Technical Support has been heavily impacted by hurricane Beryl and our ability to respond to tickets has been hindered as a result. We appreciate your understanding and patience as we address these delays.

The service “mysql” appears to be down.

Comments

4 comments

  • Haym
    What does /var/lib/mysql/.err contain?
    0
  • cPanelMichael
    Hello, Could you let us know the output from the MySQL error log (/var/lib/mysql/$hostname.err) when attempting to start MySQL? Thank you.
    0
  • Ishank
    It contains the below info
    ========================= 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size:2048 Pages to analyze:32 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size: 2048, Possible space_id count:0 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size:4096 Pages to analyze:16 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size: 4096, Possible space_id count:0 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size:8192 Pages to analyze:8 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size: 8192, Possible space_id count:0 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size:16384 Pages to analyze:4 2018-06-09 09:05:03 3785 [Note] InnoDB: Page size: 16384, Possible space_id count:0 2018-06-09 09:05:03 7f6b68d01740 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. InnoDB: Error: could not open single-table tablespace file ./visualwe_whmc322/tblticketpredefinedcats.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 180609 09:05:03 mysqld_safe mysqld from pid file /var/lib/mysql/srv11.example.com.pid ended 180609 09:10:06 mysqld_safe Logging to '/var/lib/mysql/srv11.example.com.err'. 180609 09:10:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2018-06-09 09:10:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2018-06-09 09:10:06 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path. 2018-06-09 09:10:06 0 [Note] /usr/sbin/mysqld (mysqld 5.6.38) starting as process 4414 ... 2018-06-09 09:10:06 4414 [Note] Plugin 'FEDERATED' is disabled. 2018-06-09 09:10:06 4414 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-06-09 09:10:06 4414 [Note] InnoDB: The InnoDB memory heap is disabled 2018-06-09 09:10:06 4414 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-06-09 09:10:06 4414 [Note] InnoDB: Memory barrier is not used 2018-06-09 09:10:06 4414 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-06-09 09:10:06 4414 [Note] InnoDB: Using Linux native AIO 2018-06-09 09:10:06 4414 [Note] InnoDB: Not using CPU crc32 instructions 2018-06-09 09:10:06 4414 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2018-06-09 09:10:06 4414 [Note] InnoDB: Completed initialization of buffer pool 2018-06-09 09:10:06 4414 [Note] InnoDB: Highest supported file format is Barracuda. 2018-06-09 09:10:06 4414 [Note] InnoDB: Log scan progressed past the checkpoint lsn 756093223 2018-06-09 09:10:06 4414 [Note] InnoDB: Database was not shutdown normally! 2018-06-09 09:10:06 4414 [Note] InnoDB: Starting crash recovery. 2018-06-09 09:10:06 4414 [Note] InnoDB: Reading tablespace information from the .ibd files... 2018-06-09 09:10:06 4414 [ERROR] InnoDB: space header page consists of zero bytes in tablespace ./visualwe_whmc322/tblticketpredefinedcats.ibd (table visualwe_whmc322/tblticketpredefinedcats) 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size:1024 Pages to analyze:64 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size: 1024, Possible space_id count:0 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size:2048 Pages to analyze:32 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size: 2048, Possible space_id count:0 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size:4096 Pages to analyze:16 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size: 4096, Possible space_id count:0 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size:8192 Pages to analyze:8 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size: 8192, Possible space_id count:0 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size:16384 Pages to analyze:4 2018-06-09 09:10:06 4414 [Note] InnoDB: Page size: 16384, Possible space_id count:0 2018-06-09 09:10:06 7f98e4ced740 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. InnoDB: Error: could not open single-table tablespace file ./visualwe_whmc322/tblticketpredefinedcats.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 180609 09:10:06 mysqld_safe mysqld from pid file /var/lib/mysql/srv11.example.com.pid ended ===============================
    0
  • cPanelMichael
    Hello @Ishank, It looks like InnoDB is corrupted on your system. We provide a resource on how to troubleshoot InnoDB corruption at: Tutorial - InnoDB Corruption Repair Guide Thank you.
    0

Please sign in to leave a comment.