centos mysql 启动不了

[Java-我去]

今天显得没事，想改一下日志的路径，然后就。。。 起不来了

max_allowed_packet = 20M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# Recommended in standard MySQL setup
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

[mysqld_safe]
log-error=/data/logs/mysql/mysqld.log
#log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid


#log=/data/logs/mysql/all.log

#log-output=FILE
#general-log=1
#general_log_file=/data/logs/mysql/general.log


#log-output=FILE
#slow_query_log=1
#slow_query_log_file=/data/logs/mysql/show.log
#long_query_time=10 

怎么改都启动不了，改为原来的还是启动不了
启动了很长时间，提示

[root@iZ25mz6qyb8Z ~]# service mysqld restart 
Redirecting to /bin/systemctl restart  mysqld.service
Job for mysqld.service failed. See 'systemctl status mysqld.service' and 'journalctl -xn' for details.

然后按照提示执行

[root@iZ25mz6qyb8Z ~]# systemctl status mysqld.service
mysqld.service - MySQL Community Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
   Active: activating (start-post) since 四 2016-08-04 14:22:40 CST; 4min 26s ago
  Process: 13385 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS)
  Process: 13374 ExecStartPre=/usr/bin/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 13385 (code=exited, status=0/SUCCESS);         : 13386 (mysql-systemd-s)
   CGroup: /system.slice/mysqld.service
           `-control
             |-13386 /bin/bash /usr/bin/mysql-systemd-start post
             `-14383 sleep 1

8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: mysqld.service holdoff time over, scheduling restart.
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: Stopping MySQL Community Server...
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: Starting MySQL Community Server...
8月 04 14:22:40 iZ25mz6qyb8Z mysqld_safe[13385]: 160804 14:22:40 mysqld_safe Logging to '/data/logs/mysql/mysqld.log'.
8月 04 14:22:40 iZ25mz6qyb8Z mysqld_safe[13385]: 160804 14:22:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
8月 04 14:22:40 iZ25mz6qyb8Z mysqld_safe[13385]: 160804 14:22:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

[root@iZ25mz6qyb8Z ~]# journalctl -xn
-- Logs begin at 日 2016-07-24 17:40:39 CST, end at 四 2016-08-04 14:22:40 CST. --
8月 04 14:20:01 iZ25mz6qyb8Z CROND[12895]: (root) CMD (/usr/lib64/sa/sa1 1 1)
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: mysqld.service operation timed out. Stopping.
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysqld.service has failed.
-- 
-- The result is failed.
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: Unit mysqld.service entered failed state.
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: mysqld.service holdoff time over, scheduling restart.
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: Stopping MySQL Community Server...
-- Subject: Unit mysqld.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysqld.service has begun shutting down.
8月 04 14:22:40 iZ25mz6qyb8Z systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysqld.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysqld.service has begun starting up.
8月 04 14:22:40 iZ25mz6qyb8Z mysqld_safe[13385]: 160804 14:22:40 mysqld_safe Logging to '/data/logs/mysql/mysqld.log'.
8月 04 14:22:40 iZ25mz6qyb8Z mysqld_safe[13385]: 160804 14:22:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
8月 04 14:22:40 iZ25mz6qyb8Z mysqld_safe[13385]: 160804 14:22:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

网上也查了说什么权限的问题，试了半天，还是不行 搞了大半天了，谁知道是怎么回事吗

[Java-我去]

自己顶顶啊顶啊顶啊

[Java-我去]

自己解决了，重启 一下服务器就没事了，不知怎么回事

[致命的西瓜]

运行时无法重新加载的文件 只要重启对应的服务就可以

[ACMAIN_CHM]

检查一下MYSQL本身的错误日志。

[阳泉酒家小当家]

有可能是mysql没有操作你指定的新目录的权限导致的

[ssk_12344321]

查看一下日志文件 就知道了 应该是不小心修改了 某个参数

[qq_36100464]

13386 /bin/bash /usr/bin/mysql-systemd-start post这个进程如果存在的话直接KILL掉就可以正常启动了。这种问题不能只按照提示来解决，还得看日志。