Zabbix with Fpmmm (MPM) data will not be able to solve the problem

Our environment with Zabbix MPM to monitor MySQL, but recently the official website has not called MPM, but called fpmmm, for the reasons:

fpmmm is the successor of mpm. mpm was renamed to fpmmm because of the naming conflict with the Apache Multi-Processing Modules (MPM).



Well, that's the official act, we can ignore it, so we downloaded the latest fpmmm (fpmmm-0.10.5.tar.gz) Monitoring module

All according to Http://www.fromdual.com/fpmmm-installation-guide on the instructions to install on it.

Import template everything is fine, but you can't find the data:

Sending data with Zabbix_sender is not going to be sent.

Look at the log (fpmmm module): Less/tmp/fpmmm/fpmmm.log (found like a large number of duplicate logs) 46819:2016-04-21 10:22:02.630-warn:zabbixserver=122.54.133. zabbixserverport=10051, hostname=52.29.mysql.330646819:2016-04-21 10:22:02.630-warn:connection to Zabbix serv ER failed (rc=1800)!46819:2016-04-21 10:22:02.648-err:failed to execute (rc=1107/ret=1).

It appears that the remote Zabbixserver connection failed.

When you use Telnet to join the words prompt: [[email protected]~]$ telnet 122.54.133.40 10051Trying 122.54.133.40...telnet:connect to address 122.54.133.40:No route to host

It should be a firewall problem:

Turn on the firewall: Ensure that the sever port has 10051 ports:-A input-s 122.54.133.40-m state--state new-m tcp-p TCP--dport 10050:10051-j accept-a Inpu T-S 122.54.133.40-m State--state new-m udp-p UDP--dport 10050:10051-j ACCEPT

Connect again:

[[email protected]tpl]# telnet 122.54.133.40 10051Trying 122.54.133.40...telnet:connect to address 122.54.133.40:Connection refusedStrangely, the server side has opened Port 10051, and then scan the port with the following command: [[email protected]chenzejin]# nmap-p10051 122.54.133.40 starting Nmap 5.51 (http://nmap.org) at 2016-04-21 10:15 cstnmap Scan Report for 122.54.133.40Host is up (0.0021s latency). PORT State Service10051/tcp closedUnknown Nmap done:1 IP address (1 host up) scanned in 0.14 seconds found to be closed status, so cannot connect.

Strange, the local test is good, now move to production environment test is not

So I looked at the 10051 ports on the Zabbix_server as follows:

[[email protected]zabbix]# NETSTAT-LNPT | grep 10051tcp 0 127.0.0.1:10051 0.0.0.0:* LISTEN 58116/zabbix_server

Compared to the local normal can listen to the environment, found a little bit like

[[email protected]zabbix]# NETSTAT-LNPT | grep 10051tcp 0 0 0.0.0.0: 10051 0.0.0.0:* LISTEN 58116/zabbix_server

So it should be the zabbix_server configuration problem. Then open the zabbix_server.conf configuration file, found the configuration as follows: # # option:listenip# List of comma delimited IP addresses that the trapper Shou LD Listen on.# trapper would listen on all network interfaces if this parameter is missing.## mandatory:no# Default: # listenip=0.0.0.0 listenip=127.0.0.1 I was in the local listenip=127.0.0.1 is commented out, and the production of this option was opened found this option, no wonder, so the server's IP is added, as follows: listenip=127.0.0.1,122.54.133.40

Restarting the Zabbix Server service

Then execute on the agent side: [[email protected]zabbix]# nmap-p10050 122.54.133.40 starting Nmap 5.51 (http://nmap.org) at 2016-04-21 10:43 cstnmap Scan report for 12 2.54.133.40Host is up (0.0021s latency). PORT State Service10050/tcp OpenUnknown Nmap done:1 IP address (1 host up) scanned in 0.15 seconds everything is OK, you can connect to the communication.  The data was also properly acquired. This solves the situation that Zabbix MPM can not get the data summary: The first step: see Log,log is always firsthand information The second step: firewall check, port check the third step: zabbix_server configuration Check 122.54.133.40 This IP is a fictitious IP, if it happens, Purely coincidental.

Zabbix with Fpmmm (MPM) data will not be able to solve the problem