错误日志:
##运维——日志——错误日志
错误日志是MySQL中最重要的日志之一,它记录了当mysqld启动和停止时,以及服务器在运行过程中发生任何严重错误的相关信息。当数据库出现任何故障导致无法正常使用时,建议首先查看此日志。
该日志是默认开启的,默认存放目录/var/log/,默认的日志文件名为mysqld.log。查看日志位置:
show variables like '%log_error%';
———————————————————————————————————————————虚拟环境:
二进制日志:
##运维——日志——二进制日志
介绍
二进制日志(BINLOG)记录了所有DDL(数据定义语言)语句和DML(数据操纵语言)语句,但不包括数据查询(SELECT、SHOW)
语句。
作用:1、灾难时的数据恢复;2、MySQL的主从复制。在MySQL8版本中,默认二进制日志是开启着的,涉及到的参数如下:
show variables like '%log_bin%';
日志格式:
MySQL服务器中提供了多种格式来记录二进制日志,具体格式及特点如下:
STATEMENT:基于SQL语句的日志记录,记录的是SQL语句,对数据进行修改的SQL都会记录在日志文件中
ROW:基于行的日志记录,记录的是每一行的数据变更。(默认)
MIXED:混合了STATEMENT和ROW两种格式,默认采用STATEMENT,在某些特殊情况下会自动切换为ROW进行记录
show variables like '%binlog_format%';
日志查看:
由于日志是以二进制方式存储的,不能直接读取,需要通过二进制日志查询工具mysqlbinlog来查看,具体语法:
mysqlbinlog [参数选项] logfilename
参数选项:
-d 指定数据库名称,只列出指定的数据库相关操作
-o 忽略掉同之中的前n行命令
-v 将行事件(数据变更)重构为SQL语句
-vv 将行事件(数据变更)重构为SQL语句,并输出注释信息
日志删除
对于比较繁忙的业务系统,每天生成的binlog数据巨大,如果长时间不清除,将会占用大量磁盘空间。可以通过以下几种方式清理日志:
reset master 删除全部binlog日志,删除之后,日志编号,将从binlog.000001重新开始
purge master logs to 'binlog.******' 删除******编号之前的所有日志
purge master logs before 'yyyy-mm-dd hh24:mi:ss' 删除日志为"yyyy-mm-dd hh24:mi:ss"之前产生的所有日志
也可以在mysql的配置二进制日志的过期时间,设置之后,二进制日志过期会自动删除
show variables like '%binlog_expire_logs_secords%';
———————————————————————————————————————————虚拟环境:
在/etc/my.cnf配置文件中添加binlog_format=STATEMENT,将ROW改为STATEMENT,然后重启MySQL
使用mysqlbinlog -v binlog.000021查看
———————————————————————————————————————————虚拟机中:
mysql> use user;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> show tables;
+--------------------+
| Tables_in_user |
+--------------------+
| a |
| course |
| employee |
| stu_v_1 |
| stu_v_2 |
| stu_v_3 |
| stu_v_4 |
| stu_v_5 |
| stu_v_6 |
| stu_v_count |
| student |
| student_course |
| tb_stu_course_view |
| tb_user |
| tb_user_pro |
| tb_user_view |
| user_logs |
+--------------------+
17 rows in set (0.00 sec)
mysql> select * from course;
+----+--------+
| id | name |
+----+--------+
| 4 | Cloud |
| 1 | JavaEE |
| 3 | MySQL |
| 2 | Spring |
+----+--------+
4 rows in set (0.01 sec)
mysql> select * from student;
+----+-----------+------------+
| id | name | no |
+----+-----------+------------+
| 1 | 幻读 | 2000100101 |
| 2 | jkl | 2000100102 |
| 3 | 斯科拉 | 2000100103 |
| 4 | 三剑客 | 2000100104 |
| 5 | nlk | 2000100145 |
| 6 | 量子 | 2000100106 |
| 7 | sjk | 2000100122 |
| 8 | 大润发 | 2000100122 |
| 9 | dh | 2000100128 |
| 10 | jslk | 2000100130 |
+----+-----------+------------+
10 rows in set (0.00 sec)
mysql> create table score(id int primary key auto_increment,name varchar(10) comment '姓名',math int comment '数学',english int comment '英语',chinese int comment '语文')comment '成绩表';
Query OK, 0 rows affected (0.02 sec)
mysql> insert into score values(1,'Tom',65,88,100);
Query OK, 1 row affected (0.00 sec)
mysql> insert into score values(2,'Rose',99,66,90);
Query OK, 1 row affected (0.00 sec)
mysql> insert into score values(3,'Jack',89,98,100);
Query OK, 1 row affected (0.00 sec)
mysql> select * from score;
+----+------+------+---------+---------+
| id | name | math | english | chinese |
+----+------+------+---------+---------+
| 1 | Tom | 65 | 88 | 100 |
| 2 | Rose | 99 | 66 | 90 |
| 3 | Jack | 89 | 98 | 100 |
+----+------+------+---------+---------+
3 rows in set (0.00 sec)
mysql> update score set math=math+1;
Query OK, 3 rows affected (0.00 sec)
Rows matched: 3 Changed: 3 Warnings: 0
mysql> update score set math=math+1;
ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
Connection id: 8
Current database: user
Query OK, 3 rows affected (0.09 sec)
Rows matched: 3 Changed: 3 Warnings: 0
mysql> update score set math=math-1 where id=2;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
mysql> select * from score;
+----+------+------+---------+---------+
| id | name | math | english | chinese |
+----+------+------+---------+---------+
| 1 | Tom | 67 | 88 | 100 |
| 2 | Rose | 100 | 66 | 90 |
| 3 | Jack | 91 | 98 | 100 |
+----+------+------+---------+---------+
3 rows in set (0.00 sec)
mysql> purge master logs to 'binlog.000002';
Query OK, 0 rows affected (0.00 sec)
mysql> reset master
-> ;
Query OK, 0 rows affected (0.02 sec)
mysql> show variables like 'binlog_expire%';
+-------------------------------+---------+
| Variable_name | Value |
+-------------------------------+---------+
| binlog_expire_logs_auto_purge | ON |
| binlog_expire_logs_seconds | 2592000 |
+-------------------------------+---------+
2 rows in set (0.02 sec)
mysql>