[Top][All Lists]

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

Re: M/Monit: HTTP 408 Request Timeout

From: Martin Pala
Subject: Re: M/Monit: HTTP 408 Request Timeout
Date: Fri, 10 Apr 2015 09:09:42 +0200

I’m sorry Thomas … the hint with unixsocket won’t work if Monit is used with M/Monit as M/Monit uses only TCP to connect to Monit. If Docker shares the same IP for multiple containers, you’ll need to set unique TCP port for each Monit instance in the “set httpd port <xyz>” statement.


On 03 Apr 2015, at 22:40, Thomas Spicer <address@hidden> wrote:


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/monit.sock
    allow user:pass

No port is specified for the socket? When we tried to include port it said “syntax error”. Same for SSL. We removed those for now.

On Apr 3, 2015, at 3:51 PM, Martin Pala <address@hidden> wrote:

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.


To unsubscribe:

reply via email to

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