Agent and server are reporting different results

[ncurry]

I am running Zabbix server 1.8.7 on ScientificLinux 6.1 and have a agent running 1.8.7 on CentOS 5. I have started monitoring a network connection to a remote host from the CentOS system using the "net.tcp.port[192.168.0.1,8001]" key.

I noticed that the server was getting 0 for this consistently and saying that it was up. So I ran zabbix_get and got the same data:
zabbix_get -s matm-asdex -k net.tcp.port[192.168.0.1,8001]

When I run the zabbix_agentd command to retrieve the information on the host itself I get a response of: [u|1]
zabbix_agentd -t net.tcp.port[192.168.0.1,8001]

I checked the zabbix_server.log and noticed the following log entries appearing constantly in the log file (MASD is the hosts name):

085:20111020:153201.827 Zabbix Host [MASD]: first network error, wait for 15 seconds
32085:20111020:153310.322 Zabbix Host [MASD]: first network error, wait for 15 seconds
32083:20111020:153357.101 Zabbix Host [MASD]: first network error, wait for 15 seconds
32084:20111020:153517.890 Zabbix Host [MASD]: first network error, wait for 15 seconds
32080:20111020:153716.388 Zabbix Host [MASD]: first network error, wait for 15 seconds
32082:20111020:153756.716 Zabbix Host [MASD]: first network error, wait for 15 seconds
32086:20111020:153818.223 Zabbix Host [MASD]: another network error, wait for 15 seconds
32086:20111020:153834.614 Zabbix Host [MASD]: another network error, wait for 15 seconds

I don't know if the entries in the log are related or not but the possibility is there. I do get data from the system other than the connection status but do notice there are gaps in the data received.

Has anyone else seen this happen before or know how to correct it. I did see anything in the configuration files and have not read anything about other people having the same issue in the forums.

[richlv]

my first suspicion would be some item that's slow and times out. when that happens, host itself gets disabled for 15 seconds, and thus other items will end up missing some values as well.

best would be to upgrade to 1.8.9, as it has one tiny, but incredibly helpful improvement to logging - these messages contain item key, which helps to identify the source of the problem

http://www.zabbix.com/documentation/...r_improvements