Can't get correct value of proc.num

[suzuka46]

The problem that value of proc.num was frequent "0" occurred in my environment.
This actual process wasn't stopped.

The following was output in zabbix_agentd.log.

1598:20151004:233940.087 [24] Too many open files
1598:20151004:235340.144 [24] Too many open files
1598:20151004:235740.283 [24] Too many open files
1598:20151005:000840.014 [24] Too many open files

It was solved by a restart of zabbix agent.

It occurred in all servers installed zabbix-agent, and occurred 3-4 months later after these started.

My environment is following.

zabbix agent : 2.4.4
OS : ubuntu 14.04,
centos6.6,
Amazon Linux AMI release 2015.03

[Atsushi]

It does not reach the maximum number to open the file?
Please check kernel parameter on your environment.

[suzuka46]

Thank you for your reply.

I don't change the value of kernel parameter.
So, those values are default.

$ cat /proc/sys/fs/file-nr
2912 0 184512

$ cat /proc/`pgrep zabbix_agent | head -1`/limits | grep 'open files'
Max open files 1024 4096 files


These servers are just running zabbix-server or zabbix-proxy in light load environment.(Required server performance, new values per second 3.8)

When using proc.num, do I need to increase "maximum number to open the file"?

I think zabbix-agent has to release the file which opened.
If zabbix-agent doesn't release it, even if "maximum number to open the file" is increased, may they reach the upper limit for a while?

[Atsushi]

At first, you should solve the problem of open files is increased.

It opened remains of the process or does not exist a large number of files?
It really your Zabbix agent?
If you are using only standard features of the agent,
I think that it is not to be left to open the file.

If really necessary, please adjust the parameters of the kernel.

[suzuka46]

I found this issue. Do you think is this related?

https://support.zabbix.com/browse/ZBX-9251

[Atsushi]

Link of the issue, seems to have been fixed in 2.4.5.
Perhaps, 2.4.4 will have a that issue.

Error message is different, but you should use a newer version.

[suzuka46]

I will try it.

Thank you for your advice.