mysqld log

160618 19:11:08 mysqld_safe Starting mysqld daemon with databases from /usr/local/emps/var/mysql
160618 19:11:08 [Note] /usr/local/emps/bin/mysqld (mysqld 5.5.49-log) starting as process 4879 ...
160618 19:11:08 InnoDB: The InnoDB memory heap is disabled
160618 19:11:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160618 19:11:08 InnoDB: Compressed tables use zlib 1.2.3
160618 19:11:08 InnoDB: Initializing buffer pool, size = 128.0M
160618 19:11:08 InnoDB: Completed initialization of buffer pool
160618 19:11:08 InnoDB: highest supported file format is Barracuda.
160618 19:11:08  InnoDB: Waiting for the background threads to start
160618 19:11:09 InnoDB: 5.5.49 started; log sequence number 1595675
160618 19:11:09 [Note] Recovering after a crash using mysql-bin
160618 19:11:09 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 245, event_type: 2
160618 19:11:09 [Note] Starting crash recovery...
160618 19:11:09 [Note] Crash recovery finished.
17:11:09 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=1048576
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 = 327373 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/local/emps/bin/mysqld(my_print_stacktrace+0x2e)[0x7781ce]
/usr/local/emps/bin/mysqld(handle_fatal_signal+0x386)[0x65fc26]
/lib64/libpthread.so.0(+0xf7e0)[0x7fac014d07e0]
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.
160618 19:11:09 mysqld_safe mysqld from pid file /usr/local/emps/var/mysql/mysqld.pid ended