Trigger alert flood after server restart

[sbecker]

I tuned my Mysql database yesterday and restarted both Mysql and Zabbix. The triggers page had over 13k acknowledgeable events. I had to increase my refresh time to begin to see them. Then the php stopped responding. I had to go to each group individually to acknowledge the nodata and service good triggers. I have a little over 100 hosts being monitored by Zabbix currently but that number will rise to over 600 hundred shortly. This will be a huge problem going forward.

Is there any way to avoid this in the future?

[richlv]

which zabbix version ?
this should not happen with recent versions.

[sbecker]

We are currently using v. 1.6.5. We began using v. 1.6.2 and upgraded thru 1.6.3, and 1.6.4.

[sbecker]

Does the nodata clause need to be added to each trigger to stop this?

[otheus]

Can you post more information about this, please? When you were tuning your database, did you bring it down for an extended period of time? Was this what triggered your triggers? Can you post a sample of one of the items and corresponding triggers that was ill-behaved?