Nagios sending multiple notifications insted of one

[tgriep]

Try upgrading to version 0.5.2.39 of the NSClient++ agent to see if that helps.

Another thing to try, change the filter for that check to the following. Replace everything in $ARG2$ for that service check and see if that helps.

Code: Select all

-a "filter=type in (fixed) and readable = 1 and mounted = 1" exclude="System Reserved" ignore-unreadable

Another question, is there some sort of backup software or application that could be mounting a volume when it runs?
If you see the error again, search in the nsclient.log file for the date and time is happened to see if there is an error.

[supportagilita]

Following changes were made today:

Upgrading NSClient to current version.

adding filter to $ARG2$

found settings in host-configuration.
changes host-check-settings & host-alert-settings

now I've do have the same configurations as in service settings. set host settings
"If problems persist:
Send a notification every minutes 0 until the problem is resolved. "

will see what happens next.

is there a other way so set "if problems persists" than changing it over (attachment) ?

I'm asking because I could not find any settings in "Config -> Core Config Manager -> Host > xy > Notification"

Just found it over "Search host -> Configure -> Re-configure this host -> Notifications"

[tgriep]

To change the Notification options in the Core Config Manager, you would open up an object and go to the Alert Settings TAB.
In there is where you would change the Notification Interval, delay, etc.
The wait setting is the First Notification Delay.
The Send Notification every minutes is the Notification Interval.

https://support.nagios.com/kb/article/n ... t-286.html
https://support.nagios.com/kb/article/n ... t-539.html
https://support.nagios.com/kb/article/n ... r-717.html
https://support.nagios.com/kb/article/n ... s-728.html

[supportagilita]

Hi all,

it seems like that the host configuration "repeate in case problem still exists" was messing up the whole notification thing.

after changing this property everything seems to be good!

thx for the help!

[scottwilkerson]

Hi all,

it seems like that the host configuration "repeate in case problem still exists" was messing up the whole notification thing.

after changing this property everything seems to be good!

thx for the help!

Great!

Locking