如何修复mysql错误日志中的“mbind：不允许操作”

Question

我的 MySQL 错误日志有问题，目前主要由“mbind：不允许操作”行组成（见下文）。为什么会发生，我该如何解决？

这是困扰我的“主要”部分。正如您在下面看到的，并非所有行都是“mbind：不允许操作”。我怀疑 MySQL 查询错误应该是而不是那行，但由于某种原因它们不能写入文件。

MySQL 本身是一个 Docker 容器，其中的日志文件通过以下方式进行处理：

volumes:
- ./mysql/log:/var/log/mysql

有趣的是：

• “docker logs mysql_container”什么也没显示...
• 驻留在同一个卷文件夹中的slow.log 完全没问题，并且里面有真正的慢日志行，没有任何“mbind：不允许操作”！
• 与slow.log 转到general.log 相同——这里也没有问题

有任何想法吗？先感谢您。

2019-04-07T12:56:22.478504Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2019-04-07T12:56:22.478533Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2019-04-07T12:56:22.478605Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.15) starting as process 1
2019-04-07T12:56:22.480115Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2019-04-07T12:56:22.480122Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
mbind: Operation not permitted
[same line goes forever]

PS MySQL 启动并运行良好，没有问题。正是这个 error.log 一直困扰着我并阻止我看到实际的错误。

Answer 1

将功能添加CAP_SYS_NICE到您的容器，直到 MySQL 服务器可以“静默”处理错误。

service:
  mysql:
    image: mysql:8.0.15
    # ...
    cap_add:
      - SYS_NICE  # CAP_SYS_NICE

如果你没有docker-compose，那么你可以定义CAP_SYS_NICE通过

docker run --cap-add=sys_nice -d mysql

参考：

• Docker Seccomp 安全配置文件：https ://docs.docker.com/engine/security/seccomp/
• Docker 资源限制：https : //docs.docker.com/config/containers/resource_constraints/

Answer 2

security_opt在 docker-compose.yml 中添加选项有助于解决这个问题：

database:
  image: mysql:latest
  container_name: mysql_0
  ports:
    - "3306:3306"
  security_opt:
    - seccomp:unconfined