Mysql does not start on the server!

Question

I am unable to start Mysql on the server console. Follows log of Mysql error below:

/*************** /var/log/mysql/error.log ***************/

170525 10:50:35 [Warning] Using Unique option prefix myisam-Recover Instead of myisam-Recover-options is deprecated and will be Removed in a Future release. Please use the full name Instead. 170525 10:50:35 [Note] Plugin 'FEDERATED' is disabled. 170525 10:50:35 Innodb: The Innodb memory heap is disabled 170525 10:50:35 Innodb: Mutexes and rw_locks use GCC Atomic builtins 170525 10:50:35 Innodb: Compressed Tables use zlib 1.2.3.4 170525 10:50:35 Innodb: Initializing buffer pool, size = 128.0M 170525 10:50:35 Innodb: Completed initialization of buffer pool 170525 10:50:35 Innodb: Highest supported file format is Barracuda. Innodb: Log scan progressed Past the checkpoint lsn 97859737067 170525 10:50:35 Innodb: Database was not Shut down normally! Innodb: Starting crash Recovery. Innodb: Reading tablespace information from the . ibd files... Innodb: Restoring possible half-Written data pages from the doublewrite Innodb: buffer... Innodb: Doing Recovery: Scanned up to log Sequence number 97860968674 Innodb: 1 transaction(s) which must be Rolled back or cleaned up Innodb: in Total 1 Row Operations to undo Innodb: Trx id counter is 1C0C5A00 170525 10:50:35 Innodb: Starting an apply batch of log Records to the database... Innodb: Progress in percents: 0 13:50:35 UTC - mysqld got Signal 11 ; 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. We will Try our best to Scrape up some info that will hopefully help diagnose the problem, but Since we have already Crashed, Something is Definitely Wrong and this may fail.

key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K bytes of memory Hope that’s ok; if not, decrease some variables in the Equation.

Thread Pointer: 0x0 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 = 0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f975b99b719] /usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7f975b860ae3] /lib/x86_64-linux-gnu/libpthread.so. 0(+0xfcb0)[0x7f975a5aacb0] /usr/sbin/mysqld(+0x6bbd45)[0x7f975bafdd45] /usr/sbin/mysqld(+0x6bb2a8)[0x7f975bafd2a8] /usr/sbin/mysqld(+0x6bb925)[0x7f975bafd925] /usr/sbin/mysqld(+0x6a868b)[0x7f975baea68b] /usr/sbin/mysqld(+0x6a9b51)[0x7f975baebb51] /usr/sbin/mysqld(+0x64925b)[0x7f975ba8b25b] /usr/sbin/mysqld(+0x6779d9)[0x7f975bab99d9] /usr/sbin/mysqld(+0x6037b0)[0x7f975ba457b0] /lib/x86_64-linux-gnu/libpthread.so. 0(+0x7e9a)[0x7f975a5a2e9a] /lib/x86_64-linux-gnu/libc.so. 6(clone+0x6d)[0x7f9759cd33fd] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.

/******************************/

/*************** my.cnf ***************/

/***********************************************/