Zabbix删除使用agent监控的主机出现SQL执行错误问题

Posted

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Zabbix删除使用agent监控的主机出现SQL执行错误问题相关的知识,希望对你有一定的参考价值。

今天在操作zabbix页面时,添加agent主机监控,发现添加错了,于是想删除再重新添加,却出现了以下问题,提示语句错误,如下图:
技术图片
技术图片

然后查看mysql数据库日志:
发现都是一大堆的innodb_table_stats表的问题
InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
技术图片

使用sqlyog连接数据库,打开mysql,找到innodb_table_stats,右击打开,提示错误
然后其他表也都顺便点了打开,找到红框有5张表一样提示错误问题。
技术图片

解决方法也简单,先删除表,删除对应的数据文件,然后重新建表,重启mysql即可。

1、 删除这5张表
DROP TABLE mysql.innodb_index_stats;
DROP TABLE mysql.innodb_table_stats;
DROP TABLE mysql.slave_master_info;
DROP TABLE mysql.slave_relay_log_info;
DROP TABLE mysql.slave_worker_info;

2、 删除对应的数据文件,一般是.ibd、.frm结尾的
例如我的mysql数据文件在这目录 /data/mysql/data/mysql
由于发现只有这5个前缀一样的,所以我直接执行删除
rm –rf innodb*
rm –rf slave
*

3、 重新建表,执行以下语句,如果到slave_master_info提示报错,先执行后面2条,再执行master的
CREATE TABLE innodb_index_stats (
database_name varchar(64) COLLATE utf8_bin NOT NULL,
table_name varchar(64) COLLATE utf8_bin NOT NULL,
index_name varchar(64) COLLATE utf8_bin NOT NULL,
last_update timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
stat_name varchar(64) COLLATE utf8_bin NOT NULL,
stat_value bigint(20) unsigned NOT NULL,
sample_size bigint(20) unsigned DEFAULT NULL,
stat_description varchar(1024) COLLATE utf8_bin NOT NULL,
PRIMARY KEY (database_name,table_name,index_name,stat_name)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;
CREATE TABLE innodb_table_stats (
database_name varchar(64) COLLATE utf8_bin NOT NULL,
table_name varchar(64) COLLATE utf8_bin NOT NULL,
last_update timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
n_rows bigint(20) unsigned NOT NULL,
clustered_index_size bigint(20) unsigned NOT NULL,
sum_of_other_index_sizes bigint(20) unsigned NOT NULL,
PRIMARY KEY (database_name,table_name)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;
CREATE TABLE slave_master_info (
Number_of_lines int(10) unsigned NOT NULL COMMENT ‘Number of lines in the file.‘,
Master_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT ‘The name of the master binary log currently being read from the master.‘,
Master_log_pos bigint(20) unsigned NOT NULL COMMENT ‘The master log position of the last read event.‘,
Host char(64) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT ‘‘ COMMENT ‘The host name of the master.‘,
User_name text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The user name used to connect to the master.‘,
User_password text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The password used to connect to the master.‘,
Port int(10) unsigned NOT NULL COMMENT ‘The network port used to connect to the master.‘,
Connect_retry int(10) unsigned NOT NULL COMMENT ‘The period (in seconds) that the slave will wait before trying to reconnect to the master.‘,
Enabled_ssl tinyint(1) NOT NULL COMMENT ‘Indicates whether the server supports SSL connections.‘,
Ssl_ca text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The file used for the Certificate Authority (CA) certificate.‘,
Ssl_capath text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The path to the Certificate Authority (CA) certificates.‘,
Ssl_cert text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The name of the SSL certificate file.‘,
Ssl_cipher text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The name of the cipher in use for the SSL connection.‘,
Ssl_key text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The name of the SSL key file.‘,
Ssl_verify_server_cert tinyint(1) NOT NULL COMMENT ‘Whether to verify the server certificate.‘,
Heartbeat float NOT NULL,
Bind text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘Displays which interface is employed when connecting to the MySQL server‘,
Ignored_server_ids text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The number of server IDs to be ignored, followed by the actual server IDs‘,
Uuid text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The master server uuid.‘,
Retry_count bigint(20) unsigned NOT NULL COMMENT ‘Number of reconnect attempts, to the master, before giving up.‘,
Ssl_crl text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The file used for the Certificate Revocation List (CRL)‘,
Ssl_crlpath text CHARACTER SET utf8 COLLATE utf8_bin COMMENT ‘The path used for Certificate Revocation List (CRL) files‘,
Enabled_auto_position tinyint(1) NOT NULL COMMENT ‘Indicates whether GTIDs will be used to retrieve events from the master.‘,
PRIMARY KEY (Host,Port)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT=‘Master Information‘;
CREATE TABLE slave_relay_log_info (
Number_of_lines int(10) unsigned NOT NULL COMMENT ‘Number of lines in the file or rows in the table. Used to version table definitions.‘,
Relay_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT ‘The name of the current relay log file.‘,
Relay_log_pos bigint(20) unsigned NOT NULL COMMENT ‘The relay log position of the last executed event.‘,
Master_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT ‘The name of the master binary log file from which the events in the relay log file were read.‘,
Master_log_pos bigint(20) unsigned NOT NULL COMMENT ‘The master log position of the last executed event.‘,
Sql_delay int(11) NOT NULL COMMENT ‘The number of seconds that the slave must lag behind the master.‘,
Number_of_workers int(10) unsigned NOT NULL,
Id int(10) unsigned NOT NULL COMMENT ‘Internal Id that uniquely identifies this record.‘,
PRIMARY KEY (Id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT=‘Relay Log Information‘;
CREATE TABLE slave_worker_info (
Id int(10) unsigned NOT NULL,
Relay_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
Relay_log_pos bigint(20) unsigned NOT NULL,
Master_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
Master_log_pos bigint(20) unsigned NOT NULL,
Checkpoint_relay_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
Checkpoint_relay_log_pos bigint(20) unsigned NOT NULL,
Checkpoint_master_log_name text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
Checkpoint_master_log_pos bigint(20) unsigned NOT NULL,
Checkpoint_seqno int(10) unsigned NOT NULL,
Checkpoint_group_size int(10) unsigned NOT NULL,
Checkpoint_group_bitmap blob NOT NULL,
PRIMARY KEY (Id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT=‘Worker Information‘;
然后重启mysql,查看mysql日志文件,发现正常了,回到zabbix页面,也可以正常删除了!
技术图片

结论:innodb_index_stats和innodb_table_stats 这2张表和innodb引擎关联的,如果mysql使用的是innodb引擎,这2张表出问题了,相应的SQL数据操作就会出问题。
参考文档:
https://www.linuxidc.com/Linux/2015-05/117521.htm

以上是关于Zabbix删除使用agent监控的主机出现SQL执行错误问题的主要内容,如果未能解决你的问题,请参考以下文章

Zabbix删除使用agent监控的主机出现SQL执行错误问题

Zabbix删除使用agent监控的主机出现SQL执行错误问题

Zabbix3.X---Zabbix _Agent主动模式的监控(Active)

Zabbix3.X-Zabbix _Agent主动模式的监控(Active)

运维在zabbix-server的web界面配置agent主机监控

青蛙学Linux—Zabbix Agent的主动模式和被动模式