problem setting up maintenance

[mizaring]

Event Generation

I don't know what you mean with "multiple true events"?

When you create a trigger you have an option called "Event generation" with 2 possible value :

- Normal – events are generated normally, on TRIGGER status change
- Normal + Multiple TRUE events – events are also generated on every TRUE evaluation of the trigger

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

Just make sure your triggers are "Normal" and not "Normal + Multiple TRUE events"

[f.koch]

When you create a trigger you have an option called "Event generation" with 2 possible value :

- Normal – events are generated normally, on TRIGGER status change
- Normal + Multiple TRUE events – events are also generated on every TRUE evaluation of the trigger

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

Just make sure your triggers are "Normal" and not "Normal + Multiple TRUE events"

ok thx, I use "normal" event generation.

[mizaring]

No email this week!

Hi all,

I didn't receive any email this week... but I restarted the zabbix-server last week. So I guess maybe the modifications in the database are not picked up correctly by the server until you reboot it. I also found a way to reproduce the problem rather easily :

1 - Create items, triggers and actions for a host
2 - Activate one of the triggers that send a mail (you should receive an email activated by the trigger)
3 - Enter a maintenance period from now till some time in the future while the trigger is still active.
4 - Wait for 10 minutes... then try to toggle the trigger (on/off).

Works almost all the time... but be prepared to get spammed!

Please follow up on this problem!

Thanks!

[Fluze]

I also have the same problem.
Any news on the issue?
Zabbix 1.8.2 and 1.8.3.

[mizaring]

Resolved for my problem

Hi all,

We traced the problem with the zabbix support to be a configuration problem with the action. When we checked "recovery message" in the action we thought it was related to the state of the trigger (Problem = send message, Ok = send recovery message). However the "recovery message" is sent when a trigger happen and the action conditions goes to "false". So if you don't use Trigger Value = Problem as a condition in your action you can end up with this problem because the action conditions may stay true even if the trigger value is back to Ok.

Hope that helps

[Fluze]

Thank you for the quick reply! i will try it and report back.

[red1157]

Same problem....
Any news on the issue?
Zabbix agent 1.8.3
Zabbix server 1.8.3
CentOS 5.5.

[red1157]

Add condition "Trigger value=Problem" not work

[red1157]

And finally, if in action add condition "Maintenance status in "maintenance" - in my case zabbix NOT send any alerts then maintenance period active | not active and trigger false | true
I do not understand conditions "Maintenance status in "maintenance".......

[arli]

Same problem....
Any news on the issue?
Zabbix agent 1.8.3
Zabbix server 1.8.3
CentOS 5.5.

This issue described here earlier is definitely fixed in 1.8.3

[red1157]

I do not see: ( tell the post № pls

[arli]

Sorry... I posted this reply on a wrong thread. I never managed to reproduce the problem on my environment.

[scanch]

Up !
Same problem here when migrating from 1.8.3 to 1.8.4.
Without changing configuration, in the 1.8.3 version we don't receive email alerts when host are in maintenance mode, but now we are spammed.

Example that we have now in 1.8.4:
- Action is to send mail when maintenance status IS NOT in maintenance.
- Maintenance period all days at 23h50 with duration of 1h40.
- Database stopped a 0h00, zabbix send mail at 0h01 about the state of the database, subject start with "RECOVERY: ..... PROBLEM".
- From the Event tab I can see trigger is OK at 0h47, no mail are sent.
- At the end of the maintenance period (1:30AM), one minute later, Zabbix send mails about the state of the database: "Alert: ..... OK".

[mjsr]

Dead thread?

Hi there,

Just noticed *that* specific weird behaviour on our 1.8.4 installation.

Just after the maintenance period finishes, we get a notification that the host is OK.

In the worse case it could tell "{HOSTNAME} finished maintenance period 'database shutdown for full backup'" or whatever.

Thoughts? Suggestions? Ideas?

tyvm!

[igor]

Zabbix is working correctly in this case.

In order to get rid of these OK notifications after the maintenance ends you need to perform the following changes in the configuration of your action:

1. In the configuration of your action from "Action conditions" you should remove option "trigger value = "OK"" and leave option "Trigger value = "PROBLEM"" and also leave option "Maintenance status not in "maintenance"";

2. Turn on (enable) recovery messages in this action;

This will allow you NOT to receive notifications about the Problem events that occurred during the Maintenance period and also will not send recovery messages (OK messages) when maintenance will ends.