无法在Google计算引擎上启用bin-log

时间:2018-05-31 20:28:33

标签: mysql google-compute-engine lamp

我试图在Google的LAMP堆栈上设置bin-log。除了log-bin配置外,一切正常。每当我将log-bin = /var/log/mysql/mysql-bin添加到/etc/mysql/mysql.conf.d/mysqld.cnf文件并重新启动mysql时,它都会抛出错误

    # sudo /etc/init.d/mysql restart
[....] Restarting mysql (via systemctl): mysql.serviceJob for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
 failed!

/etc/mysql/mysql.conf.d/mysqld.cnf的内容

[mysqld]
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
datadir         = /var/lib/mysql
log-error       = /var/log/mysql/error.log
bind-address    = localhost
log-bin         = /var/log/mysql/mysql-bin
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

mysql:root可能具有必需的权限,因为mysql可以在/var/log/mysql/error.log上记录错误。但无论如何我也试过这些

chown -R mysql:mysql /var/log/mysql/
chmod 770 /var/log/mysql/
# and
chown -R mysql:root /var/log/mysql/

我已经尝试过这些帖子中给出的解决方案,但没有任何方法可以帮助我

https://serverfault.com/questions/502713/mysql-wont-start-if-i-set-the-log-bin

try to change bin log directory: mysql-bin.index not found (Errcode: 13)

https://dba.stackexchange.com/questions/12346/mysql-bin-log-index-not-found

https://dba.stackexchange.com/questions/97816/cant-enable-binary-logging-index-not-found

https://serverfault.com/questions/382945/why-cant-i-get-the-binlog-in-mysql/383580

Binary log error in mysql

mysql error.log内容

2018-05-31T20:40:15.934303Z 0 [Note] InnoDB: Starting shutdown...
2018-05-31T20:40:16.034693Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2018-05-31T20:40:16.034934Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 180531 20:40:16
2018-05-31T20:40:17.487431Z 0 [Note] InnoDB: Shutdown completed; log sequence number 3080730
2018-05-31T20:40:17.489847Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-05-31T20:40:17.489886Z 0 [Note] Shutting down plugin 'MEMORY'
2018-05-31T20:40:17.489893Z 0 [Note] Shutting down plugin 'CSV'
2018-05-31T20:40:17.489898Z 0 [Note] Shutting down plugin 'sha256_password'
2018-05-31T20:40:17.489901Z 0 [Note] Shutting down plugin 'mysql_native_password'
2018-05-31T20:40:17.490163Z 0 [Note] Shutting down plugin 'binlog'
2018-05-31T20:40:17.490592Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

详细错误日志error-log

1 个答案:

答案 0 :(得分:0)

这可能很容易成为您在其上运行的服务器(AppArmor或SELinux)上的安全设置的问题。请注意,二进制日志实际上不是与通常放置在/ var / log中的常规文本文件相同的意义上的“日志”,并且您可能始终不想将该文件放置在/ var / log中。可能是在您运行的设置中,AppArmor或SELinux规则阻止mysql将任意文件写入/ var / log(这些规则超出了常规文件权限的限制,没有chmod / chown可以避免它们)。您可能要考虑选择另一个目录来将bin-log保存到该目录中。

也许数据库根目录是一个更好的选择(/var/lib/mysql,或者任何配置为用作存储数据库文件的mysql)。

相关问题