Elevated alerts

[jmoseley at corp.xanadoo.com]

Grant Lowe <glowe at sbcglobal.net> wrote:

>Hi James,
>
>One question/problem with this.  I'm not getting any pages or email on
when services are showing up as critical in the nagios.log.  For example:>
>
>[1231773440] SERVICE ALERT: blarney;Check Remote Zombie
Processes;CRITICAL;SOFT;1;PROCS CRITICAL: 13 processes with STATE = Z
>[1231773500] SERVICE ALERT: blarney;Check Remote Zombie
Processes;CRITICAL;SOFT;2;PROCS CRITICAL: 23 processes with STATE = Z
>[1231773560] SERVICE ALERT: blarney;Check Remote Zombie
Processes;CRITICAL;SOFT;3;PROCS CRITICAL: 21 processes with STATE = Z
>[1231773620] SERVICE ALERT: blarney;Check Remote Zombie
Processes;CRITICAL;SOFT;4;PROCS CRITICAL: 32 processes with STATE = Z
>[1231773680] SERVICE ALERT: blarney;Check Remote Zombie
Processes;CRITICAL;HARD;5;PROCS CRITICAL: 18 processes with STATE = Z
>[1231747200] CURRENT SERVICE STATE: blarney;Check Remote Number of
Processes;CRITICAL;HARD;5;PROCS CRITICAL: 1388 processes
>
>Any thoughts?

As I was telling another poster, make the config as simple as can be until
you get this issue worked out. ;-)  Meaning, use the default notification
macros and setup one host and one contact definition until you get this
working.  Have you checked your notifiction options in your 'Check Remote
Zombie Processes' service definition?

notification_options[w,u,c,r,f,s]

You most certainly want to have a 'c' in there.  Are notifictions enabled
for this service (as defined in the service template you are probably
using)?

James




------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
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