FW: "Host

[Marc Powell]

On Monday, March 29, 2004 8:13 AM, Daniel.Mesimer at med.va.gov shared with
us:

> All,
> 
> I am using Nagios 1.2 am the forwarded message here is what Nagios is
> sending as its status update email. 
> It is obviously not formatted correctly (or at least not the way I
> expected it to be formatted).  Is there something I can change to
> make this behave more the way I expect it to?  
> 
> Thanks
> 
> Dan Mesimer
> Kansas City VA Medical Center
> Network Support
> 
> 
> -----Original Message-----
> From: nagios at vhakannms.kansas-city.med.va.gov
> [mailto:nagios at vhakannms.kansas-city.med.va.gov]
> Sent: Sunday, March 28, 2004 8:23 AM
> To: alert at vhakannms.kansas-city.med.va.gov; ",
> daniel.mesimer at med.va.gov, DOWN, for"@b15f7.kansas-city.med.va.gov 
> Subject: "Host
> 
> 
>
""*****""Nagios""*****nnNotification""Type:""PROBLEMnHost:""b15f7nState:
""DO
>
WNnAddress:""10.120.128.46nInfo:""/bin/ping""-n""-U""-c""1""10.120.128.4
6nnD
> ate/Time:""Sun""Mar""28""08:22:40""CST""2004n""


Take a look at your host/service notify-by-email commands and make sure
that they are using whatever flags are necessary to enable
interpretation of escape sequences for your OS. If the commands are
using echo, you'll probably need to add a -e argument to it (i.e. echo
-e "***** Nagios *****\n..."). I believe printf interprets escape
sequences properly by default so you could use that instead of echo -e
but you should consult the man pages as both options vary by OS and
release.

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
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