timeout queue broken since f6e6dc1

Just ran across an issue where the `timeout queue` option is non-functional. I can send a request to haproxy which sits in the queue for well past the configured limit. It appears the issue popped up as a result of this commit: commit f6e6dc12cd533b2d8bb6413a4b5f875ddfd3e6e3 (refs/bisect/bad)

haproxy requests hanging since b0bdae7

It seems that commit b0bdae7 has completely broken haproxy for me. When I send a request to haproxy, it just sits there. The backend server receives nothing, and the client waits for a response. Running with debug enabled I see just a single line: :f1.accept(0004)=0005 from

Re: HAProxy - Server Timeout and Client Timeout

HI Michael We often see the client/server timeouts requiring to be raised as you have found, A good default value for client/server timeouts are below and I include the connect timeout too in milliseconds timeout connect 4000 timeout client 42000 timeout server 43000 Say for example you run a

HAProxy - Server Timeout and Client Timeout

Greetings! We're running HAproxy 1.5.18 on RedHat Enterprise 7.4, as the load balancer for our LMS (Moodle). We have found that the course backup feature in Moodle will return a 5xx error on some backups. We have determined that the "timeout server" value needed to be increased. Initially

stable-bot: NOTICE: 10 bug fixes in queue for next release

Hi, This is a friendly bot that watches fixes pending for the next haproxy-stable release! One such e-mail is sent every week once patches are waiting in the last maintenance branch, and an ideal release date is computed based on the severity of these fixes and their merge date. Responses to

HAProxy 1.8.x not serving errorfiles with H2

We are in the process of testing HAProxy 1.8.x with ALPN and H2 on some of our servers. We have default 502 and 503 errorfiles defined (ex. errorfile 503 /etc/haproxy/errors/503.http), but we've noticed that these errorfiles are not served to the user's browser when the error occurs (for

Re: srv_is_up : unable to find server.

Thanks for replying Im trying to get haproxy to monitor redis-sentinel / redis and see which one redis instance is the master so that traffic is sent there. As originally, per this example https://www.haproxy.com/blog/haproxy-advanced-redis-health-check/ (See the comment January 7, 2018 at

Re: [PATCH]: MINOR :task another explicit cast

On Tue, Jun 05, 2018 at 12:49:34PM +0200, Olivier Houchard wrote: > Oops, thanks a lot David, I hope it'll be the last one :) > > Willy, can you please push it ? Now applied, and after checking the code it looks OK now. Thanks guys, Willy

Re: srv_is_up : unable to find server.

Thanks Jerome I just see this setup goes in line with that you are saying. https://yemaosheng.com/2016/04/haproxy-cfg-for-redis-sentinel/ Thanks so much for replying. Regards Brent On 05/06/2018 13:49, Jerome Magnin wrote: Hi Brent, On Tue, Jun 05, 2018 at 01:18:36PM +0200, Brent Clark

Re: srv_is_up : unable to find server.

Hi Brent, On Tue, Jun 05, 2018 at 01:18:36PM +0200, Brent Clark wrote: > Good day Guys > > I am at a total loss, and Im hoping someone on this list, would be so kind > to review my setup. > > I am trying to get haproxy to monitor redis / sentinel. But I keep getting. > > [WARNING] 155/110602

Re: srv_is_up : unable to find server.

On 5 June 2018 at 13:18, Brent Clark wrote: > Good day Guys > > I am at a total loss, and Im hoping someone on this list, would be so kind > to review my setup. > > I am trying to get haproxy to monitor redis / sentinel. But I keep getting. > > [WARNING] 155/110602 (309) : config : log format

srv_is_up : unable to find server.

Good day Guys I am at a total loss, and Im hoping someone on this list, would be so kind to review my setup. I am trying to get haproxy to monitor redis / sentinel. But I keep getting. [WARNING] 155/110602 (309) : config : log format ignored for frontend 'ft_redis' since it has no log

Re: Dynamically adding/deleting SSL certificates

On Fri, Jun 1, 2018 at 11:13 AM, Aurélien Nephtali wrote: > > We also need to agree on the payload format to use in the add command: > only the PEM certificate is supported at the moment but when there > will be OCSP + SCTL support it will become messy very quick. > In my tests I am using

Re: [PATCH]: MINOR :task another explicit cast

Hi, On Tue, Jun 05, 2018 at 10:46:34AM +, David CARLIER wrote: > Hi, > > Did a full rebuild and caught it only. > > Regards. Oops, thanks a lot David, I hope it'll be the last one :) Willy, can you please push it ? Thanks ! Olivier

[PATCH]: MINOR :task another explicit cast

Hi, Did a full rebuild and caught it only. Regards. From c8cda198a8315d780f11ebf03b44a7d2f686f733 Mon Sep 17 00:00:00 2001 From: David Carlier Date: Tue, 5 Jun 2018 10:41:03 + Subject: [PATCH] MINOR: task: Fix compiler warning. Waking up task, when checking if it is a valid entry.