一个非常奇怪的MYSQL 问题？

显示全部楼层 · 2014-6-12 16:34:36

本帖最后由 adriano_lee 于 2015-8-15 18:19 编辑
其实是两个问题
1前天不知道怎么回事两台住备机器上的service mysqld start都无法使用了都报mysqld: unrecognized service 前几个小时还可以用来着只能用 service mysql start 来代替
PS 有大牛知道是怎么回事吗？

2MYSQL 数据目录迁移的时候有没有碰过这种问题
datadir 改为新地址之后 /data/mysql 之后但是必须要保留老的、 /var/lib/mysql/logs/binlog/目录才能启动
如果不保留的话在mysql 的 errorlog 里有 [ERROR] Failed to open log (file '[img]file:///C:\Users\adriano.lee\AppData\Local\Temp\[LC3U)F{0XCAB)[email protected][/img]ar[img]file:///C:\Users\adriano.lee\AppData\Local\Temp\)A[Y)I~](ZC9Z[3Y)IDK7LK.gif[/img]b/mysql/logs/binlog/binlog.000003', errno 2)之类的报错出现
但是启动之后binlog 还是记到 /data/mysql/logs/binlog/下，不会记到老的/var/lib/mysql/logs/binlog/目录下

my.cnf 里我明明设置了
log-bin
=/data/mysql/logs/binlog/binlog
log_bin_index
=/data/mysql/logs/binlog/binlog_index

千问 · 2014-6-12 16:34:36

楼主的问题我也碰到过，，是因为你做迁移的时候没有切换日志,,执行 FLUSH LOGS;再迁移应该没问题
MySQL [(none)]> SHOW BINARY LOGS;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000001 | 580 |
| mysql-bin.000002 | 289 |
| mysql-bin.000003 | 143 |
| mysql-bin.000004 | 143 |
| mysql-bin.000005 |1967 |
| mysql-bin.000006 | 578 |
| mysql-bin.000007 | 143 |
| mysql-bin.000008 | 167 |
| mysql-bin.000009 | 120 |
+------------------+-----------+
9 rows in set (0.00 sec)
MySQL [(none)]>
MySQL [(none)]>
MySQL [(none)]> FLUSH LOGS;
Query OK, 0 rows affected (0.96 sec)
MySQL [(none)]> SHOW BINARY LOGS;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000001 | 580 |
| mysql-bin.000002 | 289 |
| mysql-bin.000003 | 143 |
| mysql-bin.000004 | 143 |
| mysql-bin.000005 |1967 |
| mysql-bin.000006 | 578 |
| mysql-bin.000007 | 143 |
| mysql-bin.000008 | 167 |
| mysql-bin.000009 | 167 |
| mysql-bin.000010 | 120 |
+------------------+-----------+
10 rows in set (0.00 sec)
MySQL [(none)]>

千问 · 2014-6-12 16:34:36

楼主的问题我也碰到过，，是因为你做迁移的时候没有切换日志,,执行 FLUSH LOGS;再迁移应该没问题
MySQL [(none)]> SHOW BINARY LOGS;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000001 | 580 |
| mysql-bin.000002 | 289 |
| mysql-bin.000003 | 143 |
| mysql-bin.000004 | 143 |
| mysql-bin.000005 |1967 |
| mysql-bin.000006 | 578 |
| mysql-bin.000007 | 143 |
| mysql-bin.000008 | 167 |
| mysql-bin.000009 | 120 |
+------------------+-----------+
9 rows in set (0.00 sec)
MySQL [(none)]>
MySQL [(none)]>
MySQL [(none)]> FLUSH LOGS;
Query OK, 0 rows affected (0.96 sec)
MySQL [(none)]> SHOW BINARY LOGS;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000001 | 580 |
| mysql-bin.000002 | 289 |
| mysql-bin.000003 | 143 |
| mysql-bin.000004 | 143 |
| mysql-bin.000005 |1967 |
| mysql-bin.000006 | 578 |
| mysql-bin.000007 | 143 |
| mysql-bin.000008 | 167 |
| mysql-bin.000009 | 167 |
| mysql-bin.000010 | 120 |
+------------------+-----------+
10 rows in set (0.00 sec)
MySQL [(none)]>

千问 · 2014-6-12 16:34:36

学习学习

一个非常奇怪的MYSQL 问题 ？

一个非常奇怪的MYSQL 问题？