On Mon, Sep 21, 2015 at 11:55 PM, Willy Tarreau <[email protected]> wrote: > On Mon, Sep 21, 2015 at 11:50:34PM +0530, Pradeep Jindal wrote: > > 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. > > That was my question! Your messages are a bit short, almost cryptic :-/ > > So at least I have a response to this one. Then yes it's a problem. OK so > I won't issue dev6 this evening, we'd rather sort this out before issuing > it. >
Oh! sorry for the confusion, that's exactly what I have been saying in my emails that "syncing is one way" (but registering works correctly). May be I implied too much, sorry about that. > > > 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. > > But please provide a usable configuration. The initial one you provided did > not even involve stick rules. I had to guess them and write them and it > ended > with something working fine. I can't easily guess the differences between > what > I have here that works fine and what you have that doesn't. > Sorry about that, I am sending you my complete configuration (anonimized) via private email.
