Nagios notification bug?
Marc Powell
mpowell at ena.com
Thu Mar 27 18:28:28 CET 2003
It sounds like in both cases there are multiple nagios processes
running, possibly due to starting the daemon multiple times without
killing earlier iterations. Use the init script to stop the daemon then
ps to see if you have any nagios processes still running. If so, kill
those then restart nagios.
--
Marc
> -----Original Message-----
> From: Jeremy Russell [mailto:Jeremy.Russell at chickasaw.net]
> Sent: Thursday, March 27, 2003 11:06 AM
> To: Gerald; Nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Nagios notification bug?
>
> I too have had this happen, I done things like turn notifications
> completely off, but I still get them. I finally will stop getting
> notifications when I have stoped and started the daemon several times.
> I'm not sure if it has something to do with retention or something. I
> can turn notifications back on and they start immediately. It just
> happens when disabling something. It doesn't bother me though. :)
>
>
>
> -----Original Message-----
> From: Gerald [mailto:gcoon at inch.com]
> Sent: Thursday, March 27, 2003 10:26 AM
> To: Nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios notification bug?
>
>
> Ethan & Developers,
>
> I have a machine running netsaint and nagios in parallel.
>
> Nagios sends out warning pages on hosts that are configured not to
send
> "Warning" pages. The netsaint process running on the same machine
> checking the same servers/services does not do this.
>
> Here is my concern based on the nagios documentation:
>
> When Do Notifications Occur? A: Hard state changes.
> https://netsaint.inch.com/nagios/docs/notifications.html
>
> (The documentation defines Hard state changes as...)
> https://netsaint.inch.com/nagios/docs/statetypes.html
>
> If I stop here then nagios paged me for the service going from OK ->
> Warning (...which is a hard state change)
>
>
> Here is my log of this event happening once. (It has happened more
than
> once.)
> Recovery:
> Service Ok[03-26-2003 13:49:28] SERVICE ALERT:
> ServerName;PING;OK;HARD;3;PING OK - Packet loss= 0%, RTA = 99.77 ms
>
> 3.
> Service Warning[03-26-2003 13:44:29] SERVICE ALERT:
> ServerName;PING;WARNING;HARD;3;PING WARNING - Packet loss = 0%, RTA =
> 313.78 ms
>
> 2.
> Service Warning[03-26-2003 13:43:29] SERVICE ALERT:
> ServerName;PING;WARNING;SOFT;2;PING
> WARNING - Packet loss = 20%, RTA = 458.14 ms
>
> 1.
> Service Warning[03-26-2003 13:42:38] SERVICE ALERT:
> ServerName;PING;WARNING;SOFT;1;PING
> WARNING - Packet loss = 20%, RTA = 190.77 ms
>
>
> Here is the part of the config file that should have told nagios not
to
> page me for this service:
>
> notification_options c,r
>
> http://nagios.sourceforge.net/docs/1_0/xodtemplate.html#service
>
> Is the notification_options directive ignored in nagios now?
>
> The rest is just my configs for this service in case someone wants to
> look at them and point out what I'm missing.
>
> nagios.cfg entry
> cfg_file=/usr/local/etc/nagios/ded_hosts.cfg
> cfg_file=/usr/local/etc/nagios/ded_services.cfg
>
> ded_hosts.cfg entry
> # 'Server' host definition
> define host{
> use generic-host
> host_name Server
> alias Server_alias
> address x.x.x.x
> parents main.router.x
> check_command check-host-alive
> max_check_attempts 3
> notification_interval 240
> notification_period workhours
> notification_options d,u,r
> }
>
>
> ded_services.cfg entry
> # Service definition
> define service{
> use generic-service
> host_name Server
> service_description PING
> is_volatile 0
> check_period 24x7
> max_check_attempts 3
> normal_check_interval 5
> retry_check_interval 1
> contact_groups admins
> notification_interval 240
> notification_period workhours
> notification_options c,r
> check_command check_ping_longOK
> }
>
> # 'check_ping_longOK' command definition
> define command{
> command_name check_ping_longOK
> command_line $USER1$/check_ping -H $HOSTADDRESS$ -p 5 -t 60
> -w
> 220.0,20% -c 1000.0,50%
> }
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list