I have been trying to use zabbix for a few days now and because of not being a linux guru or something, had some problems with that.
But all in all, I got the server running and monitoring itself just fine. So then I wanted to start adding clients.... and ran into a problem.
Whatever I would do, I would get a connection refused. I tried many different setups and wanted logfiles, searched the forums over and over.
But tonight, I finally figured out the problem.
In the guide, it tells you to take the default config file and edit it to your own wishes. And that is exactly what I did.
But... this doesn't work. It appears to work on a windows machine, but in reality, it does not.
When you use such a config file, you get the following :
C:\Temp>ZabbixW32.exe --config c:\temp\zabbix_agentd.conf standalone
Using configuration file "c:\temp\zabbix_agentd.conf"
Configuration file OK
Which, in the eyes of someone not having used zabbix before, looks fine? Everything is working and running.
But... the only thing it will do, is give you connection refused.
What is the problem?
In the config file there is the following line :
LogFile=/tmp/zabbix_agentd.log
When you put a ' # ' in front of it, suddenly the agent starts to work :
C:\Temp>ZabbixW32.exe --config c:\temp\zabbix_agentd.conf standalone
Using configuration file "c:\temp\zabbix_agentd.conf"
Configuration file OK
[26-Sep-2006 01:21:35] *************** Log file opened ****************
[26-Sep-2006 01:21:36] Collector thread initialized successfully
[26-Sep-2006 01:21:36] Zabbix Win32 Agent started
[26-Sep-2006 01:21:36]
*** Zabbix Win32 agent operational. Press ESC to terminate. ***
Information: 2356 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 4016 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 192 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 4060 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 3752 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 3552 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 816 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 4008 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 1496 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 1612 : Listen thread is Started.
The problem is being that the directory structure used, is unix based, which off course won't work in windows. Making it something like c:\temp\zabbix_agentd.log or even just zabbix_agentd.log, works fine.
Please please, create a way around this or fix this in your documentation, or even if I did overlook it, or do something wrong, make it a bit more clear?
It took me nearly 2 days of frustration to find the problem.
I can verify that I had the same problem using the W32 on an XP_sp2_x86 machine and the W64 on a Win2k3_R2_x64 machine.
The difference in output from the server side?
With line in agentd config file:
zabbix_get -s 10.10.xxx.xxx -k agent.ping
Error: Connection refused
Without line in agentd config file or correct log file setting:
zabbix_get -s 10.10.xxx.xxx -k agent.ping
1.000000
Any question, don't hesitate to ask..
Kind regards,
Quindor
But all in all, I got the server running and monitoring itself just fine. So then I wanted to start adding clients.... and ran into a problem.
Whatever I would do, I would get a connection refused. I tried many different setups and wanted logfiles, searched the forums over and over.
But tonight, I finally figured out the problem.
In the guide, it tells you to take the default config file and edit it to your own wishes. And that is exactly what I did.
But... this doesn't work. It appears to work on a windows machine, but in reality, it does not.
When you use such a config file, you get the following :
C:\Temp>ZabbixW32.exe --config c:\temp\zabbix_agentd.conf standalone
Using configuration file "c:\temp\zabbix_agentd.conf"
Configuration file OK
Which, in the eyes of someone not having used zabbix before, looks fine? Everything is working and running.
But... the only thing it will do, is give you connection refused.

What is the problem?
In the config file there is the following line :
LogFile=/tmp/zabbix_agentd.log
When you put a ' # ' in front of it, suddenly the agent starts to work :
C:\Temp>ZabbixW32.exe --config c:\temp\zabbix_agentd.conf standalone
Using configuration file "c:\temp\zabbix_agentd.conf"
Configuration file OK
[26-Sep-2006 01:21:35] *************** Log file opened ****************
[26-Sep-2006 01:21:36] Collector thread initialized successfully
[26-Sep-2006 01:21:36] Zabbix Win32 Agent started
[26-Sep-2006 01:21:36]
*** Zabbix Win32 agent operational. Press ESC to terminate. ***
Information: 2356 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 4016 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 192 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 4060 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 3752 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 3552 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 816 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 4008 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 1496 : Listen thread is Started.
[26-Sep-2006 01:21:36] Information: 1612 : Listen thread is Started.
The problem is being that the directory structure used, is unix based, which off course won't work in windows. Making it something like c:\temp\zabbix_agentd.log or even just zabbix_agentd.log, works fine.
Please please, create a way around this or fix this in your documentation, or even if I did overlook it, or do something wrong, make it a bit more clear?
It took me nearly 2 days of frustration to find the problem.
I can verify that I had the same problem using the W32 on an XP_sp2_x86 machine and the W64 on a Win2k3_R2_x64 machine.
The difference in output from the server side?
With line in agentd config file:
zabbix_get -s 10.10.xxx.xxx -k agent.ping
Error: Connection refused
Without line in agentd config file or correct log file setting:
zabbix_get -s 10.10.xxx.xxx -k agent.ping
1.000000
Any question, don't hesitate to ask..
Kind regards,
Quindor
Comment