CactiEZ The following error occurred using MySQL database: "[ERROR]/usr/sbin/mysqld"

Source: Internet
Author: User

In view CactiEZ found login not up, log on to find out the disk space is insufficient, finally found MySQL error log up to 10G, through the log discovery:

[[email protected] bin]# tail-f/var/log/mysqld.log2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:table './ Cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:table '. /cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:table ' ./cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:table  './cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:table './cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:tabl E './cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:tab Le './cacti/poller_item ' is marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:ta Ble './cacti/poller_item ' is Marked as crashed and should be repaired2018-03-02 15:54:17 31645 [ERROR]/usr/sbin/mysqld:table './cacti/poller_item ' I S marked as crashed and should be repaired

And the rapid growth, through the log found to be cacti this table error, after, troubleshooting repaired table structure, error ended, the following is the repair process.
is repaired by using the Mysqlcheck--auto-repair--databases cacti-u root-p.

[[email protected] bin]# mysqlcheck--auto-repair--databases cacti-u root-penter password:cacti.cdef                                       Okcacti.cdef_items okcacti.colors Okcacti.data_input Okcacti.data_input_data OKc Acti.data_input_fields okcacti.data_local Okcacti.data_templa                       Te Okcacti.data_template_data Okcacti.data_template_data_rra                                  OKCACTI.DATA_TEMPLATE_RRD okcacti.graph_local Okcacti.graph_template_input Okcacti.graph_template_input_defs Okcacti.graph_                        Templates Okcacti.graph_templates_gprint okcacti.graph_templates_graph OKcacti.graph_templates_item Okcacti.graph_tree Okcacti.graph_tre                                   E_items Okcacti.host Okcacti.host_graph                              Okcacti.host_snmp_cache Okcacti.host_snmp_query Okcacti.host_template Okcacti.host_template_graph Okcacti.host                            _template_snmp_query Okcacti.plugin_config Okcacti.plugin_db_changes                                Okcacti.plugin_hooks Okcacti.plugin_realms Okcacti.poller Okcacti.poller_command Okcacti    . poller_itemwarning:table is marked as CRASHEDWARNING:2 clients be using or haven ' t closed the Table properlyerror : Unexpected byte:0At Link:95080error:corruptcacti.poller_output Okcacti.poller_reindex Okcacti.poller_time Okcacti.rra OK CACTI.RRA_CF okcacti.settings Okcacti.settings_g                                   Raphs Okcacti.settings_tree Okcacti.snmp_query                         Okcacti.snmp_query_graph OKCACTI.SNMP_QUERY_GRAPH_RRD OKCACTI.SNMP_QUERY_GRAPH_RRD_SV OKCACTI.SNMP_QUERY_GRAPH_SV Okcacti.user_                              Auth okcacti.user_auth_perms Okcacti.user_auth_realm                                      Okcacti.user_log okcacti.version Okcacti.weathermAp_auth Okcacti.weathermap_data okcacti.weathermap_groups                          Okcacti.weathermap_maps okcacti.weathermap_settings Okrepairing Tablescacti.poller_iteminfo:Wrong bytesec:0-0-0 at 20912; Skippedinfo:found block with too small length at 87732; Skippedinfo:wrong bytesec:0-0-0 at 21096; Skippedinfo:wrong bytesec:57-48-57 at 21164; Skippedinfo:wrong bytesec:46-49-48 at 28040; Skippedinfo:found block that points outside data file at 92696info:wrong bytesec:0-0-0 at 20884; Skippedinfo:found block with too small length at 104116; Skippedinfo:wrong bytesec:0-0-0 at 27264; Skippedinfo:wrong bytesec:0-0-0 at 28208; Skippedinfo:wrong bytesec:0-0-0 at 27980; Skippedinfo:wrong block with wrong total length starting at 108504info:found block WITh too small length at 109952; Skippedinfo:wrong block with wrong total length starting at 112812info:wrong bytesec:0-0-0 at 21132; Skippedinfo:wrong block with wrong total length starting at 114852info:wrong bytesec:46-49-48 at 28012; Skippedinfo:found block with too small length at 117068; Skippedinfo:wrong block with wrong total length starting at 117292info:wrong bytesec:0-0-0 at 9320; Skippedinfo:wrong bytesec:49-46-49 at 28360; Skippedinfo:wrong block with wrong total length starting @ 120876info:wrong block with wrong total length sta Rting at 121468info:wrong bytesec:46-49-46 at 28304; Skippedinfo:wrong block with wrong total length starting @ 124488info:wrong block with wrong total length sta Rting at 125820warning:number of rows changed from 652 to 624status:ok

To view the log again:

[email protected] bin]# tail -f /var/log/mysqld.log2018-03-02 16:01:53 1824 [Note] InnoDB: Waiting for purge to start2018-03-02 16:01:53 1824 [Note] InnoDB: 5.6.37 started; log sequence number 14982631096442018-03-02 16:01:53 1824 [Note] Server hostname (bind-address): ‘*‘; port: 33062018-03-02 16:01:53 1824 [Note] IPv6 is available.2018-03-02 16:01:53 1824 [Note]   - ‘::‘ resolves to ‘::‘;2018-03-02 16:01:53 1824 [Note] Server socket created on IP: ‘::‘.2018-03-02 16:01:53 1824 [Note] Event Scheduler: Loaded 0 events2018-03-02 16:01:53 1824 [Note] /usr/sbin/mysqld: ready for connections.Version: ‘5.6.37‘  socket: ‘/var/lib/mysql/mysql.sock‘  port: 3306  MySQL Community Server (GPL)2018-03-02 16:01:54 1824 [Warning] IP address ‘172.20.66.26‘ could not be resolved: Name or service not known

The error has been resolved.

CactiEZ The following error occurred using MySQL database: "[ERROR]/usr/sbin/mysqld"

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.