Shulou(Shulou.com)06/03 Report--

Problem 1:1 windows server, installed Zabbix Agent, and then repeatedly alarm

High ICMP ping loss

Zabbix agent on xxx is unreachable for 5 minutes

Solution: change it to active detection

Open: C:\ Program Files\ Zabbix Agent\ zabbix_agentd.conf

Activate ServerActive, fill in the Zabbix monitoring server, and let the monitored host submit information actively.

For this active monitoring, the port should be 10051, ServerActive=zabbix_server_ip:10051

You can check log:sudo tail-f / var/log/zabbix-agent/zabbix_agentd.log with this command

If there is a connectivity problem, log prompts an error message as follows:

123705:20191106:074310.500 agent # 0 started [main process]

123706:20191106:074310.500 agent # 1 started [collector]

123710:20191106:074310.502 agent # 5 started [active checks # 1]

123707:20191106:074310.502 agent # 2 started [listener # 1]

123709:20191106:074310.502 agent # 4 started [listener # 3]

123708:20191106:074310.503 agent # 3 started [listener # 2]

123710 cannot connect to 20191106 active check configuration update from [54.222.165.90 cannot connect to 10050] Interrupted system call [54.222.165.90]: 10050]

Port 10050 here is incorrect and needs to be modified to 10051. At the same time, the network on the zabbix server side needs to open and allow client agent IP to access port 10051.

After the setting is successful, the normal log content is as follows:

140859:20191106:082004.516 using configuration file: / etc/zabbix/zabbix_agentd.conf

140859:20191106:082004.516 agent # 0 started [main process]

140860:20191106:082004.516 agent # 1 started [collector]

140863:20191106:082004.517 agent # 4 started [listener # 3]

140861:20191106:082004.518 agent # 2 started [listener # 1]

140862:20191106:082004.518 agent # 3 started [listener # 2]

140864:20191106:082004.518 agent # 5 started [active checks # 1]

There is also a way to change the trigger from 5 minutes to a longer time, such as 10 minutes

Question 2: prompt get value from agent failed: cannot connect to IP:10050, interrupted system call on the page side of the Zabbix server

Solution 1: the client opens port 10050 access (firewall side)

How to detect connectivity from the server side, operate on the Zabbix server side as follows:

Sudo apt install zabbix-get

Then enter the command: zabbix_get-s client_ip-p 10050-k "system.uptime"

If you pass, you will return a string of numbers.

Solution 2: the client initiates active transmission to the server

Vim / etc/zabbix/zabbix_agentd.conf

Windows:C:\ Program Files\ Zabbix Agent\ zabbix_agentd.conf

Fill in the server IP in the following line

ServerActive=zabbix_server_ip:10050

Then restart agent:sudo service zabbix-agent restart

Problem 3:Too many processes on host

The Linux Template of Zabbix defaults to 300 processes, and an alarm will be given if the process is exceeded.

Solution: disable or increase the default 300 threshold

Question 4: firewall is turned on but still cannot connect to Zabbix Agent

From the Zabbix server: zabbix_get-s IP-p 10050-k "system.uptime"

The following error is prompted:

Zabbix_get [21359]: Check access restrictions in Zabbix agent configuration

Then Zabbix Server web page side, after adding host, display red, the mouse click prompt message: Received empty response from Zabbix Agent at [IP]. Assuming that agent dropped connection because of access permissions.

On the Agent side, check log: there is no error.

Try to check the firewall and zabbix_agent.conf file configuration. There's nothing wrong with IP.

Later try to uninstall zabbix agent and then reinstall:

Sudo apt-get remove zabbix-agent

Sudo apt-get remove-auto-remove zabbix-agent

Sudo apt-get purge zabbix-agent

Installation

Sudo apt-get install zabbix-agent

This process actually installed the new version of zabbix agent. It turned out that I installed the old version.

Then reconfigure the conf file and restart the zabbix agent service, then open the log file, and the location of the new log file has been changed / var/log/zabbix/, to / var/log/zabbix_agent/, finally found the error

It is only then that I understand that the firewall and the server are implemented through port forwarding, and the server IP of zabbix_agent.conf needs to be modified to this 192.168.150.6, which has always been set up as a public network IP.

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.