Hi.
Am 18-02-2016 15:22, schrieb Willy Tarreau:
Hi Aleks,
On Thu, Feb 18, 2016 at 02:53:29PM +0100, Aleksandar Lazic wrote:
[snipp]
For openshift I will try to use 2 container in 1 pod.
If there any interests I can write here if this works ;-)
Sure, please report anyway.
You can find m
Hi Bryan.
Am 18-02-2016 21:18, schrieb Bryan Talbot:
Sorry I'm a bit late to this party but when running in a container it's
also easy to configure haproxy to log to a unix socket and bind mount
that socket to the host.
in haproxy.cnf
log /dev/log local2
Then when launching the container an
Sorry I'm a bit late to this party but when running in a container it's
also easy to configure haproxy to log to a unix socket and bind mount that
socket to the host.
in haproxy.cnf
log /dev/log local2
Then when launching the container an option like "-v /var/log:/var/log"
works quite well to g
Hi Aleks,
On Thu, Feb 18, 2016 at 02:53:29PM +0100, Aleksandar Lazic wrote:
> But this moves just the stdout handling to other tools and does not
> solve the problem with blocking handling of std*, as far as I have
> understood right.
Yes it does because if the logging daemon blocks, logs are s
On 02/18/2016 07:53 AM, Aleksandar Lazic wrote:
Thanks for answers and suggestions.
But this moves just the stdout handling to other tools and does not
solve the problem with blocking handling of std*, as far as I have
understood right.
haproxy will not block. If your logging system hangs
Aleksandar,
Shouldn’t your setup allow for one central syslog type container that collects
all logs sent to it from the network? I think it beats solutions that will
handle the write to file after HAProxy and it certainly respects the one
process per container best practice.
Pedro.
> On 18
Hi.
Am 18-02-2016 11:47, schrieb Conrad Hoffmann:
Two more cents from my side:
socklog [1] also works pretty well...
[1] http://smarden.org/socklog/
Conrad
On 02/18/2016 11:28 AM, Baptiste wrote:
On Thu, Feb 18, 2016 at 10:57 AM, Willy Tarreau wrote:
Hi Aleks,
On Wed, Feb 17, 2016 at 04:
On Thu, Feb 18, 2016 at 11:47:03AM +0100, Conrad Hoffmann wrote:
> Two more cents from my side:
>
> socklog [1] also works pretty well...
>
> [1] http://smarden.org/socklog/
Thanks for the links guys. These should probably be added to the
management doc so that people find them more easily.
wil
Two more cents from my side:
socklog [1] also works pretty well...
[1] http://smarden.org/socklog/
Conrad
On 02/18/2016 11:28 AM, Baptiste wrote:
> On Thu, Feb 18, 2016 at 10:57 AM, Willy Tarreau wrote:
>> Hi Aleks,
>>
>> On Wed, Feb 17, 2016 at 04:30:06PM +0100, Aleksandar Lazic wrote:
>>> Hi
On Thu, Feb 18, 2016 at 10:57 AM, Willy Tarreau wrote:
> Hi Aleks,
>
> On Wed, Feb 17, 2016 at 04:30:06PM +0100, Aleksandar Lazic wrote:
>> Hi.
>>
>> how difficult is it to be able to add "log stdout;" to haproxy?
>>
>> I ask because in some PaaS environment is it difficult to setup a
>> dedicated
Hi Aleks,
On Wed, Feb 17, 2016 at 04:30:06PM +0100, Aleksandar Lazic wrote:
> Hi.
>
> how difficult is it to be able to add "log stdout;" to haproxy?
>
> I ask because in some PaaS environment is it difficult to setup a
> dedicated user yust for haproxy.
>
> It fits also a little bit better to
Hi.
how difficult is it to be able to add "log stdout;" to haproxy?
I ask because in some PaaS environment is it difficult to setup a
dedicated user yust for haproxy.
It fits also a little bit better to http://12factor.net/logs
BR Aleks
12 matches
Mail list logo
