<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> To follow up on my own email. It looks like this is not just the upgrade. I moved my 3.2.1 binary back in, and it still happens.<o:p></o:p> <o:p> </o:p> And I’ve found that it’s not limited to the notification commands:<o:p></o:p> <o:p> </o:p> [1378314473] SERVICE ALERT: Server86;Server86 - Ping;UNKNOWN;SOFT;1;check_ping: Invalid hostname/address - 19216874204<o:p></o:p> [1378314493] SERVICE ALERT: Server86;Server86 - SAP;CRITICAL;SOFT;1;TCP CRITICAL - Invalid hostname, address or socket: 19216874204<o:p></o:p> [1378314503] HOST ALERT: Server86;DOWN;SOFT;1;check_ping: Invalid hostname/address - 19216874204<o:p></o:p> [1378314533] SERVICE ALERT: Server86;Server86 - Ping;UNKNOWN;HARD;2;check_ping: Invalid hostname/address - 19216874204<o:p></o:p> [1378314543] HOST ALERT: Server86;DOWN;SOFT;2;check_ping: Invalid hostname/address - 19216874204<o:p></o:p> [1378314553] SERVICE ALERT: Server86;Server86 - SAP;CRITICAL;HARD;2;TCP CRITICAL - Invalid hostname, address or socket: 19216874204<o:p></o:p> [1378314553] SERVICE ALERT: Server86;Server86 - Load;WARNING;HARD;10;85% CPU load.<o:p></o:p> [1378314563] HOST ALERT: Server86;DOWN;SOFT;3;check_ping: Invalid hostname/address - 19216874204<o:p></o:p> [1378314573] HOST ALERT: Server86;DOWN;SOFT;4;check_ping: Invalid hostname/address – 19216874204<o:p></o:p> <o:p> </o:p> (the periods are removed from the IPs)<o:p></o:p> I really have no idea what caused this, but I am reviewing my config and changes I made while testing splunk, and opsgenie integration.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: Jason Gauthier Sent: Wednesday, September 04, 2013 10:28 AM To: 'nagios-users@lists.sourceforge.net' Subject: Upgraded from 3.2.1 to 3.5 - macros broke?<o:p></o:p> </div> </div> <o:p> </o:p> Greetings,<o:p></o:p> <o:p> </o:p> It seems during a recent upgrade, my notifications broke! Well, I did digging and found notification themselves are working, but the macro variables are completely botched.<o:p></o:p> <o:p> </o:p> I took “notify-by-email”, and changed it to this:<o:p></o:p> /usr/bin/printf "\"%b\" \"Notification Type: $NOTIFICATIONTYPE$ ($SERVICEACKAUTHOR$)\n\nService: $SERVICEDESC$\nHost: $HOSTNAME$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n\nComment: $SERVICEACKCOMMENT$\" | /bin/mail -s \"** $NOTIFICATIONTYPE$ alert - $HOSTNAME$/$SERVICEDESC$ is $SERVICESTATE$ **\" $CONTACTEMAIL$" >> /tmp/nagiosnotify.log<o:p></o:p> <o:p> </o:p> So, it will write the contents to a file instead of just directly piped to mail. Here is what I see:<o:p></o:p> <o:p> </o:p> "Notification Type: RECOVERY ($)<o:p></o:p> <o:p> </o:p> Service: $<o:p></o:p> Host: v-ww7b2<o:p></o:p> Address: 19216876178<o:p></o:p> State: $<o:p></o:p> <o:p> </o:p> Date/Time: W Sp 4 10:18:11 EDT 2013<o:p></o:p> <o:p> </o:p> Additional Info:<o:p></o:p> <o:p> </o:p> $<o:p></o:p> <o:p> </o:p> Comment: $" | /bin/mail -s "** RECOVERY alert - v-ww7b2/$ is $ **" bv<o:p></o:p> <o:p> </o:p> <o:p> </o:p> It seems like all of the variable are wrong. For instance, the host is v-windows7lab2. <o:p></o:p> The email address starts with “bv”, but it ends with a whole lot more!<o:p></o:p> <o:p> </o:p> I’m not sure what would be causing this, and would appreciate any input.<o:p></o:p> <o:p> </o:p> Thanks!<o:p></o:p> <o:p> </o:p> </div> </body> </html>