Using different sources when connecting to a server

Hello, I'm trying to add a feature which allows HAProxy to use more than one source when connecting to a server of a backend. The main reason is to avoid duplicating the 'server' lines to reach more than 64k connections from HAProxy to one server. So far I thought of two ways: - each time the

new article

Hello there, Your page http://feedjunkie.com/feed/242/10 has some good references to depression and suicide so I wanted to get in touch with you. I've recently written an article about HOW TO HELP THOSE CONSIDERING SUICIDE and was wondering if you thought my article could be a good addition t

Re: haproxy bug: healthcheck not passing after port change when statefile is enabled

Hey Baptiste, Thank you for looking into it. The bug is triggered by running haproxy with the following config: global maxconn 32000 tune.maxrewrite 2048 user haproxy group haproxy daemon chroot /var/lib/haproxy nbproc 1 maxcompcpuusage 85 spread-checks 0

Re: Issue with parsing DNS from AWS

Ah yes, I also added the following "init-addr none" statement on the server-template line. This prevents HAProxy from using libc resolvers, which might end up in unpredictible behavior in that enviroment Baptiste On Tue, Jul 3, 2018 at 3:18 PM, Baptiste wrote: > Well, I can partially reprod

Re: Issue with parsing DNS from AWS

Well, I can partially reproduce the issue you're facing and I can see some weird behavior of AWS's DNS servers. First, by default, HAProxy only support DNS over UDP and can accept up to 512 bytes of payload in the DNS response. DNS over TCP is not yet available and accepted payload size can be inc

Re: Issue with parsing DNS from AWS

Answering myself... I found my way in the menu to be able to allow port 9000 to read the stats page and to find the public IP associated to my "app". That said, I still can't get a shell on the running container, but I think I found an AWS documentation page for this purpose. I keep you updated.

Re: Issue with parsing DNS from AWS

Hi Jim, I think I have something running... At least, terraform did not complain and I can see "stuff" in my AWS dashoard. Now, I have no idea how I can get connected to my running HAProxy container, neither how I can troubleshoot what's happening :) Any help would be (again) appreciated. Baptis

Re: Issue with parsing DNS from AWS

Hi Jim, Sorry for the long pause :) I was dealing with some travel, conferences and catching up on my backlog. So, the good news, is that this issue is now my priority :) I'll try to first reproduce it and come back to you if I have any issue during that step. (by the way, thanks for the github r

Re: haproxy bug: healthcheck not passing after port change when statefile is enabled

Hi Sven, Thanks a lot for your feedback! I'll check how we could handle this use case with the state file. Just to ensure I'm going to troubleshoot the right issue, could you please summarize how you trigger this issue in a few simple steps? IE: - conf v1, server port is X - generate server state

Re: Observations about reloads and DNS SRV records

Hi, Actually, the problem was deeper than my first thought. In its current state, statefile and SRV records are simply not compatible. I had to add a new field in the state file format to add support to this. Could you please confirm the patch attached fixes your issues? Baptiste On Mon, Jun