Mariadb

munin-run mysql_ 外掛返回數據但 munin 伺服器出現“錯誤退出”錯誤

  • January 27, 2018

我有一個帶有多個 Munin 節點的 Munin 伺服器，所有節點都使用 Ansible 進行配置，因此配置幾乎相同。系統是 Debian Jessie。

其中兩台伺服器的 mysql_* 圖存在但為空，而其他三台伺服器具有完整圖。

munin-run --debug mysql_commands在其中一台故障伺服器中執行會返回正確的輸出：

# munin-run --debug mysql_commands
# Processing plugin configuration from /etc/munin/plugin-conf.d/ansible.conf
# Processing plugin configuration from /etc/munin/plugin-conf.d/munin-node
# Setting /rgid/ruid/ to /119/0/
# Setting /egid/euid/ to /119 119/0/
# Setting up environment
# Environment mysqluser = debian-sys-maint
# Environment mysqlconnection = DBI:mysql:mysql;mysql_read_default_file=/etc/mysql/debian.cnf
# Environment mysqlopts = --defaults-file=/etc/mysql/debian.cnf
# About to run '/etc/munin/plugins/mysql_commands'
Com_delete.value 4546376
Com_insert.value 2804559
Com_insert_select.value 341479
Com_load.value 0
Com_replace.value 0
Com_replace_select.value 0
Com_select.value 236967004
Com_update.value 7069348
Com_update_multi.value 0

所以看起來 Munin 節點工作正常。

但是當我munin-cron在 munin 伺服器中執行時，外掛bad exit在獲取時返回：

# sudo -u munin munin-cron --host server.com --debug
...
2018/01/09 08:35:01 [DEBUG] for my mysql_commands (irqstats mysql_innodb_tnx diskstats apache_accesses smart_sda df ntp_offset vmstat fw_packets mysql_select_types netstat users mysql_qcache mysql_table_locks swap mysql_slow mysql_myisam_indexes if_err_eth0 apt hddtemp_smartctl ntp_kernel_err ntp_kernel_pll_freq mysql_innodb_rows mysql_innodb_bpool forks ntp_kernel_pll_off cpu load postfix_mailvolume postfix_mailqueue mysql_qcache_mem open_inodes processes http_loadtime open_files uptime mysql_commands mysql_innodb_semaphores apt_all mysql_innodb_io smart_sdb memory mysql_connections mysql_files_tables mysql_network_traffic df_inode mysql_sorts if_eth0 entropy proc_pri mysql_innodb_bpool_act apache_processes threads mysql_innodb_log mysql_innodb_insert_buf mysql_tmp_tables mysql_innodb_io_pend interrupts apache_volume)
2018/01/09 08:35:01 [DEBUG] Fetching service configuration for 'mysql_commands'
2018/01/09 08:35:01 [DEBUG] Writing to socket: "config mysql_commands
".
2018/01/09 08:35:02 [DEBUG] Reading from socket: "graph_vlabel Commands per ${graph_period}\ngraph_total Questions\ngraph_args --base 1000\ngraph_title Command Counters\ngraph_category mysql2\nCom_delete.type DERIVE\nCom_delete.label Delete\nCom_delete.draw STACK\nCom_delete.min 0\nCom_insert.draw STACK\nCom_insert.min 0\nCom_insert.type DERIVE\nCom_insert.label Insert\nCom_insert_select.type DERIVE\nCom_insert_select.label Insert select\nCom_insert_select.draw STACK\nCom_insert_select.min 0\nCom_load.label Load Data\nCom_load.type DERIVE\nCom_load.min 0\nCom_load.draw STACK\nCom_replace.type DERIVE\nCom_replace.label Replace\nCom_replace.draw STACK\nCom_replace.min 0\nCom_replace_select.draw STACK\nCom_replace_select.min 0\nCom_replace_select.type DERIVE\nCom_replace_select.label Replace select\nCom_select.type DERIVE\nCom_select.label Select\nCom_select.draw STACK\nCom_select.min 0\nCom_update.type DERIVE\nCom_update.label Update\nCom_update.draw STACK\nCom_update.min 0\nCom_update_multi.label Update multi\nCom_update_multi.type DERIVE\nCom_update_multi.min 0\nCom_update_multi.draw STACK".
2018/01/09 08:35:02 [DEBUG] config: 0.151266 sec for 'mysql_commands' on server.com/1.2.3.4/4949
2018/01/09 08:35:02 [DEBUG] Now parsing config output from plugin mysql_commands on server.com
2018/01/09 08:35:02 [DEBUG] update_rate 0 for mysql_commands on server.com/1.2.3.4:4949
2018/01/09 08:35:02 [DEBUG] No service data for mysql_commands, fetching it
2018/01/09 08:35:02 [DEBUG] Writing to socket: "fetch mysql_commands
".
2018/01/09 08:35:02 [DEBUG] data: 0.175058 sec for 'mysql_commands' on server.com/1.2.3.4/4949
2018/01/09 08:35:02 [DEBUG] Now parsing fetch output from plugin mysql_commands on server.com/1.2.3.4:4949
2018/01/09 08:35:02 [FETCH from mysql_commands] # Bad exit
...

兩台伺服器中的所有 mysql_* 外掛都會發生這種情況，但它們在其他三台伺服器中工作正常。其他 Munin 外掛在所有伺服器上都可以正常工作，因此一般配置似乎還可以。

mysql_* 外掛的配置：

[mysql*]
user root
env.mysqlopts --defaults-file=/etc/mysql/debian.cnf
env.mysqluser debian-sys-maint
env.mysqlconnection DBI:mysql:mysql;mysql_read_default_file=/etc/mysql/debian.cnf

執行時不會向 Munin 節點日誌 ( /var/log/munin/munin-node.log) 或 MySQL添加新條目sudo -u munin munin-cron。

Munin節點服務報告正常執行：

# systemctl status munin-node
● munin-node.service - Munin Node
  Loaded: loaded (/lib/systemd/system/munin-node.service; enabled)
  Active: active (running) since mié 2018-01-17 14:20:10 CET; 19s ago
    Docs: man:munin-node(1)
          http://munin.readthedocs.org/en/stable-2.0/reference/munin-node.html
 Process: 4515 ExecStart=/usr/sbin/munin-node $DAEMON_ARGS (code=exited, status=0/SUCCESS)
Main PID: 4541 (munin-node)
  CGroup: /system.slice/munin-node.service
          └─4541 /usr/bin/perl -wT /usr/sbin/munin-node

ene 17 14:20:10 example.com systemd[1]: Started Munin Node.
  • Munin 版本（節點和伺服器）：Debian 軟體包 2.0.25-1+deb8u3。
  • 數據庫：mariadb-server Debian 軟體包 10.0.26-0+deb8u1。

這些節點有什麼問題？或者我該如何調試問題？

真丟人。

兩個 munin-node 配置了相同的 IP，因此從未聯繫過一台伺服器，而另一台則被要求提供兩次統計資訊。該雙重請求使 mysql_ 外掛表現不佳。

此問題解釋了我檢測到但在此問題之後排隊等待解決的其他小問題（例如，奇怪的磁碟使用情況）。

從 master 調試外掛的有趣方式：

$ nc example.com 4949
# munin node at example.com
fetch mysql_commands
Com_delete.value 5481602
Com_insert.value 3468782
Com_insert_select.value 437696
Com_load.value 0
Com_replace.value 0
Com_replace_select.value 0
Com_select.value 295884041
Com_update.value 8498783
Com_update_multi.value 6
.

請參閱調試 Munin 外掛。

引用自：https://serverfault.com/questions/891315

相關問答

Mysql

如何查找沒有索引執行的連接？

  • May 7, 2022
檢視問答
Mysql

Docker 容器中 MariaDB 的超時錯誤

  • April 11, 2022
檢視問答
Munin

在 munin 圖中隱藏欄位

  • March 2, 2022
檢視問答
Postgresql

最可靠的 MariaDB 到 Postgres 轉儲方法

  • February 17, 2022
檢視問答
Ubuntu

無法將新的 munin 節點添加到現有的 munin 主節點

  • February 11, 2022
檢視問答
Backup

mariabackup 失敗並出現錯誤：cannot mkdir 2: /data/backups/mariadb/

  • February 8, 2022
檢視問答