OK, I will check the points you mentioned. But isn't it interesting that
the second node correctly registers the entry in it's stick table, it's
just that it doesn't get replicated to first node.
PFA my haproxy.cfg using which I can still reproduce the same behaviour as
I stated, I used "socat openssl-listen:8443,fork,reuseaddr,cert=./cert.pem
echo" to spawn a dummy SSL server which correctly gives session IDs. I am
running this same configuration on both the instances.
- Pradeep Jindal
On Mon, Sep 21, 2015 at 11:19 PM, Willy Tarreau <w@1wt.eu> wrote:
> On Mon, Sep 21, 2015 at 11:14:25PM +0530, Pradeep Jindal wrote:
> > Which version (or sha would be better) are you running?
>
> The latest git with the latest crash fix :
>
> HA-Proxy version 1.6-dev5-a68f76-30 2015/09/21
>
> That's 30 patches after dev5, so pretty similar.
>
> > I am running
> > 1.6-dev5 tarball (patched with SRV_ADMF_CMAINT patch & this peers
> segfault
> > patch) downloaded from haproxy.org. Here's my haproxy -vv:
>
> (...)
> OK I consider yours totally equivalent regarding this issue.
>
> We'll need your config. There's no reason for the problem to occur
> in one direction only as the peers protocol is totally symmetric.
> Are you sure the config on the second node works fine and allows
> the track-sc statement to be performed ? Can you check if the second
> node correctly sees its own activity when you connect there directly.
> It would be imaginable that because of a test one line was commented
> out and that only node 1 learns from the traffic. That's just a guess.
>
> Willy
>
>
the second node correctly registers the entry in it's stick table, it's
just that it doesn't get replicated to first node.
PFA my haproxy.cfg using which I can still reproduce the same behaviour as
I stated, I used "socat openssl-listen:8443,fork,reuseaddr,cert=./cert.pem
echo" to spawn a dummy SSL server which correctly gives session IDs. I am
running this same configuration on both the instances.
- Pradeep Jindal
On Mon, Sep 21, 2015 at 11:19 PM, Willy Tarreau <w@1wt.eu> wrote:
> On Mon, Sep 21, 2015 at 11:14:25PM +0530, Pradeep Jindal wrote:
> > Which version (or sha would be better) are you running?
>
> The latest git with the latest crash fix :
>
> HA-Proxy version 1.6-dev5-a68f76-30 2015/09/21
>
> That's 30 patches after dev5, so pretty similar.
>
> > I am running
> > 1.6-dev5 tarball (patched with SRV_ADMF_CMAINT patch & this peers
> segfault
> > patch) downloaded from haproxy.org. Here's my haproxy -vv:
>
> (...)
> OK I consider yours totally equivalent regarding this issue.
>
> We'll need your config. There's no reason for the problem to occur
> in one direction only as the peers protocol is totally symmetric.
> Are you sure the config on the second node works fine and allows
> the track-sc statement to be performed ? Can you check if the second
> node correctly sees its own activity when you connect there directly.
> It would be imaginable that because of a test one line was commented
> out and that only node 1 learns from the traffic. That's just a guess.
>
> Willy
>
>