zabbixw32.exe help please!

[bDok]

I have one windows 2000 server that is working wonderfully now with zabbix. I copied over the information to another windows 2000 server and did the whole

zabbixw32.exe install

with the zabbix_agentd.conf file in the c:\ directory

it installed just fine and registers in the services menu, but on start up it hangs and gives the msg
Could not start the Zabbix W32 Agent Service on Local Computer
Error 1053: The service did not respond to the start or control request in a timely fashion.

help please



So confused as to how it worked on one machine and when copied over to another it doesn't work.

Cheers,
B

[safl]

Hmm which servicepacks are on those two boxes?

[bDok]

should be the same ones. Both running windows 2000 and both on service pack 4. Is there any more logs I can be checking to see what is stopping it from starting?

[safl]

Try this:
On the windows box goto:
Control Panel>Administration>Services
Find Zabbix is the list of services.
Right click on it and select properties.
Look at the 'path box' it should read something like:
"C:\zabbix\ZabbixW32.exe" --config "c:\zabbix\zabbix_agentd.conf"
If the path to the config file is wrong the zabbix service refuses to start.

Hope this helps

- Simon

[lecars]

Try this:
On the windows box goto:
Control Panel>Administration>Services
Find Zabbix is the list of services.
Right click on it and select properties.
Look at the 'path box' it should read something like:
"C:\zabbix\ZabbixW32.exe" --config "c:\zabbix\zabbix_agentd.conf"
If the path to the config file is wrong the zabbix service refuses to start.

Hope this helps

- Simon

i had same problem.
relative paths didn't work, use always to install
zabbixw32 --config "COMPLETE_PATH!!!" install

sl3

[ryanknapper]

I'm trying to upgrade today and my win32 agents won't start either. From the command line I get:

c:\>zabbixw32 --config "c:\zabbix_agentd.conf"
StartServiceCtrlDispatcher() failed: The service process could not connect to the service controller.

[janand2]

Hi,

did you find any solution?
I get the same error "StartServiceCtrlDispatcher() failed: The service process could not connect to the service controller." .
OS is Windows 2003 SP1 and Windows 2000 SP4.
Thanks for your help.

[myxz]

IMO You dont need --config when zabbix configuration is in c:\. You need it when configuration file is in different location. when it is in c:\ I simply do zabbixw32.exe install.

[zirconx]

I'm trying to upgrade today and my win32 agents won't start either. From the command line I get:

c:\>zabbixw32 --config "c:\zabbix_agentd.conf" StartServiceCtrlDispatcher() failed: The service process could not connect to the service controller.

I am just getting into Zabbix, and am trying to install an agent on one of our windows servers. I'm getting the same error. About ready to give up on zabbix, too many errors and not enough documentation to figure them out. Typical of an open source project.

[bing]

Check the temp path exists

make sure the temp path, c:\tmp by default exists or it wont start.

[sysigs]

try to see if you have all zabbix_agentd.conf configuration ok by using
"zabbixw32 --config C:\zabbix_agentd.conf test vfs.fs.size[c:,free]"
it will give you :
Using configuration file "C:\zabbix_agentd.conf"
Configuration file OK
[06-Oct-2006 08:59:31] *************** Log file opened ****************
[06-Oct-2006 08:59:31] 4716 Debug Info: AddAlias == OK
[06-Oct-2006 08:59:31] 2428 Debug Info: CollectorThread start
[06-Oct-2006 08:59:31] 2428 Debug Info: counterPath1
[06-Oct-2006 08:59:31] 2428 Debug Info: \Processor(_Total)\% Processor Time
[06-Oct-2006 08:59:31] 2428 Debug Info: counterPath2
[06-Oct-2006 08:59:31] 2428 Debug Info: \Processor(0)\% Processor Time
[06-Oct-2006 08:59:31] 2428 Debug Info: counterPath2
[06-Oct-2006 08:59:31] 2428 Debug Info: \Processor(1)\% Processor Time
[06-Oct-2006 08:59:31] 2428 Debug Info: counterPath3
[06-Oct-2006 08:59:31] 2428 Debug Info: \System\Processor Queue Length
[06-Oct-2006 08:59:31] Collector thread initialized successfully
vfs.fs.size[c:,free] [13851041792.000000]
or a message error