monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: monit alert mail message id issue


From: Eric Pailleau
Subject: Re: monit alert mail message id issue
Date: Thu, 19 Oct 2017 09:30:03 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

Thanks !


Le 18/10/2017 à 22:52, address@hidden a écrit :
Hi,

the problem was fixed in Monit 5.2.4, changelog excerpt:

--8<--
* Randomize the mail message id to prevent duplicates in the case, that
  the same hostname is used on multiple hosts running monit and messages
  are generated in the same second in parallel. Thanks to Sergey B
  Kirpichev.
--8<--

Best regards,
Martin


On 18 Oct 2017, at 16:43, Eric Pailleau <address@hidden> wrote:

Hi,
yes I will do if I got confirmation this is a monit issue for monit guys.
thanks.


Le 18/10/2017 à 16:35, SZÉPE Viktor a écrit :
Try reporting it on Bitbucket: 
https://bitbucket.org/tildeslash/monit/issues/new 


Idézem/Quoting Eric Pailleau <address@hidden>: 

Hi Viktor, 
yes I know this.  but I wonder if this message id is forged by monit or not. 
If monit create this id , this need more entropy. 
1508333561.0  1508333561.1 etc...  in same second, at least. 

monit guys may know if this issue is solved in upper version or not, too. 
regards 


Le 18/10/2017 à 16:17, SZÉPE Viktor a écrit : 
message-id=<address@hidden> 
It seems to be a timestamp based ID which it not precise enough for your case. 


Idézem/Quoting Eric Pailleau <address@hidden>: 

Hello, 
forgot to mention that we use (quiet old ?) monit 5.2.3 
but why change something running like a charm ;) ? 


Le 18/10/2017 à 15:46, Eric Pailleau a écrit : 
Hello, 

I encountered a monit alert mail issue. 

I use simple config : 

check file no_acks with path /path/to/no_acks.log 
        if match ".*" then alert 

So that monit effetively send a mail at each entry in this log. 
So far so good. 

But since we changed mail architecture, we did not received all the mails, 
but, by investigating , only the first one of all in the same second (using monit.log timestamp reference) 

We could find that imapd/cyrus  removed duplicate message ids and could add a special config entry disabling this option. 

Indeed we could see in postfix/smtpd that all the mails was relayed, but all in the same second add same ID : 
example : 
Oct 18 15:32:41 sv1 postfix/cleanup[31715]: 9AE25A87C51: message-id=<address@hidden> 
Oct 18 15:32:41 sv1 postfix/cleanup[31715]: A59FDA87C3D: message-id=<address@hidden> 

It is not clear to me if this is a monit or postfix issue. Is this mail id set by monit or postfix ? 

Thanks for sharing any thoughts on this. 

Regards 
Eric 



-- 


SZÉPE Viktor, honlap üzemeltetés 
https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md 

-- 


SZÉPE Viktor, honlap üzemeltetés 
https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md 

-- 
<Signature-EP.jpg>
-- 
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general



--

reply via email to

[Prev in Thread] Current Thread [Next in Thread]