I've tried all kinds of things to resolve this with limited success
Therfore I'm now posting my issue here to get some new pointers as to where the problem is.
After an update of our system from 3.0 LTS to 4.0 LTS one Zabbix agent on a Windows box started to act out making hundreds of errors.
The setup is with a server <-> proxy <-> agent
Today I was out by the Windows PC and tried to get it to work.
There is currently a problem only with active checks - In the logfile from the agent is states:
active check configuration update from [xxx.xxx.xxx.xxx:10051] started to fail (cannot connect to [[xxx.xxx.xxx.xx]:10051]: (null))
All passive checks responds correctly.
I've checked that the config hostname is identical in both ends (frontend and agent conf) The IP addresses are correctly configured. I've upgraded the agent to v.4.0.7. I've tried deleting the host in the frontend and creating it with a new hostname and changed it in the agent. I've tried Telnet to the proxy on port 10051, that works also.
Still only passive checks works, not active checks.
So I'm kinda outta ideas. We have several other agents that works fine.
Therfore I'm now posting my issue here to get some new pointers as to where the problem is.
After an update of our system from 3.0 LTS to 4.0 LTS one Zabbix agent on a Windows box started to act out making hundreds of errors.
The setup is with a server <-> proxy <-> agent
Today I was out by the Windows PC and tried to get it to work.
There is currently a problem only with active checks - In the logfile from the agent is states:
active check configuration update from [xxx.xxx.xxx.xxx:10051] started to fail (cannot connect to [[xxx.xxx.xxx.xx]:10051]: (null))
All passive checks responds correctly.
I've checked that the config hostname is identical in both ends (frontend and agent conf) The IP addresses are correctly configured. I've upgraded the agent to v.4.0.7. I've tried deleting the host in the frontend and creating it with a new hostname and changed it in the agent. I've tried Telnet to the proxy on port 10051, that works also.
Still only passive checks works, not active checks.
So I'm kinda outta ideas. We have several other agents that works fine.