Hi all,
Le 04/05/2016 23:01, Cyril Bonté a écrit :
I could reproduce the issue, it happens when the whole data can't fit in
the trash buffer.
Usually, haproxy detects that the buffer is full and sends its content
to the client, then restarts from where it stopped. But some commands
were not impl
Hi James and Baptist,
Le 04/05/2016 21:21, James Brown a écrit :
(gentle bump)
On Mon, Apr 25, 2016 at 11:36 AM, James Brown wrote:
Here's the top of the file. None of the backends override the
load-server-state-from-file setting that's made in `defaults`. There
are 106 backends defined.
On
(gentle bump)
On Mon, Apr 25, 2016 at 11:36 AM, James Brown wrote:
> Here's the top of the file. None of the backends override the
> load-server-state-from-file setting that's made in `defaults`. There
> are 106 backends defined.
>
>
> global
> log ${LOG_DGRAM_SYSLOG} local0
> log /var/ru
Here's the top of the file. None of the backends override the
load-server-state-from-file setting that's made in `defaults`. There
are 106 backends defined.
global
log ${LOG_DGRAM_SYSLOG} local0
log /var/run/epservices/syslog_bridge.sock local0
daemon
maxconn 4096
stats socket
On Thu, Apr 21, 2016 at 2:54 AM, James Brown wrote:
> I'm trying to set up state-file saving on 1.6.4, but "show servers state"
> doesn't return anything. It works fine if I specify an individual backend
> (e.g., "show servers state foo_be"), but not if I run it "bare" (which the
> manual suggests
I'm trying to set up state-file saving on 1.6.4, but "show servers state"
doesn't return anything. It works fine if I specify an individual backend
(e.g., "show servers state foo_be"), but not if I run it "bare" (which the
manual suggests should print out states for all backends).
Any thoughts?
-
6 matches
Mail list logo
