Notification emails are blank

ChrisN · April 11, 2006, 4:39pm

I am receiving notification alerts from Nagios that have blank values. When I use the check_ping command and release a hosts IP address I get the following email:

Subject: [blockquote]** PROBLEM alert - amds-expolap06/ is **[/blockquote]

Body: [blockquote]***** Nagios *****

Notification Type: PROBLEM

Service:
Host: amds-expolap06
Address: 10.0.1.11
State:

Date/Time: Tue Apr 11 10:14:20 MDT 2006

Additional Info:[/blockquote]

Any ideas? This only appears to be occuring with the check_ping command. Everything seems fine with the check_http, check_ftp, and other check commands I’m using. It would be very helpfull if I could get Nagios to tell me what the problomatic service is and what state its in. A google search and the official Nagios documentation have yielded no answers for me. I’m running this on Gentoo Linux.

Thanks for reading.

system · April 11, 2006, 4:51pm

What version of Nagios are you running? Certain values in the default v2.x notification commands don’t really work.

ChrisN · April 11, 2006, 5:06pm

This is Nagios 2.x. So it sounds like I have to write my own command for this? Unless there are some freely available ones.

Any known work arounds?

jakkedup · April 13, 2006, 9:23pm

meulie.net/portal_plugins/fo … c.php?6194
In the above url, I point out many problem’s in the docs, and also in the nagios 2.x installation in general.
One of them is what you have noticed.
The problem is this, quoting the other thread,

jakkedup:

The nagios docs show that many macro’s have been removed/replaced.
One in particular is:
$DATETIME$ from V1.x has been replaced with $LONGDATETIME$ and/or $SHORTDATETIME$
The problem is that in the notify by email command from the minimal.cfg had $LONGDATETIME$ in the command definition, and I replaced it with $SHORTDATETIME$. Having the “short” in there blew up the rest of the command output.

So, it appears to me, that the macro $SHORTDATETIME$ does not work. Will someone verify this please?

Not only that, but minimal.cfg should NOT have had the command defined such as it is below. The reason is because $OUTPUT$ is no longer valid, It has been replaced with $HOSTOUTPUT$ and/or $SERVICEOUTPUT$ WTF is this about? Doesn’t anyone check these configs before they release it as a “STABLE RELEASE?”

define command{
command_name notify-by-email
command_line /usr/bin/printf “%b” “***** Nagios ***\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $SHORTDATETIME$\n\nAdditional Info:\n\n$OUTPUT$" | /bin/mail -s " $NOTIFICATIONTYPE$ alert - $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **” $CONTACTEMAIL$
}

marketxs · May 2, 2006, 11:50am

define command {
command_name notify-by-email
command_line /usr/bin/printf “%b” “***** Nagios ***\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTNAME$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $SHORTDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$" | /usr/bin/mailx -s " $NOTIFICATIONTYPE$ alert - $HOSTNAME$/$SERVICEDESC$ is $SERVICESTATE$ **” $CONTACTEMAIL$
}

shortdatetime works for me with Nagios 2.0

Havent update to 2.1 yet

ChrisN, what does your notify-by-email looks like in miscommands.cfg?

makan · May 15, 2006, 7:39pm

my problem is same with ChrisN and i’m using Nagios Version 2.3-1

i have no any problem with nagios-2.0-2.2

jakkedup · May 18, 2006, 1:59pm

Try using mail instead of mailx and see if that helps.

barjunk · May 18, 2006, 5:00pm

Try changing the notify-by-email command to just have the state you are having problems with (or make a new command).

Also, try adding a newline right after $SERVICEOUTPUT$

Mike B.

makan · May 21, 2006, 10:00am

no, it not soled this issue…

jakkedup · May 21, 2006, 7:13pm

Paste your command notify-by-email and run it by hand. Paste the output of what you just ran and the exact command line used. That way, we can do the same here.