contacts.cfg is not working properly

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
sinkak
Posts: 158
Joined: Thu Jul 30, 2015 1:30 pm

Re: contacts.cfg is not working properly

Post by sinkak »

only failed header messages are in /var/mail/ubuntu.
Where can i get success message headers?
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: contacts.cfg is not working properly

Post by rkennedy »

Look for a message in the inbox of the alerts that are working, and depending on your client you should be able to find a 'Show Headers', or 'Message Details' part.
Former Nagios Employee
sinkak
Posts: 158
Joined: Thu Jul 30, 2015 1:30 pm

Re: contacts.cfg is not working properly

Post by sinkak »

alerts-warning email and alerts911 email are linked to my gmail account

Code: Select all

                                                                                                                                                                                                                                                               
Delivered-To:[email protected]
Received: by 10.107.15.21 with SMTP id x21csp46657ioi;
        Wed, 4 Nov 2015 10:50:42 -0800 (PST)
X-Received: by 10.140.168.11 with SMTP id o11mr3380308qho.28.1446663042824;
        Wed, 04 Nov 2015 10:50:42 -0800 (PST)
Return-Path: <[email protected]>
Received: from public2-exrmf-vx-1-1.serverdata.net (public2-exrmf-vx-1-1.serverdata.net. [64.78.22.121])
        by mx.google.com with ESMTPS id j185si1658701qhc.70.2015.11.04.10.50.42
        for <[email protected]>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 04 Nov 2015 10:50:42 -0800 (PST)
Received-SPF: permerror (google.com: permanent error in processing during lookup of [email protected]) client-ip=64.78.22.121;
Authentication-Results: mx.google.com;
       spf=permerror (google.com: permanent error in processing during lookup of [email protected]) [email protected]
Received: from localhost (localhost [127.0.0.1])
	by exrmf-vx-1-1.serverpod.net (Postfix) with ESMTP id C71D4D2BF
	for <[email protected]>; Wed,  4 Nov 2015 10:50:41 -0800 (PST)
X-Virus-Scanned: by amavisd-new at exrmf-vx-1-1
Received: from public2-exrmf-vx-1-1.serverdata.net ([10.254.254.55])
	by localhost (exrmf-vx-1-1.serverpod.net [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1xAQ1vOADWz4 for <[email protected]>;
	Wed,  4 Nov 2015 10:50:41 -0800 (PST)
Received: from exmr-vx1-3.serverpod.net (unknown [10.254.254.32])
	by exrmf-vx-1-1.serverpod.net (Postfix) with ESMTP id 4B034D0AA
	for <[email protected]>; Wed,  4 Nov 2015 10:50:41 -0800 (PST)
Received: from EXHUB017-3.exch017.msoutlookonline.net (exhub017-3.exch017.msoutlookonline.net [64.78.22.18])
	by exmr-vx1-3.serverpod.net (Postfix) with ESMTP id 2A9732D041
	for <[email protected]>; Wed,  4 Nov 2015 10:50:41 -0800 (PST)
Resent-From: <[email protected]>
Received: from exmf017-2.msoutlookonline.net (10.254.253.10) by
 EXHUB017-3.exch017.msoutlookonline.net (64.78.22.43) with Microsoft SMTP
 Server id 8.3.377.0; Wed, 4 Nov 2015 10:50:41 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])	by
 smtp.exch017.serverdata.net (Postfix) with ESMTP id 03EF230163	for
 <[email protected]>; Wed,  4 Nov 2015 10:50:41 -0800 (PST)
X-Relayed-From: 107.21.36.200
X-Relayed-From-Added: Yes
X-Virus-Scanned: by amavisd-new at exmf017-2.msoutlookonline.net
X-Spam-Flag: NO
X-Spam-Score: 0.5
X-Spam-Level:
X-Spam-Status: No, score=0.5 tagged_above=-999 required=3
	tests=[BOTNET_BADHELO=0.2, IMEDIA_NO_MX=0.1, IM_CAPS_IN_SUBJ=0.2]
Received: from exmf017-2.msoutlookonline.net ([127.0.0.1])	by localhost
 (exmf017-2.msoutlookonline.net [127.0.0.1]) (amavisd-new, port 10024)	with
 ESMTP id o7DTH3qin80t for <[email protected]>;	Wed,  4 Nov 2015
 10:50:40 -0800 (PST)
Received: from monitoring.website.com (monitoring.website.net
 [107.21.36.200])	by smtp.exch017.serverdata.net (Postfix) with ESMTP id
 604C530164	for <[email protected]>; Wed,  4 Nov 2015 10:50:40
 -0800 (PST)
Received: by monitoring.website.com (Postfix, from userid 107)	id
 DEDEC22DB3; Wed,  4 Nov 2015 12:50:39 -0600 (CST)
To: <[email protected]>
Subject: ** WSA PROBLEM Service Alert: weblinux01/Free memory is WARNING **
Message-ID: <[email protected]>
Date: Wed, 4 Nov 2015 12:50:39 -0600
From: <[email protected]>
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=WJ6CJSYR c=1 sm=1 tr=0 b=1
	a=ps2rPcza5N6F7vEsS7MxdQ==:117 a=ps2rPcza5N6F7vEsS7MxdQ==:17
	a=DPbXpQ_RAAAA:8 a=qnpTazg9AAAA:8 a=f6XlUauWAAAA:8 a=qtqOOiqGOCEA:10
	a=H-uYOeM-iCqAP6-iff4A:9 a=QWUkoNXfh58A:10
MIME-Version: 1.0
Content-Type: text/plain
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=I8iYP4Ug c=1 sm=1 tr=0
	a=liT8C2TSeTmK6A9xjbZqWg==:117 a=ps2rPcza5N6F7vEsS7MxdQ==:17
	a=dIi01Yb0AAAA:8 a=qnpTazg9AAAA:8 a=DPbXpQ_RAAAA:8 a=f6XlUauWAAAA:8
	a=l78G-EriAAAA:8 a=qtqOOiqGOCEA:10 a=H-uYOeM-iCqAP6-iff4A:9
	a=QWUkoNXfh58A:10
Resent-Message-Id: <[email protected]>
Resent-Date: Wed,  4 Nov 2015 10:50:41 -0800 (PST)

***** Nagios *****

Notification Type: PROBLEM

Service: Free memory
Host: weblinux01
Address: 10.0.1.30
State: WARNING

Date/Time: Wed Nov 4 12:50:39 CST 2015

Additional Info:

WARNING: 91% Used Memory
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: contacts.cfg is not working properly

Post by hsmith »

At this point, Nagios is working. I can't completely reconfigure your Postfix for you. Since it was working when you switched email addresses, you need to figure out where alerts911 is getting stopped. It looks like your email is going through multiple servers? At this point you're going to need to look through the mail logs on each one of those servers and figure out why this is happening. I think @rkennedy hit it on the head about '911' getting filtered, as it could be in a list of spam words.
Former Nagios Employee.
me.
sinkak
Posts: 158
Joined: Thu Jul 30, 2015 1:30 pm

Re: contacts.cfg is not working properly

Post by sinkak »

i checked with IT guy. They dont have any filters on alerts911 email.
sinkak
Posts: 158
Joined: Thu Jul 30, 2015 1:30 pm

Re: contacts.cfg is not working properly

Post by sinkak »

these are from syslog. is there anything out of ordinary

Code: Select all

Nov  4 19:53:32 nagios-2015 nagios: wproc: SERVICE PERFDATA job 22560 from worker Core Worker 14426 is a non-check helper but exited with return code 2
Nov  4 19:53:32 nagios-2015 nagios: wproc:   early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
Nov  4 19:53:32 nagios-2015 nagios: wproc:   stderr line 01: Can't open perl script "/usr/lib/pnp4nagios/libexec/process_perfdata.pl": No such file or directory
Nov  4 19:53:32 nagios-2015 nagios: Worker 14426: Unknown jobtype: 10
Nov  4 19:53:32 nagios-2015 nagios: wproc: Unknown job type: 10
Nov  4 19:53:32 nagios-2015 nagios: wproc: SERVICE PERFDATA job 22560 from worker Core Worker 14424 is a non-check helper but exited with return code 2
Nov  4 19:53:32 nagios-2015 nagios: wproc:   early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
Nov  4 19:53:32 nagios-2015 nagios: wproc:   stderr line 01: Can't open perl script "/usr/lib/pnp4nagios/libexec/process_perfdata.pl": No such file or directory
Nov  4 19:53:32 nagios-2015 nagios: Worker 14424: Unknown jobtype: 10
Nov  4 19:53:32 nagios-2015 nagios: wproc: Unknown job type: 10
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: contacts.cfg is not working properly

Post by hsmith »

If you use the warnings email address to get critical alerts - you receive them. = Critical alerts are working.
If you use the critical email address to get critical emails - you do not receive them. We proved earlier that critical alerts are indeed working.

If your email for "911alerts" is hosted off site, they may not have any control over the filters and what get dropped. I would look into modifying your main.cf.

Some things you should think about:

Some email provides drop spoofed email. If you are sending emails from "[email protected]", and the remote email server does a reverse DNS lookup, and sees that it is coming from an IP address other than the one associated with "examplesite1.com", it may get dropped.

The word 911 may be getting filtered by something external. Without knowing your exact email configuration, such as who is hosting it, it's hard to tell what is going on.

If warnings alerts-warning and 911alerts are on the same email provider, it would be a good clue that the string "911" is getting filtered out. You may want to try an email address without "911" in it.
Former Nagios Employee.
me.
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: contacts.cfg is not working properly

Post by hsmith »

sinkak wrote:these are from syslog. is there anything out of ordinary
Nothing that should have to do with email, no.
Former Nagios Employee.
me.
sinkak
Posts: 158
Joined: Thu Jul 30, 2015 1:30 pm

Re: contacts.cfg is not working properly

Post by sinkak »

hsmith wrote: If warnings alerts-warning and 911alerts are on the same email provider, it would be a good clue that the string "911" is getting filtered out. You may want to try an email address without "911" in it.
Just an additional info.
alerts911 email is working from amazon web services monitoring system. we keep getting alerts to alerts911 email from AWS
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: contacts.cfg is not working properly

Post by hsmith »

sinkak wrote:Just an additional info.
alerts911 email is working from amazon web services monitoring system. we keep getting alerts to alerts911 email from AWS
That's not related to what is happening here. The AWS system could be doing something completely different to send their emails, and coming from a proper FQDN.
Former Nagios Employee.
me.
Locked