Re: "HOST UP" flood after Nagios Core update
Posted: Sun Jul 08, 2018 7:52 pm
Hi.
I also suffer from similar problems.
I have not changed the setting.
The problem started after the version was upgraded from 4.3.4 to 4.4.1.
I was flooded with a notification mail of PASSIVE HOST check.
### BEGIN EMAIL ###
Subject:** RECOVERY Host Alert: myserver1.tld is UP **
BODY:
***** Nagios *****
Notification Type: RECOVERY
Host: myserver1.tld
State: UP
Address: myserver1.tld
Info: PING OK - Packet loss = 0%, RTA = 5.88 ms
Date/Time: Mon Jul 9 09:22:06 JST 2018
### END EMAIL ###
I examined the cause.
In the case of the condition below, it seems to be different processing.
* PASSIVE HOST CHECK
* Host was UP.
* Host is still UP.
* passive_host_checks_are_soft=0
https://github.com/NagiosEnterprises/na ... ks.c#L2609
vs
https://github.com/NagiosEnterprises/na ... cks.c#L987
Perhaps it seems that behavior has changed by refactoring with the added function below.
https://github.com/NagiosEnterprises/na ... cks.c#L935
Downgrading to 4.3.4, the problem no longer occurs.
Thank you.
--
Tomohiro Hosaka
I also suffer from similar problems.
I have not changed the setting.
The problem started after the version was upgraded from 4.3.4 to 4.4.1.
I was flooded with a notification mail of PASSIVE HOST check.
### BEGIN EMAIL ###
Subject:** RECOVERY Host Alert: myserver1.tld is UP **
BODY:
***** Nagios *****
Notification Type: RECOVERY
Host: myserver1.tld
State: UP
Address: myserver1.tld
Info: PING OK - Packet loss = 0%, RTA = 5.88 ms
Date/Time: Mon Jul 9 09:22:06 JST 2018
### END EMAIL ###
I examined the cause.
In the case of the condition below, it seems to be different processing.
* PASSIVE HOST CHECK
* Host was UP.
* Host is still UP.
* passive_host_checks_are_soft=0
https://github.com/NagiosEnterprises/na ... ks.c#L2609
vs
https://github.com/NagiosEnterprises/na ... cks.c#L987
Perhaps it seems that behavior has changed by refactoring with the added function below.
https://github.com/NagiosEnterprises/na ... cks.c#L935
Downgrading to 4.3.4, the problem no longer occurs.
Thank you.
--
Tomohiro Hosaka