bogus unreachables after real unreachables

[NB-beheer]

We have a server which experienced network problems. This resulted in Zabbix unreachable events. Those events were correct.

Now that the problems have been fixed a few days ago, Zabbix keeps whining several times a day. For instance, according to Zabbix the server was down for over an hour today, but it was working just fine.

We are using the (standard) trigger status.min(30)=2
The client was running 1.4.1 (FreeBSD port). Now it's on 1.4.2. No difference.

Zabbix server log:
11097:20071127:130321 Host [SERVER]: first network error, wait for 15 seconds
11097:20071127:130321 Parameter [system.cpu.load[,avg1]] will be checked after 20 seconds on host [SERVER]
11100:20071127:130324 Host [SERVER]: first network error, wait for 15 seconds
11100:20071127:130324 Parameter [vfs.fs.size[/opt,used]] will be checked after 120 seconds on host [SERVER
]
11102:20071127:130325 Host [SERVER]: first network error, wait for 15 seconds
11102:20071127:130325 Parameter [system.cpu.load[,avg15]] will be checked after 80 seconds on host [SERVER
]
11099:20071127:130326 Host [SERVER]: first network error, wait for 15 seconds
11099:20071127:130326 Parameter [system.cpu.load[,avg5]] will be checked after 40 seconds on host [SERVER]
11132:20071127:130349 Host [SERVER]: another network error, wait for 15 seconds
11132:20071127:130409 Host [SERVER]: another network error, wait for 15 seconds
11132:20071127:130429 Host [SERVER] will be checked after 60 seconds
11132:20071127:130535 Host [SERVER] will be checked after 60 seconds
11132:20071127:130641 Host [SERVER] will be checked after 60 seconds
....... all the same lines .....
11132:20071127:143706 Host [SERVER] will be checked after 60 seconds
11132:20071127:143812 Host [SERVER] will be checked after 60 seconds
11132:20071127:143912 Enabling host [SERVER]

It looks like we still have some issues but at the same time Zabbix stops trying which isn't supposed to happen.

[cbidwell]

I, too, am getting these types of errors. Running FreeBSD 5.4 here and zabbix would complain that the server would become unreachable when, in fact, nothing at all had gone wrong. I can't figure it out for the life of me and it only seems to occur in BSD-related systems.

Can anyone provide further info as to how to resolve this issue?

This is my process list on the server which zabbix says is currently down:

# ps -ax | grep zabbix
76957 ?? IN 0:00.00 zabbix_agentd: main process (zabbix_agentd)
76958 ?? SN 0:15.85 zabbix_agentd: main process (zabbix_agentd)
76959 ?? IN 7:07.21 zabbix_agentd: processing request (zabbix_agentd)
76960 ?? IN 7:07.16 zabbix_agentd: processing request (zabbix_agentd)
76961 ?? IN 7:09.23 zabbix_agentd: processing request (zabbix_agentd)
76962 ?? IN 6:58.29 zabbix_agentd: processing request (zabbix_agentd)

I'm out of ideas here. Any help would be greatly appreciated.

[NB-beheer]

I assume it's fixed in 1.4.3:

Release notes:
[ZBX-192] fixed active checks stops after connection loss