mysqld.err2017-03-03 13:21:02 4063 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
2017-03-03 13:21:02 4063 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-03 13:21:02 4063 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-03 13:21:02 4063 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-03 13:21:02 4063 [Note] InnoDB: Memory barrier is not used
2017-03-03 13:21:02 4063 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-03-03 13:21:02 4063 [Note] InnoDB: Using Linux native AIO
2017-03-03 13:21:02 4063 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-03 13:21:02 4063 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-03 13:21:02 4063 [Note] InnoDB: Completed initialization of buffer pool
2017-03-03 13:21:02 4063 [ERROR] InnoDB: Space id in fsp header 1416128883,but in the page header 824195850
10:21:02 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=262144
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 = 133629 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+0x57)[0x84c2ef7]
/usr/sbin/mysqld(handle_fatal_signal+0x3c1)[0x8266451]
/lib/libz.so.1(adler32_z+0x11f)[0xb777b4bf]
/lib/libz.so.1(adler32+0x2b)[0xb777b79b]
/usr/sbin/mysqld[0x854917b]
/usr/sbin/mysqld[0x85e5544]
/usr/sbin/mysqld[0x862adf2]
/usr/sbin/mysqld[0x85998e9]
/usr/sbin/mysqld[0x84ebe67]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x81b6bf1]
/usr/sbin/mysqld[0x82e7204]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x948)[0x82eb828]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x83d)[0x81b024d]
/usr/sbin/mysqld(main+0x1b)[0x818faeb]
/lib/libc.so.6(__libc_start_main+0xf4)[0xb71bb5c4]
/usr/sbin/mysqld[0x81a4d9c]
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.