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
Thank you for looking into it.
The bug is triggered by running haproxy with the following config:
Ah yes, I also added the following "init-addr none" statement on the
This prevents HAProxy from using libc resolvers, which might end up in
unpredictible behavior in that enviroment
On Tue, Jul 3, 2018 at 3:18 PM, Baptiste wrote:
> Well, I can partially
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
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
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.
I think I have something running...
At least, terraform did not complain and I can see "stuff" in my AWS
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.
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
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?
- conf v1, server port is X
- generate server
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?
On Mon, Jun
Mail list logo