I. environment

1.1 operating system

[ root@host-xxxsoft ]# lsb_ release -a
LSB Version: :base-4.0-amd64:base-4.0- noarch:core-4.0-amd64 :core-4.0- noarch:graphics-4.0-amd64 :graphics-4.0- noarch:printing-4.0-amd64 :printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.6 (Final)
Release: 6.6
Codename: Final
[ root@host-xxx soft]#

1.2 ZABBIX agent and server and webfront 2.4.6

[ wls81@host-xxxx sbin]$ ./zabbix_ agent –version
Zabbix agent v2.4.6 (revision 54796) (10 August 2015)
Compilation time: Nov 2 2015 21:29:13

1.3 at present, I have monitored 791 virtual machines

Two questions

Here’s to say: the problem is not that the red ZABBIX server is not running appears on the ZABBIX web page

2.1 Web

The page shows ZABBIX_ Server is not running

Zabbixserver also reported the following error

Less than 25% free in the trends cache

2.2 agent side log

28079:20161012:121243.196 active check configuration update from [192.168.176.25:10051] started to fail (cannot connect to [[192.168.176.25]:10051]: [4] Interrupted system call)
28079:20161012:122102.894 active check configuration update from [192.168.176.25:10051] is working again
28079:20161012:130105.458 active check configuration update from [192.168.176.25:10051] started to fail (ZBX_ TCP_ READ() failed: [4] Interrupted system call)
28079:20161012:153008.930 active check configuration update from [192.168.176.25:10051] is working again
28079:20161012:160811.493 active check configuration update from [192.168.176.25:10051] started to fail (ZBX_ TCP_ READ() failed: [4] Interrupted system call)
28079:20161013:104855.178 active check configuration update from [192.168.176.25:10051] is working again
28079:20161013:112258.667 active check configuration update from [192.168.176.25:10051] started to fail (cannot connect to [[192.168.176.25]:10051]: [4] Interrupted system call)

And from the agent side to the telent server side 10051

2.3 zabbix server

zabbix_ The server process is live, and port 10051 is also monitored.

Three solutions

Or read the diary

Finally, it is to locate this configuration, which is caused by the small default size.

### Option: TrendCacheSize
# Size of trend cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendCacheSize=4M
TrendCacheSize=400M