Backend warnings retr/redis on stats page

Hi HAproxy 1.4.8. If I look at the stats page, on one of my backends I'm seeing these values under the warning column: retr (344) and redis (172). The backend has 8 servers and only 1 has non-zero values for this column. Can someone explain what the numbers mean, I've tried poking through the

Re: Backend warnings retr/redis on stats page

Graeme, Hmm, it does appear to be a bit hard to find documentation on the stats page :) If I look at the stats page, on one of my backends I'm seeing these values under the warning column: retr (344) and redis (172). The backend has 8 servers and only 1 has non-zero values for this column.

haproxy 1.5 peers multi-process mode (nbproc 1) impact ?

Hi Willy, Seeing some issues in the mailing list with the couple appsession/nbproc 1, I'm working on a small patch to add some warnings if appsession or sticking rules are used on multiple processes (I leave them as non fatal errors to not break current configurations). I've not tested peers

Include client IP address in rewritten URL

I am trying to use haproxy 1.4.8 to replace an apache URL rewriting engine that crumbles under load. I have to duplicate the following part of it: ipaddr=%{REMOTE_ADDR} The IP address is not part of the original URL, but it must be included in the rewritten one. Looking at the

Re: Include client IP address in rewritten URL

Hi Shawn, On Mon, Dec 13, 2010 at 07:29:20PM -0700, Shawn Heisey wrote: I am trying to use haproxy 1.4.8 to replace an apache URL rewriting engine that crumbles under load. I have to duplicate the following part of it: ipaddr=%{REMOTE_ADDR} The IP address is not part of the original

Re: Include client IP address in rewritten URL

This might be obvious, but still: all of the programming languages I know of can access REMOTE_ADDR even if they don't get it via GET vars. For instance, in PHP you can get it from $_SERVER['REMOTE_ADDR']. So there should be no need to use GET vars, just change the way you access the data.