mysql errno 13_MySQL启动故障处理一例（errno 13）

最新推荐文章于 2023-10-20 14:58:28 发布
最新推荐文章于 2023-10-20 14:58:28 发布
阅读量447 收藏
点赞数
文章标签： mysql errno 13
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_42347422/article/details/113260086
版权

[root@bak mysql]# cat /data/mysql/mysql_3306/data/error.log

141017  9:24:53 [Warning] Using unique option prefix myisam_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

141017  9:24:53 [Note] Plugin 'FEDERATED' is disabled.

/usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist

141017  9:24:53 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

141017  9:24:53 InnoDB: The InnoDB memory heap is disabled

141017  9:24:53 InnoDB: Mutexes and rw_locks use InnoDB's own implementation

141017  9:24:53 InnoDB: Compressed tables use zlib 1.2.3

141017  9:24:53 InnoDB: Using Linux native AIO

141017  9:24:53 InnoDB: Initializing buffer pool, size = 128.0M

141017  9:24:53 InnoDB: Completed initialization of buffer pool

InnoDB: The first specified data file ./ibdata1 did not exist:

InnoDB: a new database to be created!

141017  9:24:53  InnoDB: Setting file ./ibdata1 size to 100 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

141017  9:24:58  InnoDB: Log file ./ib_logfile0 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile0 size to 100 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

141017  9:25:03  InnoDB: Log file ./ib_logfile1 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile1 size to 100 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

141017  9:25:08  InnoDB: Log file ./ib_logfile2 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile2 size to 100 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

InnoDB: Doublewrite buffer not found: creating new

InnoDB: Doublewrite buffer created

InnoDB: 127 rollback segment(s) active.

InnoDB: Creating foreign key constraint system tables

InnoDB: Foreign key constraint system tables created

141017  9:25:13  InnoDB: Waiting for the background threads to start

141017  9:25:14 InnoDB: 5.5.39 started; log sequence number 0

141017  9:25:14 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

141017  9:25:14 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

141017  9:25:14 [Note] Server socket created on IP: '0.0.0.0'.

141017  9:25:14 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

141017  9:26:15 [Warning] Using unique option prefix myisam_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

141017  9:26:15 [Note] Plugin 'FEDERATED' is disabled.

/usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist

141017  9:26:15 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

141017  9:26:15 InnoDB: The InnoDB memory heap is disabled

141017  9:26:15 InnoDB: Mutexes and rw_locks use InnoDB's own implementation

141017  9:26:15 InnoDB: Compressed tables use zlib 1.2.3

141017  9:26:15 InnoDB: Using Linux native AIO

141017  9:26:15 InnoDB: Initializing buffer pool, size = 128.0M

141017  9:26:15 InnoDB: Completed initialization of buffer pool

141017  9:26:15 InnoDB: highest supported file format is Barracuda.

InnoDB: Log scan progressed past the checkpoint lsn 48941

141017  9:26:15  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

InnoDB: Doing recovery: scanned up to log sequence number 1595668

141017  9:26:15  InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progress in percents: 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

InnoDB: Apply batch completed

141017  9:26:15  InnoDB: Waiting for the background threads to start

141017  9:26:16 InnoDB: 5.5.39 started; log sequence number 1595668

141017  9:26:16 [Note] Recovering after a crash using /data/mysql/mysql_3306/logs/mysql-bin

141017  9:26:16 [Note] Starting crash recovery...

141017  9:26:16 [Note] Crash recovery finished.

141017  9:26:17 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

141017  9:26:17 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

141017  9:26:17 [Note] Server socket created on IP: '0.0.0.0'.

141017  9:26:17 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

141017  9:28:34 [Warning] Using unique option prefix myisam_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

141017  9:28:34 [Note] Plugin 'FEDERATED' is disabled.

/usr/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)

141017  9:28:34 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

141017  9:28:34 InnoDB: The InnoDB memory heap is disabled

141017  9:28:34 InnoDB: Mutexes and rw_locks use InnoDB's own implementation

141017  9:28:34 InnoDB: Compressed tables use zlib 1.2.3

141017  9:28:34 InnoDB: Using Linux native AIO

141017  9:28:34 InnoDB: Initializing buffer pool, size = 128.0M

141017  9:28:34 InnoDB: Completed initialization of buffer pool

141017  9:28:34 InnoDB: highest supported file format is Barracuda.

InnoDB: The log sequence number in ibdata files does not match

InnoDB: the log sequence number in the ib_logfiles!

141017  9:28:34  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

141017  9:28:34  InnoDB: Waiting for the background threads to start

141017  9:28:35 InnoDB: 5.5.39 started; log sequence number 1595668

/usr/libexec/mysqld: File '/data/mysql/mysql_3306/logs/mysql-bin.000004' not found (Errcode: 13)

141017  9:28:35 [ERROR] Failed to open log (file '/data/mysql/mysql_3306/logs/mysql-bin.000004', errno 13)

141017  9:28:35 [ERROR] Could not open log file

141017  9:28:35 [ERROR] Can't init tc log

141017  9:28:35 [ERROR] Aborting

141017  9:28:35  InnoDB: Starting shutdown...

141017  9:28:36  InnoDB: Shutdown completed; log sequence number 1595668

141017  9:28:36 [Note] /usr/libexec/mysqld: Shutdown complete

141017  9:30:32 [Warning] Using unique option prefix myisam_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

141017  9:30:32 [Note] Plugin 'FEDERATED' is disabled.

/usr/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)

141017  9:30:32 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

141017  9:30:32 InnoDB: The InnoDB memory heap is disabled

141017  9:30:32 InnoDB: Mutexes and rw_locks use InnoDB's own implementation

141017  9:30:32 InnoDB: Compressed tables use zlib 1.2.3

141017  9:30:32 InnoDB: Using Linux native AIO

141017  9:30:32 InnoDB: Initializing buffer pool, size = 128.0M

141017  9:30:32 InnoDB: Completed initialization of buffer pool

141017  9:30:32 InnoDB: highest supported file format is Barracuda.

141017  9:30:32  InnoDB: Waiting for the background threads to start

141017  9:30:33 InnoDB: 5.5.39 started; log sequence number 1595668

/usr/libexec/mysqld: File '/data/mysql/mysql_3306/logs/mysql-bin.000004' not found (Errcode: 13)

141017  9:30:33 [ERROR] Failed to open log (file '/data/mysql/mysql_3306/logs/mysql-bin.000004', errno 13)

141017  9:30:33 [ERROR] Could not open log file

141017  9:30:33 [ERROR] Can't init tc log

141017  9:30:33 [ERROR] Aborting

141017  9:30:33  InnoDB: Starting shutdown...

141017  9:30:34  InnoDB: Shutdown completed; log sequence number 1595668

141017  9:30:34 [Note] /usr/libexec/mysqld: Shutdown complete

姜L
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Mysql主从同步Last_IO_Errno:1236错误解决方法
01-21
Mysql主从同步的Last_IO_Errno:1236错误是什么原因呢，我们要如何来解决这个问题呢?下面和小编一起来看看关于此问题的记录与解决办法。 [removed]ec(2);[removed] 从服务器错误代码： Last_IO_Errno: 1236 Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Slave can not handle replication events with the checksum that master is configur
解析MySQL创建外键关联错误 – errno:150
01-19
当你试图在mysql中创建一个外键的时候，这个出错会经常发生，这是非常令人沮丧的。像这种不能创建一个.frm 文件的报错好像暗示着操作系统的文件的权限错误或者其它原因，但实际上，这些都不是的，事实上，这个mysql报错已经被报告是一个mysql本身的bug并出现在mysql 开发者列表当中很多年了，然而这似乎又是一种误导。 在很多实例中，这种错误的发生都是因为mysql一直以来都不能很好的支持的关系的问题， 更不幸的是它也并没有指明到底是哪一个问题会导致上面那种错误，下面我把导致这个可怕 的150错误的常见原因列出来了，并且我以可能性的大小作了排序 已知的原因： 1， 两个字段的类型或者
MySQL复制出错 Last_SQL_Errno:1146的解决方法
09-10
主要介绍了MySQL复制出错 Last_SQL_Errno:1146的解决方法,需要的朋友可以参考下
mysql errno 13,mysql错误：错误1018（HY000）：无法读取dir的'。 （errno：13）
weixin_35440082的博客
01-27 197
when i try to view the databases in mysql i get this error:ERROR 1018 (HY000): Can't read dir of '.' (errno: 13)And that stops my app from displaying...My django debugger says:(2002, "Can't connect to...
[Error 10048] error while attempting to bind on address (‘127.0.0.1‘, 8000): 通常每个套接字地址(协议/网络地址/端口)..
qq_42926549的博客
06-29 4368
[Error 10048] error while attempting to bind on address ('127.0.0.1', 8000): 通常每个套接字地址(协议/网络地址/端口)只允许使用一次。
WARNING:tensorflow: is deprecated and will be removed in a future version的解决方案
阅读修身
04-07 3万+
1问题描述 一瞬间出现超多的WARNING WARNING:tensorflow:From e:\matlab\CNN-classification\LSTM\train_test.py:56: MultiRNNCell.__init__ (from tensorflow.python.ops.rnn_cell_impl) is deprecated and will be removed in a future version. Instructions for updating: This cla.
mysql errno 13_解决mysql“ERROR 13 (HY000): Can't get stat of '/root/aaa' (Errcode: 13)”
weixin_32533957的博客
01-27 1886
今天在导入mysql数据的时候，出现下面的错误：mysql> load data infile '/root/aaa' into table test fields terminated by ',' lines terminated by '\n';mysql> ERROR 13 (HY000): Can't get stat of '/root/aaa' (Errcode: 13)...
Mac 下mysql启动报错[Errno 13] Permission denied
zhengwenhaodezw的博客
01-01 2346
MySQL 启动errno 13 permission denied 问题
遇到：PermissionError: [Errno 13] Permission denied: ‘XXXX 错误应该如何解决
热门推荐
牛肉胡辣汤
08-08 5万+
在上面的例子中，我们尝试打开一个名为 "file.txt" 的文件，并尝试写入内容。如果我们没有足够的权限来访问或修改该文件，就会抛出 "PermissionError: [Errno 13] Permission denied" 错误。为了处理这个错误，我们使用了一个 try-except 块来捕获异常，并在 except 块中打印了相应的错误信息。遇到 "PermissionError: [Errno 13] Permission denied" 错误通常是由于没有足够的权限来执行某个操作导致的。
mysqld: File ‘./binlog.index‘ not found (OS errno 13 - Permission denied) 问题解决
最新发布
破晓的成长之路
10-20 1991
Centos7 安装Mysql 8后启动时遇到的问题，看了好几个博客方案无效，搞了半小时才找到正解，在此次进行记录。
mysql安装error13_mysqld：无法创建/写入文件(错误代码：13)
weixin_33564130的博客
01-19 2985
我最近在我的archlinux盒子上安装了mariadb,并希望用不同的数据和tmp目录运行mysqld[mysqld]user = mysqlport = 3306datadir = tmpdir = /tmp运行mysqld时,我收到以下错误消息：InnoDB: The InnoDB memory heap is disabledInnoDB: M...
mysql不能启动报error2013错误的多种解决思路
huofuhuo8469的博客
10-22 6954
方案1.在mysql配置文件[myslqd]下面添加一行设置skip-name-resolve.需要重启mysql服务. 方案2.在hosts文件内添加:　ip与主机名的映射关系，如: 127.0.0.1 localhost.　这种方式不用重启mysql服务. ---------------------------三个层面上解决这个问题： 1. 代码层面，你需要在自己的PHP数据库连接处增加大致...
mysql创建数据库报错(errno13)
xinsuwang的博客
03-15 2137
在centos上的数据库中新建数据库时发现无法创建并报错（errno 13 ） 查了很多资料 错误代码13是权限问题 大部分人建议查看数据库数据文件的权限 部分人如下 drwxr-xr-x. 7 root root 181 3月  15 10:51 mysql 这种情况的可以使用命令 chown -R mysql:mysql mysql 解决 我的数据库文件已经是mysql可操作了 如...
mysql error 13_MySQL: ERROR13(HY000):Can't get stat of
weixin_39722921的博客
01-18 1175
在mysql中load data数据mysql> load data infile '/home/a.txt' into table table_a;ERROR 13 (HY000): Can't get stat of '/home/a.txt' (Errcode: 13)我们用perror命令打印出具体错误信息>perror 13OS error code 13: Permis...
MySQL在windows上导入数据提示错误(Errcode: 13 - Permission denied)
weixin_44832383的博客
07-31 1043
编辑C:\ProgramData\MySQL\MySQL Server ***\my.ini，把 secure-file-priv=“C:/ProgramData/MySQL/MySQL Server 8.0/Uploads” 修改为 secure-file-priv=“”
MySQL数据库——MySQL错误日志（Error Log）详解
Itmastergo的博客
05-25 3260
错误日志（Error Log）是 MySQL 中最常用的一种日志，主要记录 MySQL 服务器启动和停止过程中的信息、服务器在运行过程中发生的故障和异常情况等。
Mysql 1006 不能创建表 errno:13 解决方法
xzlAwin的博客
07-10 1615
Mysql 1006 不能创建表 errno:13解决方法 问题描述：本地root创建数据库提示异常信息 ERROR 1006 (HY000): Can't create database 'xxx' (errno: 13) 分析原因：因为root为最高权限，所以不是表权限不足问题，这个问题通常是由于目录没有权限造成的。 解决方案： chown -R mysql:mysql /var/lib/mysql chmod -R 770 /var/lib/mysql 建议mysql整个目录权限，修改为 ch
mysql 8 启动报错 解决过程
chenfei2341的专栏
07-03 687
官方说明：https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html。原文链接：https://blog.csdn.net/lsqtzj/article/details/113786543。mysqladmin -u root password 123456 //恢复密码。*不知道位置可以在my.cnf文件中找到datadir后面的就是数据文件的位置。还是无法启动将上面的1改成2/3/4/5/6 直到能启动为止。
MySQL常见错误之Can‘t read dir of ‘./zabbix/‘ (errno: 13)
xu710263124的博客
05-28 1227
当我们在启动mysql时，无法打开某个数据表，出现如下报错： ERROR 1018 (HY000): Can’t read dir of ‘./zabbix/’ (errno: 13) 遇到这种情况下，我们需要查看自己的mysql配置文件 /etc/my.cnf ，查看其中的路径文件所对应的所属用户，或者读写权限。 cat /etc/my.cnf 经过 对该目录下的一系列查看，发现问题 报错原因：【权限问题】zabbix目录的所属权限为root，导致数据库中的zabbix表无法打开； 解决方案：1
mysql_stmt_free_result mysql_errno mysql_close mysql_init mysql_options mysql_real_connect mysql_autocommit mysql_set_character_set mysql_rollback mysql_stmt_close mysql_stmt_errno mysql_stmt_free_result mysql_stmt_bind_param mysql_stmt_bind_result mysql_stmt_execute mysql_stmt_fetch
05-31
这函数都与 MySQL 数据库的连接、查询和结果处理有关。下面是每个函数的简要说明： - mysql_stmt_free_result：释放与语句句柄相关的查询结果。 - mysql_errno：获取最后一次 MySQL 操作的错误码。 - mysql_close：关闭 MySQL 连接。 - mysql_init：初始化 MySQL 连接句柄。 - mysql_options：设置 MySQL 连接选项。 - mysql_real_connect：建立 MySQL 数据库连接。 - mysql_autocommit：设置 MySQL 连接是否自动提交事务。 - mysql_set_character_set：设置 MySQL 连接字符集。 - mysql_rollback：回滚 MySQL 事务。 - mysql_stmt_close：关闭 MySQL 语句句柄。 - mysql_stmt_errno：获取最后一次 MySQL 语句操作的错误码。 - mysql_stmt_bind_param：将变量绑定到 MySQL 语句的参数上。 - mysql_stmt_bind_result：将变量绑定到 MySQL 语句的结果上。 - mysql_stmt_execute：执行 MySQL 语句。 - mysql_stmt_fetch：获取 MySQL 语句的下一行结果。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值