Hi folks,
AFAICS Zabbix server/proxy/agent does a renice on the systems that support this feature. (Look for setpriority() hardwired deep inside the code.) This has several disadvantages:
- communication errors between proxy and server, e.g. "Cannot connect to [[<zabbix_server_ip>]:10051]: [4] Interrupted system call" (I got tons of these messages in my zabbix-proxy.log.)
- very slow GUI.
- the agents don't answer in time --> false alarms
- it is not configurable
For testing I have rebuilt 1.8.10 without HAVE_SYS_RESOURCE_SETPRIORITY and installed the new daemons on my hosts. The stability and speed improvement is remarkable. Esp. the GUI works like a charm. All the "interrupted system call" messages are gone.
I would suggest to make this renice configurable, if it is needed at all. It seems that it has been dropped for Zabbix2, anyway.
Many thanx
harri
AFAICS Zabbix server/proxy/agent does a renice on the systems that support this feature. (Look for setpriority() hardwired deep inside the code.) This has several disadvantages:
- communication errors between proxy and server, e.g. "Cannot connect to [[<zabbix_server_ip>]:10051]: [4] Interrupted system call" (I got tons of these messages in my zabbix-proxy.log.)
- very slow GUI.
- the agents don't answer in time --> false alarms
- it is not configurable
For testing I have rebuilt 1.8.10 without HAVE_SYS_RESOURCE_SETPRIORITY and installed the new daemons on my hosts. The stability and speed improvement is remarkable. Esp. the GUI works like a charm. All the "interrupted system call" messages are gone.
I would suggest to make this renice configurable, if it is needed at all. It seems that it has been dropped for Zabbix2, anyway.
Many thanx
harri
Comment