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. On Tue, Jul 3, 2018 at 1:06 PM, Baptiste <[email protected]> wrote: > 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. > > Baptiste > > > > On Tue, Jul 3, 2018 at 11:39 AM, Baptiste <[email protected]> wrote: > >> 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 repo to help me speed up in that step). >> >> Baptiste >> >> >> >> >> On Mon, Jun 25, 2018 at 10:54 PM, Jim Deville <[email protected]> >> wrote: >> >>> Hi Bapiste, >>> >>> >>> I just wanted to follow up to see if you were able to repro and perhaps >>> had a patch we could try? >>> >>> >>> Jim >>> ------------------------------ >>> *From:* Jim Deville >>> *Sent:* Thursday, June 21, 2018 1:05:49 PM >>> *To:* Baptiste >>> *Cc:* [email protected]; Jonathan Works >>> *Subject:* Re: Issue with parsing DNS from AWS >>> >>> >>> Thanks for the reply, we were able to extract a minimal repro to >>> demonstrate the problem: https://github.com/jg >>> works/haproxy-servicediscovery >>> >>> >>> The docker folder contains a version of the config we're using and a >>> startup script to determine the local private DNS zone (AWS puts it at the >>> subnet's +2). >>> >>> >>> Jim >>> ------------------------------ >>> *From:* Baptiste <[email protected]> >>> *Sent:* Thursday, June 21, 2018 11:02:26 AM >>> *To:* Jim Deville >>> *Cc:* [email protected]; Jonathan Works >>> *Subject:* Re: Issue with parsing DNS from AWS >>> >>> and by the way, I had a quick look at the pcap file and could not find >>> anything weird. >>> The function you're pointing seem to say there is not enough space to >>> store a server's dns name, but the allocated space is larger that your >>> current records. >>> >>> Baptiste >>> >> >> >
