I'm seeing the following error show up in the zabbix proxy log on some of our proxies:
5736:20100707:045404.714 Error sending result back
Once a proxy starts reporting these errors in the proxy log, it doesn't seem to recover completely until the proxy is restarted. This is causing problems with host down type .nodata triggers on hosts that these proxies monitor - the trigger will go into problem state, then a bit of data makes it through with timestamps right around the 'dead' timer for the node and turns it ok again, but since its right on the edge, the trigger almost immediately goes into problem state again.
While I've managed to rate limit the trigger state transitions some by using hysterisis (http://www.zabbix.com/documentation/...ers#hysteresis), the triggers still cycle when they shouldn't be.
Unfortunately I haven't been able to find any conditions that are causing the proxies to get into this state. Running with a higher log level produces too much log & disk activity. At default logging levels, there are no other log messages surrounding the error sending results messages.
Any ideas?
Zabbix version 1.8
5736:20100707:045404.714 Error sending result back
Once a proxy starts reporting these errors in the proxy log, it doesn't seem to recover completely until the proxy is restarted. This is causing problems with host down type .nodata triggers on hosts that these proxies monitor - the trigger will go into problem state, then a bit of data makes it through with timestamps right around the 'dead' timer for the node and turns it ok again, but since its right on the edge, the trigger almost immediately goes into problem state again.
While I've managed to rate limit the trigger state transitions some by using hysterisis (http://www.zabbix.com/documentation/...ers#hysteresis), the triggers still cycle when they shouldn't be.
Unfortunately I haven't been able to find any conditions that are causing the proxies to get into this state. Running with a higher log level produces too much log & disk activity. At default logging levels, there are no other log messages surrounding the error sending results messages.
Any ideas?
Zabbix version 1.8