Nagios notification message unreadable

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Chris Guo
> Sent: Thursday, April 28, 2005 4:42 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios notification message unreadable
> 
> Hi,
> 
> My name is Chris, we are using Nagios as network monitor in our
company.
> And it turns out it's a very useful tool. But one thing weird about
nagios
> is the notification message is unreadable. For example, we have one
host
> called "LAYER3_SWITCH" with IP address "192.168.3.254", and we got
problem
> by pinging it. Then nagios sent notification message like this:
> 
> 
> 
> Subject: "**
> 
>
""*****""Nagios""*****nnNotification""Type:""PROBLEMnnService:""PINGnHos
t:
>
""LAYER3_SWITCHnAddress:""192.168.3.254nState:""CRITICALnnDate/Time:""We
d"
> "Apr""27""04:14:49""PDT""2005nnAdditional""Info:nnPING""CRITICAL""-
> ""Packet""loss""=""60%,""RTA""=""9.00""ms""
> 
> 
> 
> I wonder if this is normal or I did something wrong. Any help will be
> highly appreciated.

Your notification command isn't properly parsing backslash-escaped
characters. If it uses gnu echo, you need to change it to 'echo -e'. If
it's another echo, use the man page to figure out the correct flag.
printf should automatically handle escape characters properly.

--
Marc


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id5hix
_______________________________________________
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