Hello,
I see today that libreNMS sends me the email alert 2h after the detection!
e-mail content:
Devices up/down
Severity: critical
Timestamp: 2019-06-20 12:35:04
e-mail date : 2019-06-20 14:40
Why ??
What have you looked at?
Have you tried doing some test email alerts? Have you seen anything in the logs? Are you sure the delay is in Librenms and not with your e-mail server - include reasons why you think that…
It’s hard to troubleshoot when all you have is two timestamps…
No problem with my Postfix mailserver. Alert transport -> Test transport is immediate.
The date in the headers is also incorrect.:
Received: by nms.xxx.net (Postfix, from userid 999)
id AF60828A1F; Thu, 20 Jun 2019 14:40:02 +0200 (CEST)
To: NMS [email protected]
Subject: Alert for device cpe002.xxxxxxxx- Devices up/down
Date: Thu, 20 Jun 2019 12:40:02 +0000
A problem in libreNMS with the timezone ?
I made now a forced upgrade of libreNMS blocked by git.
I receive my Recover immediatly after upgrade.
Probably a bug already fixed…
I have now the current version of LibreNMS.
I make a test:
- I disabled the SNMP of a router
- LibreNMS detect : " 2019-06-20 23:35:16 [Devices up/down] "
- No e-mail generated… (tail -f /var/log/mail.log)
My date is correct:
root@nms:/opt/librenms# date
Fri Jun 21 00:03:22 CEST 2019
and what is your settings for alerting
delay 5 m =
detect at example 01:00:00
Alert will be send at : 01:05:00 (if not recovered )
- u can use debug mode and view log files if its trying someting…
But 2 hrs… looks like timezone settings …
else u can use:
@if ($alert->state == 0) Time elapsed: {{ $alert->elapsed }} @endif
Timestamp: {{ $alert->timestamp }}
So u will see Timestamp of aler (examle) : 01:00:00
and Time Elapsed (Example) your case : 2 hrs and 5 mins … (else if timezones incorrect = 5 mins)