Windows Server 2008 - Agent Startup Error

[Plaice]

Have a strange issue with one server and the Zabbix agent. After a reboot the other evening the agent just won't start. When starting from Services error seen is:

Windows could not start the Zabbix Agent service on Local Computer.

Error 1067: The process terminated unexpectedly.

Only error we really see in the event logs is:

Log Name: System
Source: Service Control Manager
Date: 31/07/2012 09:46:17
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: 3TRPDDB01.3T.local
Description:
The Zabbix Agent service terminated unexpectedly. It has done this 13 time(s).

This has been working fine for months before the reboot. All other servers that were rebooted at the same time are ok and working as expected.

[tchjts1]

First I would check on zabbix_agentd.conf and make sure everything is in order there.

Next, I would look at the log on the host. What is the zabbix_agentd.log reporting? You could set log tracing to 4 and see if that gives you any information.

In zabbix_agentd.conf, set:

DebugLevel=4

Try to start the agent.

If that doesn't work, do a fresh re-install of the agent.

This will uninstall and remove the Zabbix service:
c:\<path>\zabbix_agentd –u -c c:\<path>\zabbix_agentd.conf

[Plaice]

Had already tried a fresh install of the agent with the same issue. Here's what the log is reporting:

6632:20120801:092934.571 Zabbix Agent started. Zabbix 1.8.4 (revision 16601).
6632:20120801:092934.603 Listener failed with error: bind() for [[-]:10054] failed with error 10013: An attempt was made to access a socket in a way forbidden by its access permissions..

[Plaice]

Sorted it, was a port conflict. Bit of reconfiguration and it's all working again.

[stickynotes]

Hii Plaice,
I am getting the same error on one of the server can you please tell me what reconfigurations you have done on the port. I would be thankful if you help me asap.

Thanks and Regards,

Abhishek

[phirschorn]

Fix worked for me

I experienced the same. The problem was resolved in the following way.

First: I changed the listenport in the zabbix_agentd.win.conf to 10055 in the .conf file, started the service, the service started.
This really didn't make sense because A netstat revealed that nothing was listening on port 10050. Then I changed the port back to 10050 and assigned ListenIP to the ip of the server and tried to start again, it worked.

[stickynotes]

Thank you Phirschorn.