debugging notifications

[Marc Powell]

> -----Original Message-----
> From: Eric Doutreleau [mailto:Eric.Doutreleau at int-edu.eu]
> Sent: Monday, January 21, 2008 2:53 PM
> To: Marc Powell
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] debugging notifications
> 
[chop]

>  /usr/lib/nagios/plugins/notify_by_jabber
> doutrele at jabberd.int-evry.fr,procacci at jabberd.int-evry.fr,gabor
>
et at jabberd.int-evry.fr,ghanotak at jabberd.int-evry.fr,gilles at jabberd.int-
> evry.fr
> "***** Nagios  *****   Not
> ification Type: PROBLEM Service: mise a jour Host: serveur snmp
Address:
> 157.159.21.5 State: CRITICAL  Da
> te/Time: Mon Jan 21 21:40:38 CET 2008  Additional Info:  YUM CRITICAL
-
> updates found: 6 critical, 0 warn
> ing"
> 
> if i run sh /tmp/jabber.txt i got the messages through jabber.
> it seems that nagios just not able to launch directly the command

When you are testing 'sh /tmp/jabber.txt', are you doing so as the user
'nagios' (i.e. this may be a permissions issue)? Does the
notify_by_jabber script rely on any environment variables that may not
be present for a non-interactive session? Does the script specify full
paths to all external files/programs it references? Follow that logic
through to all programs/scripts that notify_by_jabber calls.

--
Marc 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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