InnoDB crashed, no MySQL service available

Dear Friends, I have a severe issue on my VPS. After the common cron upgrade of cPanel at 2:00 AM tonight, the MySQL service died. At the morning as I tried to recover that, I saw this error message in the error log file: 2018-04-17 22:58:39 31551 [Note] Plugin 'FEDERATED' is disabled. 2018-04-17 22:58:39 31551 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-04-17 22:58:39 31551 [Note] InnoDB: The InnoDB memory heap is disabled 2018-04-17 22:58:39 31551 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-04-17 22:58:39 31551 [Note] InnoDB: Memory barrier is not used 2018-04-17 22:58:39 31551 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-04-17 22:58:39 31551 [Note] InnoDB: Using Linux native AIO 2018-04-17 22:58:39 31551 [Note] InnoDB: Using CPU crc32 instructions 2018-04-17 22:58:39 31551 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2018-04-17 22:58:39 31551 [Note] InnoDB: Completed initialization of buffer pool 2018-04-17 22:58:39 31551 [Note] InnoDB: Highest supported file format is Barracuda. 2018-04-17 22:58:39 31551 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2888683 2018-04-17 22:58:39 31551 [Note] InnoDB: Database was not shutdown normally! 2018-04-17 22:58:39 31551 [Note] InnoDB: Starting crash recovery. 2018-04-17 22:58:39 31551 [Note] InnoDB: Reading tablespace information from the .ibd files... 2018-04-17 22:58:39 31551 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 0. 2018-04-17 22:58:39 7fd43daaa740 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. 2018-04-17 22:58:39 31551 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation As you see this is the error log from 22:58 PM. I opened a ticket with cPanel, but got only a link how to solve the InnoDB problems, which I can't. On the whole day I tried different ways, the only which was successful was when I moved every ib* files from the /var/lib/mysql/ directory and restarted the mysql service. However it caused another problems with the .frm files of the databases. So I "restored" the original status and now I have no any idea what to do. Please help, because I have more than 60.000 different files in the mysql directory. Thank you for any help in advance!

Peter Horvath

April 18, 2018 00:36

I got very thorough answer from cPanel CUstomer Care, so I see that the issue wasn't caused by the upgrade. However, it is still there. Please help. Thank you!

Infopro

April 18, 2018 01:28

Check to see if this thread is of any use to you:

May 14, 2018 15:16

Check to see if this thread is of any use to you:
I read a lot of articles including the

cPanelMichael

May 15, 2018 16:36

Hello @Peter Horvath, If the information on the Thank you.

InnoDB crashed, no MySQL service available

Comments

Didn't find what you were looking for?