Error sending result back

[teferi]

(zabbix 1.5.3)
28456:20080815:122351 Error sending result back
28447:20080815:122351 Error sending result back
28445:20080815:122351 Error sending result back

I get these in my proxy's logs from time to time. I digged the code a bit and found it was coming from trapper.c due to some error when sending results from proxy to server. correct me if I'm wrong please.

What might be causing these errors? Maybe I overload my proxies too much? each monitors a good deal of items.



I've turned the DebugLevel to 4 on one of the proxies to seek more info, but it's rather hard to catch that mistake.

[teferi]

Still cannot realise why the error occurs. And can't find any trace of it in 300MB log file produced by DebugLevel=4

Can it be that proxy exceeds kern.ipc.maxsockbuf value?

If I'll be unable to fix the problem today - tomorrow I think I'll try using more proxies.

[teferi]

The problem seems to be resolved. I made 2 things to achieve this (on FreeBSD).
1 - Significantly increased number of trappers. I found the error text in trapper.c in source files, so one guess was that there's not enough trappers running(althow I tried to tun the number in acordance with the number of active checks performed). I also switched most of items to be active checks.
2 - I set net.inet.tcp.blackhole=2 and net.inet.udp.blackhole=1. I did so after I noticed lots of lines like "Limiting closed port RST response from 417 to 200 packets/sec" in my dmesg output. Not exactly sure if it's related, but it appeared on every zabbix_proxy machine.

Another issue solved by the performed actions - is numerous "Lock wait timout exceeded" lines in log files.

I'd want to repeat that problem only seems to be solved. If it wouldn't show up in some time then I'll write another post here. =)

[teferi]

Actually the problem doesnot seem to be solved. It shows up occasionaly after restarting of proxy. Seems like some nasty little bug that I hope is already solved in 1.5.4 =)