Would you mind submitting a ticket at tickets.cpanel.net with logins to this machine so we could take a closer look? It's hard to gauge what might be causing the issue with just that log.

It appears InnoDB ends up starting okay after a crash recovery, so it may very well be a setting you're using needs to be adjusted (or a new one added). I would also recommend the use of MariaDB (should be able to upgrade in WHM) as it has better crash handling and utilizes XtraDB (drop-in replacement of InnoDB).

If/once you open a ticket, please email me jesse[at]cpanel.net the ticket number and we will take a closer look.

I had the same issue even with MariaDB.
InnoDB storage engine was crashing randomly every 5-10 days and every InnoDB table was unavailable. Tweaking some settings in my.cnf seems to have solved the problem.

I had the same issue even with MariaDB.
InnoDB storage engine was crashing randomly every 5-10 days and every InnoDB table was unavailable. Tweaking some settings in my.cnf seems to have solved the problem.

Click to expand...

@nickg78 yeah it's not an ultimate solution, just simply a means for better handling and less possible corruption as it's optimized/improved over MySQL. Glad you were able to get your individual issue resolved by tweaking settings - feel free to share your success settings if you'd like!

@nickg78 yeah it's not an ultimate solution, just simply a means for better handling and less possible corruption as it's optimized/improved over MySQL. Glad you were able to get your individual issue resolved by tweaking settings - feel free to share your success settings if you'd like!

Click to expand...

Actually it has to do with the innodb_buffer_pool_size and other settings
tmp_table_size
max_heap_table_size
query_cache_limit
query_cache_size

If they are set too high, InnoDB may crash after a while, due to lack of free RAM.
Setting innodb_buffer_pool_size to 1/4 of the server RAM and the other values to 1/8 of the server RAM seems to be OK. I have also created a script which checks if InnoDB crashes and if so, it restarts MySQL automatically.

Actually it has to do with the innodb_buffer_pool_size and other settings
tmp_table_size
max_heap_table_size
query_cache_limit
query_cache_size

If they are set too high, InnoDB may crash after a while, due to lack of free RAM.
Setting innodb_buffer_pool_size to 1/4 of the server RAM and the other values to 1/8 of the server RAM seems to be OK. I have also created a script which checks if InnoDB crashes and if so, it restarts MySQL automatically.

Yes, the funny thing is that I had set the settings according to mysqltuner's suggestions which caused the random InnoDB crashes. After setting the values to lower values than what mysqltuner advised, the problem was resolved.