On 4/30/2015 4:08 PM, Cyril Bonté wrote:
No, you didn't provide err as the minlevel argument.
It should be something like :
log 127.0.0.1 local0 notice err
Also, ensure you don't have a log global somewhere in those backends
or in the previously declared defaults section.
I now have a
Le 01/05/2015 21:57, Shawn Heisey a écrit :
On 5/1/2015 12:30 PM, Cyril Bonté wrote:
Message from syslogd@ at Fri May 1 11:29:51 2015 ...
localhost.localdomain haproxy[23754]: backend be-services-dev-8443 has
no server available!
Any other ideas?
Please provide your configuration, I'm quite
On 5/1/2015 12:30 PM, Cyril Bonté wrote:
Message from syslogd@ at Fri May 1 11:29:51 2015 ...
localhost.localdomain haproxy[23754]: backend be-services-dev-8443 has
no server available!
Any other ideas?
Please provide your configuration, I'm quite sure it's a
misconfiguration in it.
I'm
Le 01/05/2015 19:36, Shawn Heisey a écrit :
On 4/30/2015 4:08 PM, Cyril Bonté wrote:
No, you didn't provide err as the minlevel argument.
It should be something like :
log 127.0.0.1 local0 notice err
Also, ensure you don't have a log global somewhere in those backends
or in the previously
I have a number of backend configs that handle requests to dev and
staging webservers. These backend configs only have one server. If
that server goes down briefly because the server process is restarted,
which happens frequently precisely because they are for dev/staging, I
get a console
Hi Shawn,
Le 30/04/2015 21:57, Shawn Heisey a écrit :
One thing that I can do is increase the fall parameter for checks on
the dedicated dev/staging servers, but there's a downside: haproxy won't
notice that a server is down very quickly. I don't mind that haproxy
*logs* the server going down
On 4/30/2015 1:03 PM, Pavlos Parissis wrote:
On 30/04/2015 08:31 μμ, Shawn Heisey wrote:
I definitely DO want this kind of console notification if one of the
production backends has no server available, but I don't want the
interruption for staging or dev. If a config option to reduce the
On 30/04/2015 08:31 μμ, Shawn Heisey wrote:
I have a number of backend configs that handle requests to dev and
staging webservers. These backend configs only have one server. If
that server goes down briefly because the server process is restarted,
which happens frequently precisely because
On 30/04/2015 09:57 μμ, Shawn Heisey wrote:
On 4/30/2015 1:03 PM, Pavlos Parissis wrote:
On 30/04/2015 08:31 μμ, Shawn Heisey wrote:
I definitely DO want this kind of console notification if one of the
production backends has no server available, but I don't want the
interruption for staging
Le 30/04/2015 23:32, Shawn Heisey a écrit :
On 4/30/2015 2:11 PM, Cyril Bonté wrote:
Simply adjust your the log levels in your haproxy configuration for
those backends, by setting the minimum syslog level to error for
example, this will prevent still log the events but won't send them as
On 4/30/2015 2:11 PM, Cyril Bonté wrote:
Simply adjust your the log levels in your haproxy configuration for
those backends, by setting the minimum syslog level to error for
example, this will prevent still log the events but won't send them as
emerg/alert/crit (which I assume one of them is
11 matches
Mail list logo
