[ZBX-6767] Host set into state "not monitored" still send alert notifications Created: 2013 Jul 03  Updated: 2017 May 30  Resolved: 2013 Jul 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.0.6
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Eino Mäkitalo Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux lon1 3.9.3-x86-linode52 #1 SMP Mon May 20 09:32:28 EDT 2013 i686 i686 i386 GNU/Linux


Issue Links:
Duplicate
duplicates ZBX-4476 Nodata triggers immediately fire on n... Closed

 Description   

I have a configuration of zabbix_server and zabbix_proxy. I turn off host "X" through GUI and went to work on host "X". (network card off etc). After turning on machine, I change status back to "Monitored".

Zabbix server still send me alert email, triggers etc. ....



 Comments   
Comment by richlv [ 2013 Jul 03 ]

which trigger expressions generated events ?

Comment by Eino Mäkitalo [ 2013 Jul 03 ]

I was very basic Agent trigger and system was warm up and running when I turned monitoring on again.

Trigger: Zabbix agent on X is unreachable for 5 minutes
Trigger status: PROBLEM
Trigger severity: High
Trigger URL:

Item values:

1. Agent ping (X:agent.ping): Up (1)
2. UNKNOWN (UNKNOWN:UNKNOWN): UNKNOWN
3. UNKNOWN (UNKNOWN:UNKNOWN): UNKNOWN

Comment by richlv [ 2013 Jul 03 ]

this is not about disabled hosts being alerted on but events being generated on new/just enabled hosts. there is an issue about it that i just can't find right now

leaving this issue open until the original one is found

Comment by Marc [ 2013 Jul 03 ]

Sounds similar to ZBXNEXT-1565

Comment by richlv [ 2013 Jul 03 ]

ZBXNEXT-1565 is about already running escalations and maintenance - this is about adding a new host (or enabling a previously disabled one) and getting alerts from nodata() and similar triggers

Comment by Eino Mäkitalo [ 2013 Jul 03 ]

Yes, I have monitored this host few days OK, and maybe I did it wrong way to maintain it, but I change state not monitored - do my job - and change back to monitored. Maybe this has same root cause?

Comment by Oleksii Zagorskyi [ 2013 Jul 04 ]

Eino, we steel don't see the trigger expression.
Taking into account your trigger name (it looks like a build in 2.0 setup) I suppose your trigger expression is:
{Template App Zabbix Agent:agent.ping.nodata(5m)}=1

I guess Rich meant ZBX-4476, feel free to close

<richlv> exactly that issue, closing

Comment by Eino Mäkitalo [ 2013 Jul 05 ]

Fix then ZBX-4476 to affects versio 2.0.6 too

Comment by richlv [ 2013 Jul 05 ]

we usually consider that issue is still ongoing if not closed, but sure, added 2.0.6 to that one

Generated at Sat Aug 09 09:06:52 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.