In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-05 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
This article mainly tells you what to do when history_uint damage causes frequent mysql restarts and finally leads to zabbix_server shutdown. You can check the relevant professional terms on the Internet or find some related books to supplement them. We will not dabble here. Let's go straight to the topic. I hope that history_uint damage causes frequent mysql restarts and finally leads to zabbix_server shutdown. This article can bring you some practical help.
Question: 13:15:47 InnoDB: Page checksum 2390903969, prior-to-4.0.14-form checksum 2524550738
InnoDB: stored checksum 2319722401, prior-to-4.0.14-form stored checksum 192332111
InnoDB: Page lsn 0 1902263731, low 4 bytes of lsn at page end 1900395394
InnoDB: Page number (if stored to page already) 16222
InnoDB: space id (if created with > = MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 0 462
InnoDB: (index "GEN_CLUST_INDEX" of table "zabbix". "history_uint")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 16222.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
Solution:
Add innodb_force_recovery=1 to my.cnf and restart mysql
[root@zabbix /] # / etc/init.d/mysqld restart
Create a new table with the same structure, and the engine is myisam
Mysql > use zabbix
Mysql > create table history_uint_new like history_uint
Mysql > alter table history_uint_new type=myisam
Import the original table data into the newly created table
Mysql > Insert into history_uint_new select * from history_uint
Mysql > exit
Comment out innodb_force_recovery=1 in my.cnf and restart mysql
[root@strongzabbix /] # / etc/init.d/mysqld restart
Change the new table engine to innodb
Mysql > use zabbix
Alter table history_uint_new type=innodb
Delete the original table
Mysql > Drop table history_uint
Change the name of the new table to the original table and refresh permissions, restart mysql
Mysql > rename table history_uint_new to history_uint
Mysql > flush privileges
Mysql > exit
[root@strongzabbix /] # / etc/init.d/mysqld restart
History_uint damage makes mysql restart frequently and finally causes zabbix_server to shut down. Let's stop here. If you want to know about other related issues, you can continue to follow our industry information. Our section will capture some industry news and professional knowledge to share with you every day.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.