|
From: | Jorge Bastos |
Subject: | RE: Question about restart/stop |
Date: | Tue, 15 Oct 2013 11:06:12 +0100 |
Martin, I understand you! So far I’m good, thanks! I have one question of a different type. I have a: if failed port 143 protocol imap with timeout 20 seconds within 1 cycles then stop but monit it self stop’s, is this normal?! From: address@hidden [mailto:address@hidden On Behalf Of Martin Pala The "set alert" is necessary - it sets the alert destination. The per-test action (such is "if failed XYZ then alert" or "... restart") dosn't set the alert destination - it just triggers the alert to the email set in "set alert". The base cycle is configured using "set daemon" statement - if you want to check some service less frequently, you can use the "every" statement: check process ABC with pidfile /var/run/ABC.pid every 5 cycles ... I recommend to check Monit manual and configuration examples (the mailing list is not meant as tutorial for basic configuration): On Oct 14, 2013, at 11:17 PM, "Jorge Bastos" <address@hidden> wrote: Well but I defined set alert address@hidden not on {instance, action} Ok I’ll remove it no problem. It’s not possible to have cycle time per daemon, is it? From: address@hidden [mailto:monit-address@hidden] On Behalf Of Martin Pala The "stop" action will send alert too (no need for explicit "stop+alert" action). On Oct 14, 2013, at 11:11 PM, "Jorge Bastos" <address@hidden> wrote: There’s always one last question J Is it possible to have alert and stop in the same statement? Like: if failed port 123 then alert stop is it? From: address@hidden [mailto:monit-address@hidden] On Behalf Of Jorge Bastos Well perfect, didn’t saw it! By default debian has /etc/monit/monitrc.d/ with some scripts, and I thought it was reading it, but no, the default is /etc/monit/conf.d/ Solved, thanks a lot! From: address@hidden [mailto:address@hidden] On Behalf Of Martin Pala Make sure your monit configuration file has "include" statement set for this directory. If you add some include file, you have to reload Monit to load it (CLI: "monit reload"). On Oct 14, 2013, at 10:47 PM, "Jorge Bastos" <address@hidden> wrote: Sorry but another question. I created a script in monitrc.d, but it seems that is not being read, how can I know if the script is really being read ? From: address@hidden [mailto:monit-address@hidden] On Behalf Of Jorge Bastos Thank you J From: address@hidden [mailto:address@hidden] On Behalf Of Martin Pala Hi, yes you can use stop, for example: if failed port 123 then stop Regards, Martin On Oct 14, 2013, at 10:00 PM, "Jorge Bastos" <address@hidden> wrote: Hi guys, I’d like to know, it I can use or its supported, “stop” instead of “restart”, is it? Thanks in advanced, Jorge Bastos, -- -- -- -- |
[Prev in Thread] | Current Thread | [Next in Thread] |