The error earlier reported during -dev7 about not compiling with DEBUG_FULL is still present in rc1 and ss-20100208. As that msg indicated, changing it f rom req to rep allowed the compile.
Aside from DEBUG_MEMORY, it looks like most of the other DEBUG_FSM/HASH/AUTH are all related to "mode http". Since I'm strictly "mode tcp" I'm guessing only DEBUG_FULL and DEBUG_MEMORY are of use to me, although DEBUG_MEMORY only seems to activate a couple of signal catchers, so it's not a big thing for me right now. The main reason I'm trying a DEBUG_FULL is I'm getting reports from my clients of not being able to connect, or being disconnected. But my haproxy logs (option tcplog) don't show any sign of it. Even if I had hit some limit (connections, whatever), wouldn't there be an entry in the haproxy logs - denying the incoming connection or whatever, but there'd be some record of it? I admit, being buried in the logs is a bit tough, so I'm not sure yet. I don't see any obvious non "--" status entries in my log (which is kinda where I'm starting.) Any hints on tracking this down would be appreciated :) I realize it's a bit vague, but it's all I've got to go on right now. Thank you, PH
