Alerts/notifications stopped randomly?
Hi All
Im trying to see if anybody else is having this issue
Our Observium has randomly stopped sending alerts
Currently using email/pushover/slack/hipchat and I don’t seem to get any of them!?
Running test_alert -a 1 works without any issues
The alert_tests range from device down to storage low
regards
Simon - Hestor Ltd
Hi,
Has something changed in the alerts php code by any chance?
As just noticed these errors in roots mail on the server
33@observium.xxxxx.com (expanded from <33>): unknown user: “33” 37@observium.xxxxx.com (expanded from <37>): unknown user: “37"
Regards
Simon
On 19 Jun 2017, at 14:51, Simon Mousey Smith simonsmith5521@gmail.com wrote:
Hi All
Im trying to see if anybody else is having this issue
Our Observium has randomly stopped sending alerts
Currently using email/pushover/slack/hipchat and I don’t seem to get any of them!?
Running test_alert -a 1 works without any issues
The alert_tests range from device down to storage low
regards
Simon - Hestor Ltd
As just noticed these errors in roots mail on the server
33@observium.xxxxx.com (expanded from <33>): unknown user: “33” 37@observium.xxxxx.com (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
On 19 Jun 2017, at 16:42, Tim Cooper lists@coop3r.com wrote:
As just noticed these errors in roots mail on the server
33@observium.xxxxx.com (expanded from <33>): unknown user: “33” 37@observium.xxxxx.com (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing
Are they still being generated, or were there just a couple generated on the 15th?
adam. On 19/06/2017 16:48:10, Tim Cooper lists@coop3r.com wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
(expanded from ): unknown user: “33” (expanded from ): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong adama@memetic.org wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam.
On 19/06/2017 16:48:10, Tim Cooper lists@coop3r.com wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
33@observium.xxxxx.com (expanded from <33>): unknown user: “33” 37@observium.xxxxx.com (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
If you run test_alert.php -d for this particular alert, what is its output?
adam. On 19/06/2017 17:10:16, Simon Mousey Smith simonsmith5521@gmail.com wrote: Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam. On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com [mailto:lists@coop3r.com]> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
<33@observium.xxxxx.com [mailto:33@observium.xxxxx.com]> (expanded from <33>): unknown user: “33” <37@observium.xxxxx.com [mailto:37@observium.xxxxx.com]> (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
test_alert -a 1 -d Works fine, I get all notifications via email/slack/hipchat/pushover, no local error message in mutt emails
But if I Stop snmpd on a server, observium then send alerts but they take 5-10mins to cum threw again by all methods, and mutt emails are being shown
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong adama@memetic.org wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam.
On 19/06/2017 17:10:16, Simon Mousey Smith simonsmith5521@gmail.com wrote:
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam.
On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
<33@observium.xxxxx.com mailto:33@observium.xxxxx.com> (expanded from <33>): unknown user: “33” <37@observium.xxxxx.com mailto:37@observium.xxxxx.com> (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System MAILER-DAEMON@observium.xxxxx.com To: root@observium.xxxxx.com Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
56@observium.xxxxx.com (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com Original-Recipient: rfc822;56@observium.xxxxx.com Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium observium@observium.xxxxx.com To: simon@xxxxx.com Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
------------------------------------ ALERT Device Is Down ------------------------------------ Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10) ------------------------------------
------------------------------------ Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m ------------------------------------
E-mail sent to: simon@vvvvv.com E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org http://www.observium.org/
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong adama@memetic.org wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam.
On 19/06/2017 17:10:16, Simon Mousey Smith simonsmith5521@gmail.com wrote:
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam.
On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
<33@observium.xxxxx.com mailto:33@observium.xxxxx.com> (expanded from <33>): unknown user: “33” <37@observium.xxxxx.com mailto:37@observium.xxxxx.com> (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
This is strange, since the correct email is included in the message, and these alerts are working for me.
Are these alerts going to a contact, or to a "default" configured in the config?
adam. On 19/06/2017 17:23:29, Simon Mousey Smith simonsmith5521@gmail.com wrote: Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com [mailto:MAILER-DAEMON@observium.xxxxx.com]> To: root@observium.xxxxx.com [mailto:root@observium.xxxxx.com] Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com [http://observium.xxxxx.com].
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<56@observium.xxxxx.com [mailto:56@observium.xxxxx.com]> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com [http://observium.xxxxx.com] X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com [mailto:root@observium.xxxxx.com] Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com [mailto:56@observium.xxxxx.com] Original-Recipient: rfc822;56@observium.xxxxx.com [http://observium.xxxxx.com] Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com [mailto:observium@observium.xxxxx.com]> To: simon@xxxxx.com [mailto:simon@xxxxx.com] Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
------------------------------------ ALERT Device Is Down ------------------------------------ Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10) ------------------------------------
------------------------------------ Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m ------------------------------------
E-mail sent to: simon@vvvvv.com [mailto:simon@vvvvv.com] E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org [http://www.observium.org]
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam. On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com [mailto:simonsmith5521@gmail.com]> wrote: Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam. On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com [mailto:lists@coop3r.com]> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
<33@observium.xxxxx.com [mailto:33@observium.xxxxx.com]> (expanded from <33>): unknown user: “33” <37@observium.xxxxx.com [mailto:37@observium.xxxxx.com]> (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
You can try putting "print_r($emails);" below the two $emails lines in includes/alerting/email.inc.php and then running test_alert.php.
This might help show what the issue is.
adam. On 19/06/2017 17:30:18, Adam Armstrong adama@memetic.org wrote: Hi,
This is strange, since the correct email is included in the message, and these alerts are working for me.
Are these alerts going to a contact, or to a "default" configured in the config?
adam. On 19/06/2017 17:23:29, Simon Mousey Smith simonsmith5521@gmail.com wrote: Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com [mailto:MAILER-DAEMON@observium.xxxxx.com]> To: root@observium.xxxxx.com [mailto:root@observium.xxxxx.com] Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com [http://observium.xxxxx.com].
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<56@observium.xxxxx.com [mailto:56@observium.xxxxx.com]> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com [http://observium.xxxxx.com] X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com [mailto:root@observium.xxxxx.com] Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com [mailto:56@observium.xxxxx.com] Original-Recipient: rfc822;56@observium.xxxxx.com [http://observium.xxxxx.com] Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com [mailto:observium@observium.xxxxx.com]> To: simon@xxxxx.com [mailto:simon@xxxxx.com] Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
------------------------------------ ALERT Device Is Down ------------------------------------ Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10) ------------------------------------
------------------------------------ Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m ------------------------------------
E-mail sent to: simon@vvvvv.com [mailto:simon@vvvvv.com] E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org [http://www.observium.org]
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam. On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com [mailto:simonsmith5521@gmail.com]> wrote: Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam. On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com [mailto:lists@coop3r.com]> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
<33@observium.xxxxx.com [mailto:33@observium.xxxxx.com]> (expanded from <33>): unknown user: “33” <37@observium.xxxxx.com [mailto:37@observium.xxxxx.com]> (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com
Don't you have some strange mail forwarding rules with a typo in it? What is the user ID of your user (simon@xxxxx.com mailto:simon@xxxxx.com)? Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)
Tylla
On 2017-06-19 18:21, Simon Mousey Smith wrote:
Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com mailto:MAILER-DAEMON@observium.xxxxx.com> To: root@observium.xxxxx.com mailto:root@observium.xxxxx.com Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com http://observium.xxxxx.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system<56@observium.xxxxx.com mailto:56@observium.xxxxx.com> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com http://observium.xxxxx.com X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com mailto:root@observium.xxxxx.com Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com mailto:56@observium.xxxxx.com Original-Recipient: rfc822;56@observium.xxxxx.com http://observium.xxxxx.com Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com mailto:observium@observium.xxxxx.com> To: simon@xxxxx.com mailto:simon@xxxxx.com Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
ALERT Device Is Down
Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10)
Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m
E-mail sent to: simon@vvvvv.com mailto:simon@vvvvv.com E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam.
On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> wrote:
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam.
On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
> > As just noticed these errors in roots mail on the server > > <33@observium.xxxxx.com mailto:33@observium.xxxxx.com>
(expanded from <33>): unknown user: “33”
> <37@observium.xxxxx.com mailto:37@observium.xxxxx.com>
(expanded from <37>): unknown user: “37"
>
I'm seeing these erroneous emails also running r8665. At a rough
guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June
(r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
We also see this same issue. Validated via postfix logs that emails to invalid addresses are actually generated by Observium.
When new alert is triggered Observium sends the email to the actual real designated alert email address, but also generate these emails to invalid addresses, looks like it tries to send email to the device ID #, eg. 119@domain.com where 119 is the Observium device ID for one of our switches.
On 06/19/2017 12:59 PM, Attila Nagy wrote:
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com
Don't you have some strange mail forwarding rules with a typo in it? What is the user ID of your user (simon@xxxxx.com mailto:simon@xxxxx.com)? Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)
Tylla
On 2017-06-19 18:21, Simon Mousey Smith wrote:
Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com mailto:MAILER-DAEMON@observium.xxxxx.com> To: root@observium.xxxxx.com mailto:root@observium.xxxxx.com Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com http://observium.xxxxx.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system<56@observium.xxxxx.com mailto:56@observium.xxxxx.com> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com http://observium.xxxxx.com X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com mailto:root@observium.xxxxx.com Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com mailto:56@observium.xxxxx.com Original-Recipient: rfc822;56@observium.xxxxx.com http://observium.xxxxx.com Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com mailto:observium@observium.xxxxx.com> To: simon@xxxxx.com mailto:simon@xxxxx.com Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
ALERT Device Is Down
Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10)
Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m
E-mail sent to: simon@vvvvv.com mailto:simon@vvvvv.com E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam.
On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> wrote:
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam.
On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote:
> On 19 Jun 2017, at 16:42, Tim Cooper wrote: > > >> >> As just noticed these errors in roots mail on the server >> >> <33@observium.xxxxx.com mailto:33@observium.xxxxx.com> (expanded from <33>): unknown user: “33” >> <37@observium.xxxxx.com mailto:37@observium.xxxxx.com> (expanded from <37>): unknown user: “37" >> > > I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663) > > Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
the server addresses are blanked out for privacy hense the xxxxx.com :)
Any ideas how to debug postfix locally as my outbound email isn't going threw SMTP server
Simon
Sent from my iPhone
On 19 Jun 2017, at 18:59, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com
Don't you have some strange mail forwarding rules with a typo in it? What is the user ID of your user (simon@xxxxx.com)? Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)
Tylla
On 2017-06-19 18:21, Simon Mousey Smith wrote: Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System MAILER-DAEMON@observium.xxxxx.com To: root@observium.xxxxx.com Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system56@observium.xxxxx.com (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com Original-Recipient: rfc822;56@observium.xxxxx.com Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium observium@observium.xxxxx.com To: simon@xxxxx.com Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
ALERT Device Is Down
Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10)
Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m
E-mail sent to: simon@vvvvv.com E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong adama@memetic.org wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam.
On 19/06/2017 17:10:16, Simon Mousey Smith simonsmith5521@gmail.com wrote:
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong adama@memetic.org wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam.
On 19/06/2017 16:48:10, Tim Cooper lists@coop3r.com wrote:
> On 19 Jun 2017, at 16:42, Tim Cooper wrote: > > >> >> As just noticed these errors in roots mail on the server >> >> 33@observium.xxxxx.com (expanded from <33>): unknown user: “33” >> 37@observium.xxxxx.com (expanded from <37>): unknown user: “37" >> > > I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663) > > Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Please to be answering the questions in my previous mails.
adam. On 19/06/2017 19:42:39, Simon Mousey Smith simonsmith5521@gmail.com wrote: the server addresses are blanked out for privacy hense the xxxxx.com [http://xxxxx.com] :)
Any ideas how to debug postfix locally as my outbound email isn't going threw SMTP server
Simon
Sent from my iPhone
On 19 Jun 2017, at 18:59, Attila Nagy <tylla_at_memetic.org@tylla.hu [mailto:tylla_at_memetic.org@tylla.hu]> wrote:
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com [mailto:56@observium.xxxxx.com]
Don't you have some strange mail forwarding rules with a typo in it? What is the user ID of your user (simon@xxxxx.com [mailto:simon@xxxxx.com])? Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)
Tylla
On 2017-06-19 18:21, Simon Mousey Smith wrote:
Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com [mailto:MAILER-DAEMON@observium.xxxxx.com]> To: root@observium.xxxxx.com [mailto:root@observium.xxxxx.com] Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com [http://observium.xxxxx.com].
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<56@observium.xxxxx.com [mailto:56@observium.xxxxx.com]> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com [http://observium.xxxxx.com] X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com [mailto:root@observium.xxxxx.com] Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com [mailto:56@observium.xxxxx.com] Original-Recipient: rfc822;56@observium.xxxxx.com [http://observium.xxxxx.com] Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com [mailto:observium@observium.xxxxx.com]> To: simon@xxxxx.com [mailto:simon@xxxxx.com] Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
------------------------------------ ALERT Device Is Down ------------------------------------ Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10) ------------------------------------
------------------------------------ Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m ------------------------------------
E-mail sent to: simon@vvvvv.com [mailto:simon@vvvvv.com] E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org [http://www.observium.org]
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam. On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com [mailto:simonsmith5521@gmail.com]> wrote: Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
Are they still being generated, or were there just a couple generated on the 15th?
adam. On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com [mailto:lists@coop3r.com]> wrote:
On 19 Jun 2017, at 16:42, Tim Cooper wrote:
As just noticed these errors in roots mail on the server
<33@observium.xxxxx.com [mailto:33@observium.xxxxx.com]> (expanded from <33>): unknown user: “33” <37@observium.xxxxx.com [mailto:37@observium.xxxxx.com]> (expanded from <37>): unknown user: “37"
I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
Also seems Telegram alerts stopped working since 13th June (r8661 ish?)
Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
This issue should be resolved when updating to latest rolling release (17.6.8667).
Tom
On 06/20/2017 12:31 AM, Adam Armstrong wrote:
Please to be answering the questions in my previous mails.
adam.
On 19/06/2017 19:42:39, Simon Mousey Smith simonsmith5521@gmail.com wrote:
the server addresses are blanked out for privacy hense the xxxxx.com http://xxxxx.com :)
Any ideas how to debug postfix locally as my outbound email isn't going threw SMTP server
Simon
Sent from my iPhone
On 19 Jun 2017, at 18:59, Attila Nagy <tylla_at_memetic.org@tylla.hu mailto:tylla_at_memetic.org@tylla.hu> wrote:
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com
Don't you have some strange mail forwarding rules with a typo in it? What is the user ID of your user (simon@xxxxx.com mailto:simon@xxxxx.com)? Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)
Tylla
On 2017-06-19 18:21, Simon Mousey Smith wrote:
Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com mailto:MAILER-DAEMON@observium.xxxxx.com> To: root@observium.xxxxx.com mailto:root@observium.xxxxx.com Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com http://observium.xxxxx.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system<56@observium.xxxxx.com mailto:56@observium.xxxxx.com> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com http://observium.xxxxx.com X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com mailto:root@observium.xxxxx.com Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com mailto:56@observium.xxxxx.com Original-Recipient: rfc822;56@observium.xxxxx.com http://observium.xxxxx.com Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com mailto:observium@observium.xxxxx.com> To: simon@xxxxx.com mailto:simon@xxxxx.com Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
ALERT Device Is Down
Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10)
Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m
E-mail sent to: simon@vvvvv.com mailto:simon@vvvvv.com E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam.
On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> wrote:
Hi,
Im still getting these, generated today too
Had 4 today so far (faulty server, groan)
Simon
> On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org > mailto:adama@memetic.org> wrote: > > Are they still being generated, or were there just a couple > generated on the 15th? > > adam. >> >> On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com >> mailto:lists@coop3r.com> wrote: >> >> >> >> > On 19 Jun 2017, at 16:42, Tim Cooper wrote: >> > >> > >> >> >> >> As just noticed these errors in roots mail on the server >> >> >> >> <33@observium.xxxxx.com mailto:33@observium.xxxxx.com> >> (expanded from <33>): unknown user: “33” >> >> <37@observium.xxxxx.com mailto:37@observium.xxxxx.com> >> (expanded from <37>): unknown user: “37" >> >> >> > >> > I'm seeing these erroneous emails also running r8665. At a >> rough guess it looks like we first started noticing them after >> upgrading on 15th June (r8663) >> > >> > Also seems Telegram alerts stopped working since 13th June >> (r8661 ish?) >> >> Ignore that last bit. Telegram is working fine after all. It's >> just the undeliverable emails we are seeing >> _______________________________________________ >> observium mailing list >> observium@observium.org mailto:observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > _______________________________________________ > observium mailing list > observium@observium.org mailto:observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
No longer getting errors :)
However the notified columns in alert_log re still showing as NO instead of OK
Simon
On 20 Jun 2017, at 09:50, Tom Laermans tom.laermans@powersource.cx wrote:
This issue should be resolved when updating to latest rolling release (17.6.8667). Tom
On 06/20/2017 12:31 AM, Adam Armstrong wrote:
Please to be answering the questions in my previous mails.
adam.
On 19/06/2017 19:42:39, Simon Mousey Smith simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com wrote:
the server addresses are blanked out for privacy hense the xxxxx.com http://xxxxx.com/ :)
Any ideas how to debug postfix locally as my outbound email isn't going threw SMTP server
Simon
Sent from my iPhone
On 19 Jun 2017, at 18:59, Attila Nagy <tylla_at_memetic.org@tylla.hu mailto:tylla_at_memetic.org@tylla.hu> wrote:
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com mailto:56@observium.xxxxx.com
Don't you have some strange mail forwarding rules with a typo in it? What is the user ID of your user (simon@xxxxx.com mailto:simon@xxxxx.com)? Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)
Tylla
On 2017-06-19 18:21, Simon Mousey Smith wrote:
Sample email if helps:
Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST) From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com mailto:MAILER-DAEMON@observium.xxxxx.com> To: root@observium.xxxxx.com mailto:root@observium.xxxxx.com Subject: Undelivered Mail Returned to Sender
[-- Attachment #1: Notification --] [-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
This is the mail system at host observium.xxxxx.com http://observium.xxxxx.com/.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system<56@observium.xxxxx.com mailto:56@observium.xxxxx.com> (expanded from <56>): unknown user: "56"
[-- Attachment #2: Delivery report --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; observium.xxxxx.com http://observium.xxxxx.com/ X-Postfix-Queue-ID: 4AA00200C2B X-Postfix-Sender: rfc822; root@observium.xxxxx.com mailto:root@observium.xxxxx.com Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)
Final-Recipient: rfc822; 56@observium.xxxxx.com mailto:56@observium.xxxxx.com Original-Recipient: rfc822;56@observium.xxxxx.com http://observium.xxxxx.com/ Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "56"
[-- Attachment #3: Undelivered Message --] [-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]
Date: Mon, 19 Jun 2017 15:21:10 +0100 From: Observium <observium@observium.xxxxx.com mailto:observium@observium.xxxxx.com> To: simon@xxxxx.com mailto:simon@xxxxx.com Subject: ALERT: [router.xxxxx] [device] Device Is Down X-Mailer: Observium 17.6.8665
ALERT Device Is Down
Entity: router.xxxxx Conditions: device_status equals 0 (0) Metrics: device_status = 0 Duration: 5m (2017-06-19 15:16:10)
Device: router.xxxxx Hardware: OS: TP-LINK Router Location: xxxxx Uptime: Down 5m
E-mail sent to: simon@vvvvv.com mailto:simon@vvvvv.com E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100
-- Observium Professional 17.6.8665 http://www.observium.org http://www.observium.org/
Regards
Simon
On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
If you run test_alert.php -d for this particular alert, what is its output?
adam. > On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> wrote: > > Hi, > > Im still getting these, generated today too > > Had 4 today so far (faulty server, groan) > > Simon > >> On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote: >> >> Are they still being generated, or were there just a couple generated on the 15th? >> >> adam. >>> On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote: >>> >>> >>> >>> > On 19 Jun 2017, at 16:42, Tim Cooper wrote: >>> > >>> > >>> >> >>> >> As just noticed these errors in roots mail on the server >>> >> >>> >> <33@observium.xxxxx.com mailto:33@observium.xxxxx.com> (expanded from <33>): unknown user: “33” >>> >> <37@observium.xxxxx.com mailto:37@observium.xxxxx.com> (expanded from <37>): unknown user: “37" >>> >> >>> > >>> > I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663) >>> > >>> > Also seems Telegram alerts stopped working since 13th June (r8661 ish?) >>> >>> Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing >>> _______________________________________________ >>> observium mailing list >>> observium@observium.org mailto:observium@observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> _______________________________________________ >> observium mailing list >> observium@observium.org mailto:observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 19 Jun 2017, at 16:57, Adam Armstrong adama@memetic.org wrote:
Are they still being generated, or were there just a couple generated on the 15th?
I'm still seeing these erroneous emails being generated today for new alerts on r8665. Lay was about 45minutes ago.
I feel you're omitting some very useful information...
adam. On 19/06/2017 14:52:11, Simon Mousey Smith simonsmith5521@gmail.com wrote: Hi All
Im trying to see if anybody else is having this issue
Our Observium has randomly stopped sending alerts
Currently using email/pushover/slack/hipchat and I don’t seem to get any of them!?
Running test_alert -a 1 works without any issues
The alert_tests range from device down to storage low
regards
Simon - Hestor Ltd _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Running latest SVN 17.6.8665, from the looks of it it stopped about 3 days ago
What I’ve also spotted is the following:
1. Im getting the notifications threw now, just very late (say 15mins after the event happened)
2. When I look at the alert logging page, the notified columns are shown as NO, yet I get the alerts 15mins later?
Simon
On 19 Jun 2017, at 15:53, Adam Armstrong adama@memetic.org wrote:
I feel you're omitting some very useful information...
adam.
On 19/06/2017 14:52:11, Simon Mousey Smith simonsmith5521@gmail.com wrote:
Hi All
Im trying to see if anybody else is having this issue
Our Observium has randomly stopped sending alerts
Currently using email/pushover/slack/hipchat and I don’t seem to get any of them!?
Running test_alert -a 1 works without any issues
The alert_tests range from device down to storage low
regards
Simon - Hestor Ltd _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (6)
-
Adam Armstrong -
Attila Nagy -
Chris Smith -
Simon Mousey Smith -
Tim Cooper -
Tom Laermans