I was trying to troubleshoot this with a packet dump on the "peer" traffic. The raw tcpdump does not mean anything to me, and Wireshark is decoding it as Java RMI traffic which isnt much use, and it looks like a binary protocol.
So I can report that 'peer' traffic is certainly working because when I restart one of the haproxy processes there are a bunch of different packets sent (Wireshark doesent even attempt to decode these). I was hoping to be able to grep for one of the offending session IDs to see if that gave me a hint. Does anybody have a working configuration for multi peer persistence based on a cookie that I could test, by chance? Thanks, -Alex
