[Top][All Lists]

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

RE: Monit and laptops

From: Tomich,John
Subject: RE: Monit and laptops
Date: Thu, 8 Oct 2020 15:17:37 +0000

If you just stop the artifact, won't a process reboot activate it again?  
Safer to uninstall, or at least untarget.

If you are not the intended recipient of this message (including attachments) 
or if you have received this message in error, immediately notify us and delete 
it and any attachments.

If you do not wish to receive any email messages from Edward Jones, excluding 
administrative communications, please email this request to from the email address you wish to unsubscribe.

For important additional information related to this email, visit Edward D. Jones & Co., L.P. 
d/b/a Edward Jones, 12555 Manchester Road, St. Louis, MO 63131 © Edward Jones. 
All rights reserved.

-----Original Message-----
From: monit-general 
<> On Behalf Of 
Lutz Mader
Sent: Wednesday, October 7, 2020 1:59 PM
To: This is the general mailing list for monit <>
Subject: Re: Monit and laptops

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hello David,
I use monit on a Macbook, this works well.

> It seems like Monit would do just fine with a config that said “ping this 
> address and if you have N failures in time T (or cycles), cycle the 
> interface”. My only concern is how it might handle situations when the laptop 
> sleeps or partially sleeps (or wakes up and doesn’t have wifi for a bit). I 
> don’t think I’d want it to be flapping things in those cases.

But you are right, a wake-up or a switch to a other wlan is a problem.

I configure monitrc to use the Macbook hostname to bind to.

use address macbook.local

And monit monitor themselves, to bind to an interface after the wake-up.

check host Monit with address macbookpro.local
  start program "/usr/local/bin/monit reload"
  if failed port 2812 with protocol https username "guest" password "guest"
     and request "/_ping" with status >= 200
     with ssl options {verify: disable, selfsigned: allow}
     with timeout 30 seconds for 3 cycles then start #  if failed port 2812 
with timeout 30 seconds for 3 cycles then start
#     else if recovered then alert
  if 3 restarts within 10 cycles then unmonitor

With regards,

reply via email to

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