AnsweredAssumed Answered

Starting MySQL.. ERROR! The server quit without updating PID file

Question asked by apkhurana on Mar 8, 2016
Latest reply on Aug 29, 2016 by Stephen_Hughes

160308 11:28:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160308 11:28:46 [Warning] Using unique option prefix log-slave-update instead of log_slave_updates is deprecated and will be removed in a future release. Please use the full name instead.
160308 11:28:46 [Note] Plugin 'FEDERATED' is disabled.
160308 11:28:46 [Note] Plugin 'partition' is disabled.
160308 11:28:46 InnoDB: The InnoDB memory heap is disabled
160308 11:28:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160308 11:28:46 InnoDB: Compressed tables use zlib 1.2.3
160308 11:28:46 InnoDB: Using Linux native AIO
160308 11:28:46 InnoDB: Initializing buffer pool, size = 64.0M
160308 11:28:46 InnoDB: Completed initialization of buffer pool
160308 11:28:46 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160308 11:28:46  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: Last MySQL binlog file position 0 195017, file name /var/lib/mysql/ssgbin-log.000065
160308 11:28:46  InnoDB: Waiting for the background threads to start
160308 11:28:47 InnoDB: 5.5.42 started; log sequence number 93104858507
160308 11:28:47 [Note] Recovering after a crash using /var/lib/mysql/ssgbin-log
160308 11:28:47 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 249, event_type: 2
160308 11:28:47 [Note] Starting crash recovery...
160308 11:28:47 [Note] Crash recovery finished.
17:28:47 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=67108864
read_buffer_size=131072
max_used_connections=0
max_threads=10000
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 = 21941004 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7afda5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6878e4]
/lib64/libpthread.so.0(+0xf710)[0x7f214cb95710]
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.
160308 11:28:47 mysqld_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended

Outcomes