ld be sent
> with this error.
>
> Or would this require a separate "file" check?
>
> Thank you,
>
> Shak
>
> From: monit-general on
> behalf of mart...@tildeslash.com
> Sent: 18 October 2017 08:25
> To: This is the general mailing list for
ubject: 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 "
in/monit-slack.sh
> 'https://hooks.slack.com/services...'"
>
> All sources are available on GitHub:
> https://github.com/szepeviktor/debian-server-tools/tree/master/monitoring/monit
>
> I've received a separate email with "Action: alert"
> Pl
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 '3'"
every 33 cycles
group int
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 '3'" every 33
> cycles
> group integrity
> if status != 0 th
ease advise.
Thank you.
- Forwarded message from r...@example.com -
Date: Tue, 17 Oct 2017 21:04:31 GMT
From: r...@example.com
Subject: monit alert -- Status failed network_resolv
To: ad...@szepe.net
Status failed Service network_resolv
Date:Tue, 17 O
