mysql 启动时日志报错，求助这是啥原因了

bing0726

[iyunv@sb_dbtest2 ~]# service mysqld start
Starting MySQL (Percona Server). ERROR! The server quit without updating PID file (/mysql/data/sb_dbtest2.pid).
日志入下
151015 14:57:52 mysqld_safe Starting mysqld daemon with databases from /mysql/data
2015-10-15 14:57:53 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2015-10-15 14:57:53 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2015-10-15 14:57:53 11966 [Note] Plugin 'FEDERATED' is disabled.
2015-10-15 14:57:53 11966 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-10-15 14:57:53 11966 [Note] InnoDB: The InnoDB memory heap is disabled
2015-10-15 14:57:53 11966 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-10-15 14:57:53 11966 [Note] InnoDB: Memory barrier is not used
2015-10-15 14:57:53 11966 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-10-15 14:57:53 11966 [Note] InnoDB: Using Linux native AIO
2015-10-15 14:57:53 11966 [Note] InnoDB: Using CPU crc32 instructions
2015-10-15 14:57:53 11966 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-10-15 14:57:53 11966 [Note] InnoDB: Completed initialization of buffer pool
2015-10-15 14:57:53 11966 [Note] InnoDB: Highest supported file format is Barracuda.
2015-10-15 14:57:53 11966 [Note] InnoDB: 128 rollback segment(s) are active.
2015-10-15 14:57:53 11966 [Note] InnoDB: Waiting for purge to start
2015-10-15 14:57:53 11966 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.22-rel71.0 started; log sequence number 1626017
2015-10-15 14:57:53 11966 [Note] Recovering after a crash using mysql-bin
2015-10-15 14:57:53 11966 [Note] Starting crash recovery...
2015-10-15 14:57:53 11966 [Note] Crash recovery finished.
06:57:53 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=402653184
read_buffer_size=2097152
max_used_connections=0
max_threads=153
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 = 1022144 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
/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0x8f092c]
/mysql/bin/mysqld(handle_fatal_signal+0x461)[0x67a6d1]
/lib64/libpthread.so.0(+0xf790)[0x7f09f0288790]
/lib64/libc.so.6(+0x1283f6)[0x7f09eea613f6]
/usr/lib64/libcrypto.so.6(+0x7fdba)[0x7f09ef6f0dba]
/usr/lib64/libcrypto.so.6(lh_insert+0xa6)[0x7f09ef6f1106]
/usr/lib64/libcrypto.so.6(OBJ_NAME_add+0x6b)[0x7f09ef6cd8eb]
/usr/lib64/libssl.so.6(SSL_library_init+0x1d1)[0x7f09efa1d441]
/mysql/bin/mysqld(ssl_start+0x3c)[0xba45cc]
/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x110f)[0x5b712f]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f09ee957d5d]
/mysql/bin/mysqld[0x5a9bbd]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
151015 14:57:53 mysqld_safe mysqld from pid file /mysql/data/sb_dbtest2.pid ended

sky

问题可能的原因有多种，具体什么原因最好的办法是先查看下错误日志：
1、可能是/usr/local/mysql/data/mysql.pid文件没有写的权限
解决方法 ：给予权限，执行 “chown -R mysql:mysql /var/data” “chmod -R 755 /usr/local/mysql/data”  然后重新启动mysqld！

2、可能进程里已经存在mysql进程
解决方法：用命令“ps -ef|grep mysqld”查看是否有mysqld进程，如果有使用“kill -9  进程号”杀死，然后重新启动mysqld！

3、可能是第二次在机器上安装mysql，有残余数据影响了服务的启动。
解决方法：去mysql的数据目录/data看看，如果存在mysql-bin.index，就赶快把它删除掉吧，它就是罪魁祸首了。本人就是使用第三条方法解决的 ！

4、mysql在启动时没有指定配置文件时会使用/etc/my.cnf配置文件，请打开这个文件查看在[mysqld]节下有没有指定数据目录(datadir)。
解决方法：请在[mysqld]下设置这一行：datadir = /usr/local/mysql/data

5、skip-federated字段问题
解决方法：检查一下/etc/my.cnf文件中有没有没被注释掉的skip-federated字段，如果有就立即注释掉吧。

6、错误日志目录不存在
解决方法：使用“chown” “chmod”命令赋予mysql所有者及权限

7、selinux惹的祸，如果是centos系统，默认会开启selinux
解决方法：关闭它，打开/etc/selinux/config，把SELINUX=enforcing改为SELINUX=disabled后存盘退出重启机器试试。

sky

你贴出出来的日志我没看见报错。

bing0726

是这样啊  我是用两台服务器+keepalived做的主主复制，开始的时候是可以起来的，我把keepalived起来后，将1台mysql停掉测试，然后就起不来了，