Re: Monit is not notifying me of PID changes

Hello, the PID and PPID change tests are no longer implicit from Monit 5.11.0, changelog excerpt: --8<-- New: The PID and PPID change tests are no longer implicit. If you want to test the process PID/PPID changes, you have to add this test explicitly: if changed pid then alert if

Re: monit alert mail message id issue

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.

Monit is not notifying me of PID changes

Hello, I have monit 5.16 installed in Ubuntu 16.04 and I am not getting alerts of PID changes. I get alerts of other monit events without any problems. My alerts are configured in monitrc as follows: set alert hidden@hidden.hidden NOT ON { fsflags } My services config files looks like this:

Re: monit alert mail message id issue

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 : Hi Viktor, yes I know

Re: monit alert mail message id issue

Try reporting it on Bitbucket: https://bitbucket.org/tildeslash/monit/issues/new Idézem/Quoting Eric Pailleau : 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 

Re: monit alert mail message id issue

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

Re: monit alert mail message id issue

message-id=<150833356...@mydomain.net> It seems to be a timestamp based ID which it not precise enough for your case. Idézem/Quoting Eric Pailleau : Hello, forgot to mention that we use (quiet old ?) monit 5.2.3 but why change something running like a charm ;) ? Le

Re: monit alert mail message id issue

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

monit alert mail message id issue

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

Re: monit alert -- Status failed network_resolv

Monit doesn't support such fallback currently, you can implement this in the exec action script (it would require the script to always exist). Best regards, Martin > On 18 Oct 2017, at 11:02, Shakil Shaikh wrote: > > Hi Martin, > > Like the OP I am getting an email as

Re: monit alert -- Status failed network_resolv

Hi Martin, Like the OP I am getting an email as well as the script action (which I now understand is as designed). Is it possible to set up email as a backup/monit error alert? Usage: I want to suppress emails in lieu of scripts, but if monit fails in executing (script path is not available

Re: monit alert -- Status failed network_resolv

Hello Viktor, the 'alert' action is implicit, the alert is send too even if you have 'exec' action => you can simplify the configuration: original: if status != 0 then alert if status != 0 then exec "/usr/local/sbin/monit-slack.sh 'https://hooks.slack.com/services...'" simplified (exec

Re: monit alert -- Status failed network_resolv

Idézem/Quoting Juergen Nickelsen : On 2017-10-17, at 23:13, SZÉPE Viktor wrote: I may seem a rookie but why am I getting an email on the execution of a Slack script? check program network_resolv with path "/usr/local/sbin/server-integrity.sh -c RES -r