I can't seem to parse It doesn't make sense to get a recovery
notification for something you never knew was a problem.
Are you saying that since Nagios doesn't consider an unknown a
problem, it won't send a recovery? Because it does... And in
this case, I certainly want to know when a service
On Tue, Jun 11, 2013 at 11:12:23AM -0500, C. Bensend wrote:
I can't seem to parse It doesn't make sense to get a recovery
notification for something you never knew was a problem.
see the original language here:
http://nagios.sourceforge.net/docs/3_0/notifications.html
Note: Notifications about
There is workaround this is how I fixed in our environment
use_large_installation_tweaks=1 in nagios.cfg see whether this helps this
removes the warning for you
Regards
Sunil
On Tue, Jun 11, 2013 at 9:52 PM, Justin T Pryzby just...@norchemlab.comwrote:
On Tue, Jun 11, 2013 at 11:12:23AM
see the original language here:
http://nagios.sourceforge.net/docs/3_0/notifications.html
Note: Notifications about host or service recoveries are only sent out
if a notification was sent out for the original problem. It doesn't
make sense to get a recovery notification for something you
Yep, I've had that one enabled for quite some time. :)
There is workaround this is how I fixed in our environment
use_large_installation_tweaks=1 in nagios.cfg see whether this helps this
removes the warning for you
Regards
Sunil
On Tue, Jun 11, 2013 at 9:52 PM, Justin T Pryzby
On 6/7/2013 9:28 AM, C. Bensend wrote:
Not real sure why Nagios doesn't think that's a valid config - I
want a contact that will receive only UNKNOWN alerts for services.
Have you tried giving that contact the extra options Nagios wants, and then
defining a service escalation for that
This is by design, and it is only a warning message. The config is valid
and should work as you intended. It doesn't make sense to get a recovery
notification for something you never knew was a problem. Unknowns are not
considered problems in Nagios logic.
On Mon, Jun 10, 2013 at 1:25 PM, Chris
Have you tried giving that contact the extra options Nagios wants, and
then defining a service escalation for that contact with the
escalation_options directive set to u?
No, I haven't. It *seems* to be working as I intend. My question is
more as to why Nagios seems to think it's a bad
Hey folks,
Still ironing out the wrinkles in my 3.5.0 distributed environment.
Yesterday, I added a new contact, and on preflight check it seemed
to think that what I did wasn't smart:
Jun 6 15:11:02 hostname nagios: Warning: Service recovery notification
option for contact
