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 /var/run/m
Regarding the port 2812 issues ... you can use unixsocket as an option to TCP
port for Monit HTTP (added in Monit 5.12 specifically because of Docker
networking specifics).
Regarding the setup - yes, the classic active-passive cluster (hot-cold) is
possible.
Regards,
Martin
> On 03 Apr 2015,
I had not set connectionTimeout so it is using the default. We are narrowing
the issue down to a Docker networking issue. basically, the port (2812) is not
being properly opened which would possibley explain the timeout.
As for the approach…
Within the monitrc config file I would set 2 differe
Hello Thomas,
the request timeout may occur if the client (Monit or GUI client/browser)
didn't complete the HTTP request on time. Default timeout is 30 seconds, you
can modify it in the conf/server.xml file with the "connectionTimeout"
attribute of the element.
Note that the mentioned setup w
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 Req
