Nagios Support Forum

Good afternoon.
I noticed that nagios often receive false notifications.
Example:
max check attempts: 3
check interval: 1
retry interval: 1


If from the status of critical soft 2 goes to state ok, the status becomes hard 3 and an alert is sent:


[14-09-2019 01:17:32] SERVICE ALERT: server_stak_bld;check_ping;OK;HARD;3;PING OK - Packet loss = 0%, RTA = 1.81 ms
[14-09-2019 01:16:28] SERVICE ALERT: server_stak_bld;check_ping;CRITICAL;SOFT;2;PING CRITICAL - Packet loss = 0%, RTA = 15.39 ms
[14-09-2019 01:15:23] SERVICE ALERT: server_stak_bld;check_ping;CRITICAL;SOFT;1;PING CRITICAL - Packet loss = 0%, RTA = 10.76 ms
server_stak_bld check_ping OK 14-09-2019 01:17:32 24x7 notify-service-247-email PING OK - Packet loss = 0%, RTA = 1.81 ms
server_stak_bld check_ping OK 14-09-2019 01:17:32 24/7- sms notify-service-by-sms PING OK - Packet loss = 0%, RTA = 1.81 ms
server_stak_bld check_ping OK 14-09-2019 01:17:32 admin notify-service-by-email PING OK - Packet loss = 0%, RTA = 1.81 ms

What version of Nagios Core are you running?

There were a few bugs in the early 4.4.x versions that could cause this

Updated a week ago from 4.4.2 to 4.4.5
I also thought the problem was because of this, therefore it was updated at the beginning, but after the update the problem persisted.

It still could be residual affects from the bug, once the parameters had been corrupted a host/service would need to go down and then back up again to reset, or you could do the following (command and lfile location will vary depending on OS and installation type

stop nagios remove retention.dat start nagios

I did this, unsubscribe in a couple of days, helped or not.
Give thanks.

AlfaArt wrote:I did this, unsubscribe in a couple of days, helped or not.
Give thanks.

Sounds good