GreatSQL社区

搜索

[讨论中] 万里数据库备库的日志报错

56 4 前天 10:42
万里数据库备库的日志报错,如下:


2026-04-11T03:29:56.815153+08:00 35 [ERROR] [MY-012592] [InnoDB] Operating system error number 13 in a file operation.
2026-04-11T03:29:56.817398+08:00 35 [ERROR] [MY-012595] [InnoDB] The error means mysqld does not have the access rights to the directory.
   请问下如下报错是什么目录的权限不够,怎么验证是什么目录?
数据库版本是万里商业版1.0,操作系统是麒麟v10的。                                                                                                                                          

全部回复(4)
丁一 前天 10:45
补充完整日志:
2026-04-11T00:53:10.433796+08:00 0 [System] [MY-010910] [Server] /data/wisdri/greatdb/greatdb/bin/greatdbd: Shutdown complete (mysqld 8.0.32-23-GreatDB1.0.0.6118032-GA-1)  GreatDB V1.0, Release GA-1, Revision 801aa636.
2026-04-11T00:53:10.758481+08:00 0 [Warning] [MY-011068] [Server] The syntax '--ssl=off' is deprecated and will be removed in a future release. Please use --tls-version='' instead.
2026-04-11T00:53:10.758520+08:00 0 [Warning] [MY-011069] [Server] The syntax '--master-info-repository' is deprecated and will be removed in a future release.
2026-04-11T00:53:10.758530+08:00 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-repository' is deprecated and will be removed in a future release.
2026-04-11T00:53:10.758569+08:00 0 [Warning] [MY-011068] [Server] The syntax 'log_slave_updates' is deprecated and will be removed in a future release. Please use log_replica_updates instead.
2026-04-11T00:53:10.758657+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_parallel_type' is deprecated and will be removed in a future release. Please use replica_parallel_type instead.
2026-04-11T00:53:10.758665+08:00 0 [Warning] [MY-011069] [Server] The syntax '--replica-parallel-type' is deprecated and will be removed in a future release.
2026-04-11T00:53:10.758680+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_preserve_commit_order' is deprecated and will be removed in a future release. Please use replica_preserve_commit_order instead.
2026-04-11T00:53:10.758693+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_parallel_workers' is deprecated and will be removed in a future release. Please use replica_parallel_workers instead.
2026-04-11T00:53:10.758767+08:00 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2026-04-11T00:53:10.758829+08:00 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2026-04-11T00:53:10.758837+08:00 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2026-04-11T00:53:10.758936+08:00 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2026-04-11T00:53:10.758977+08:00 0 [System] [MY-010116] [Server] /data/wisdri/greatdb/greatdb/bin/greatdbd (mysqld 8.0.32-23-GreatDB1.0.0.6118032-GA-1) starting as process 1126728
2026-04-11T00:53:10.771957+08:00 0 [Warning] [MY-000081] [Server] option 'innodb-sort-buffer-size': unsigned value 536870912 adjusted to 67108864.
2026-04-11T00:53:10.774088+08:00 0 [Warning] [MY-013267] [InnoDB] The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.
2026-04-11T00:53:10.774176+08:00 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=1610612736. Please use innodb_redo_log_capacity instead.
2026-04-11T00:53:10.778324+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-04-11T00:53:15.306274+08:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2026-04-11T00:53:17.324129+08:00 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/data/wisdri/greatdb/greatdb3306/data' in the path is accessible to all OS users. Consider choosing a different directory.
2026-04-11T00:53:17.415158+08:00 0 [Warning] [MY-010539] [Repl] Recovery from master pos 488702345 and file mysql_bin_30001.000086 for channel ''. Previous relay log pos and relay log file had been set to 1524, /data/wisdri/greatdb/greatdb3306/log/relay-log/relay-log.000002 respectively.
2026-04-11T00:53:17.420175+08:00 5 [Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2026-04-11T00:53:17.422766+08:00 5 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'repl@192.168.100.80:3306',replication started in log 'mysql_bin_30001.000086' at position 488702345
2026-04-11T00:53:17.427480+08:00 0 [System] [MY-010931] [Server] /data/wisdri/greatdb/greatdb/bin/greatdbd: ready for connections. Version: '8.0.32-23-GreatDB1.0.0.6118032-GA-1'  socket: '/data/wisdri/greatdb/greatdb3306/data/mysql.sock'  port: 3306  GreatDB V1.0, Release GA-1, Revision 801aa636.
2026-04-11T00:53:17.441900+08:00 0 [Warning] [MY-011302] [Server] Plugin mysqlx reported: 'Failed at SSL configuration: "SSL context is not usable without certificate and private key"'
2026-04-11T00:53:17.442838+08:00 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /tmp/mysqlx.sock
2026-04-11T03:29:56.815153+08:00 35 [ERROR] [MY-012592] [InnoDB] Operating system error number 13 in a file operation.
2026-04-11T03:29:56.817398+08:00 35 [ERROR] [MY-012595] [InnoDB] The error means mysqld does not have the access rights to the directory.
                                                                                                                                             
GreatSQL社区 前天 13:45
看到您使用的是 GreatDB 数据库。GreatDB 作为商业版数据库产品,配套提供专业的技术支持及 7×24 小时运维服务。建议您直接联系对应的运维支持同学或提交工单,由技术支持人员进入实际运行环境进行排查。这样可以第一时间获取完整日志、系统权限信息及相关配置,快速定位问题根因,相比仅通过论坛日志分析会更加高效和准确。


如果单从日志来看,目前无法直接判断是哪个目录权限不足。

原因是:

  1. 2026-04-11 00:53:17
  2. ready for connections
复制代码


说明实例已经完成:

* InnoDB初始化
* Redo/Undo打开
* 主从复制启动
* 服务监听

数据库已经正常运行。

而报错:

  1. 2026-04-11 03:29:56
  2. [ERROR] [MY-012592] [InnoDB] Operating system error number 13 in a file operation.
  3. [ERROR] [MY-012595] [InnoDB] The error means mysqld does not have the access rights to the directory.
复制代码


是在实例启动约2个半小时后出现的。

因此基本可以排除:

* datadir权限问题
* ibdata1权限问题
* redo日志目录权限问题
* undo表空间权限问题

因为这些问题会导致实例启动失败,而不会等运行2个多小时后才报错。

MY-012592对应Linux errno=13,即 Permission denied。通常还会伴随类似日志:


  1. Cannot open file xxx
  2. File operation call: open/create/delete
  3. File name xxx
复制代码


从而明确指出具体文件。

但当前日志只有两行错误,没有出现:

  1. File name ...
  2. File operation call ...
复制代码


所以无法仅根据现有日志确定是哪个目录或文件。

建议进一步提供:

1. 03:29:56 前后至少50行完整错误日志;
2. 是否开启了主从复制(日志显示存在Replication);
3. 错误发生时是否执行过DDL、OPTIMIZE TABLE、ALTER TABLE、导入导出等操作;
4. 检查错误时间点附近是否有权限变更、定时任务、备份脚本、清理脚本执行。

建议重点排查:

* relay-log目录
* binlog目录
* 某个独立表空间(.ibd)
* 临时文件目录(tmpdir)
* SELinux/Audit日志
yejr 前天 16:36
其他客户有遇到过类似情况,应该是麒麟系统特有的 KYSEC 安全机制限制第三方程序启动,临时关了就正常启动了,你也可以试试看。
reddey 昨天 15:02
yejr 发表于 2026-6-4 16:36
其他客户有遇到过类似情况,应该是麒麟系统特有的 KYSEC 安全机制限制第三方程序启动,临时关了就正常启动 ...

也就是这个和操作系统有关了
丁一

1

主题

0

博客

3

贡献

新手上路

Rank: 1

积分
5

合作电话:010-64087828

社区邮箱:greatsql@greatdb.com

社区公众号
社区小助手
QQ群
GMT+8, 2026-6-6 03:00 , Processed in 0.024888 second(s), 13 queries , Redis On.
快速回复 返回顶部 返回列表