Nagios email alerts.

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.
Knack
Posts: 17
Joined: Tue Jan 16, 2018 12:21 pm

Re: Nagios email alerts.

Post by Knack »

Hi

No, i still not receive emails notifications.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Nagios email alerts.

Post by scottwilkerson »

according to this log lines it was accepted for delivery to [email protected]
Knack wrote:

Code: Select all

Feb 21 23:59:41 in-nagios postfix/pickup[8756]: 82CF8C07AAE3: uid=1000 from=<nagios>
Feb 21 23:59:41 in-nagios postfix/cleanup[25022]: 82CF8C07AAE3: message-id=<[email protected]>
Feb 21 23:59:41 in-nagios postfix/qmgr[30807]: 82CF8C07AAE3: from=<[email protected]>, size=692, nrcpt=1 (queue active)
Feb 21 23:59:43 in-nagios postfix/smtp[25026]: connect to aspmx.l.google.com[2404:6800:4003:c03::1a]:25: Network is unreachable
Feb 21 23:59:44 in-nagios postfix/smtp[25026]: 82CF8C07AAE3: to=<[email protected]>, relay=aspmx.l.google.com[74.125.24.26]:25, delay=3.2, delays=0.11/0.01/2.2/0.83, dsn=2.0.0, status=sent (250 2.0.0 OK 1519237784 4-v6si12439603plc.92 - gsmtp)
Feb 21 23:59:44 in-nagios postfix/qmgr[30807]: 82CF8C07AAE3: removed
Feb 21 23:59:56 in-nagios postfix/pickup[8756]: 8D4B7C07AAE3: uid=1000 from=<nagios>
Feb 21 23:59:56 in-nagios postfix/cleanup[25022]: 8D4B7C07AAE3: message-id=<[email protected]>
Feb 21 23:59:56 in-nagios postfix/qmgr[30807]: 8D4B7C07AAE3: from=<[email protected]>, size=691, nrcpt=1 (queue active)
Feb 21 23:59:57 in-nagios postfix/smtp[25026]: 8D4B7C07AAE3: to=<[email protected]>, relay=aspmx.l.google.com[74.125.24.26]:25, delay=1.2, delays=0.05/0/0.62/0.56, dsn=2.0.0, status=sent (250 2.0.0 OK 1519237797 g8-v6si1897205plt.687 - gsmtp)
Feb 21 23:59:57 in-nagios postfix/qmgr[30807]: 8D4B7C07AAE3: removed
Feb 22 00:13:11 in-nagios postfix/pickup[8756]: 84D15C07AAE3: uid=1000 from=<nagios>
Feb 22 00:13:11 in-nagios postfix/cleanup[7158]: 84D15C07AAE3: message-id=<[email protected]>
Feb 22 00:13:11 in-nagios postfix/qmgr[30807]: 84D15C07AAE3: from=<[email protected]>, size=692, nrcpt=1 (queue active)
Feb 22 00:13:12 in-nagios postfix/smtp[7160]: connect to aspmx.l.google.com[2404:6800:4003:c03::1b]:25: Network is unreachable
Feb 22 00:13:13 in-nagios postfix/smtp[7160]: 84D15C07AAE3: to=<[email protected]>, relay=aspmx.l.google.com[74.125.200.26]:25, delay=2.4, delays=0.07/0.01/1.6/0.76, dsn=2.0.0, status=sent (250 2.0.0 OK 1519238593 x1si264315pgv.124 - gsmtp)
Feb 22 00:13:13 in-nagios postfix/qmgr[30807]: 84D15C07AAE3: removed
Feb 22 00:13:21 in-nagios postfix/pickup[8756]: 99AB2C07AAE3: uid=1000 from=<nagios>
Feb 22 00:13:21 in-nagios postfix/cleanup[7158]: 99AB2C07AAE3: message-id=<[email protected]>
Feb 22 00:13:21 in-nagios postfix/qmgr[30807]: 99AB2C07AAE3: from=<[email protected]>, size=691, nrcpt=1 (queue active)
Feb 22 00:13:22 in-nagios postfix/smtp[7160]: 99AB2C07AAE3: to=<[email protected]>, relay=aspmx.l.google.com[74.125.200.26]:25, delay=1.3, delays=0.07/0/0.59/0.59, dsn=2.0.0, status=sent (250 2.0.0 OK 1519238602 j76si31174pfj.146 - gsmtp)
Feb 22 00:13:22 in-nagios postfix/qmgr[30807]: 99AB2C07AAE3: removed
Feb 22 00:45:01 in-nagios postfix/pickup[8756]: 459E8C07AAE3: uid=1000 from=<nagios>
Feb 22 00:45:01 in-nagios postfix/cleanup[8866]: 459E8C07AAE3: message-id=<[email protected]>
Feb 22 00:45:01 in-nagios postfix/qmgr[30807]: 459E8C07AAE3: from=<[email protected]>, size=692, nrcpt=1 (queue active)
Feb 22 00:45:03 in-nagios postfix/smtp[8872]: 459E8C07AAE3: to=<[email protected]>, relay=aspmx.l.google.com[74.125.24.27]:25, delay=2.5, delays=0.05/0/1.6/0.83, dsn=2.0.0, status=sent (250 2.0.0 OK 1519240503 72-v6si3095965ple.299 - gsmtp)
Feb 22 00:45:03 in-nagios postfix/qmgr[30807]: 459E8C07AAE3: removed
Feb 22 00:45:30 in-nagios postfix/pickup[8756]: 44945C07AAE3: uid=1000 from=<nagios>
Feb 22 00:45:30 in-nagios postfix/cleanup[8866]: 44945C07AAE3: message-id=<[email protected]>
Feb 22 00:45:30 in-nagios postfix/qmgr[30807]: 44945C07AAE3: from=<[email protected]>, size=696, nrcpt=1 (queue active)
Feb 22 00:45:31 in-nagios postfix/smtp[8872]: 44945C07AAE3: to=<[email protected]>, relay=aspmx.l.google.com[74.125.24.27]:25, delay=1.3, delays=0.06/0/0.63/0.56, dsn=2.0.0, status=sent (250 2.0.0 OK 1519240531 w24-v6si7752487pll.479 - gsmtp)
If you aren't receiving these messages, I would check your spam filter, or ultimately contact google.com as they run the server that accepted the messages with 250 2.0.0 OK
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Knack
Posts: 17
Joined: Tue Jan 16, 2018 12:21 pm

Re: Nagios email alerts.

Post by Knack »

yes, it seems perfect. but where the emails stuck. spam folder also empty.

How can i check this (contact google.com as they run the server that accepted the messages with 250 2.0.0 OK)
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Nagios email alerts.

Post by scottwilkerson »

being your domain email is hosted at google I'm guessing you have G-Suite

https://gsuite.google.com/support/
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Knack
Posts: 17
Joined: Tue Jan 16, 2018 12:21 pm

Re: Nagios email alerts.

Post by Knack »

its working when i change my local lan ip to another ISP.

Thanks for your all replies.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Nagios email alerts.

Post by scottwilkerson »

glad it's working!
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked