How about something like this…
check program server-status with path /usr/local/bin/state.sh
every “5 * * * *"
if status = x then exec /usr/bin/bash -c "/usr/local/bin/foo.sh (x)”
if status = y then exec /usr/bin/bash -c "/usr/local/bin/foo.sh (y)"
‘state.sh” determines
While not an RPM, the simplest approach for us with CentOS was to use the
binary. We use a snippet like this in our Docker CentOS 7 containers:
MONIT_VERSION=5.15
# Add Monit binary
mkdir -p /tmp/monit
cd /tmp/monit
wget
Happy to give it a try too. Thanks for doing this.
--
Thomas Spicer
https://www.linkedin.com/in/thomasspicer
Openbridge, Inc.
www.openbridge.com
https://twitter.com/openbridgeinc
https://github.com/openbridge
On January 18, 2016 at 10:03:02 AM, ad...@extremeshok.com
(ad...@extremeshok.com
Martin,
Can you point me to specific configuration/setup examples for Monit / Docker?
While we can get inbound events to flow into M/Monit connecting back to the
Monit agent has presented a challenge. We are happy to read through anything
that describes this
set httpd
unixsocket
to both of them (using multiple set
mmonit statements), so it will work like a mirror.
Best regards,
Martin
On 03 Apr 2015, at 15:31, Thomas Spicer tho...@openbridge.com wrote:
Greetings,
We are currently doing a test deployment of M/Monit 3.4.1 and Monit 5.13.
In what conditions
Greetings,
We are currently doing a test deployment of M/Monit 3.4.1 and Monit 5.13.
In what conditions would HTTP 408 Request Timeout” appear in the M/Monit log?
For example:
2015-04-03 13:21:04 [client 10.0.0.222] HTTP 408 Request Timeout
2015-04-03 13:21:09 [client 10.0.0.222] HTTP 408
