Hi,

I'm trying to get pound to maintain "session-stickiness" based on a COOKIE
(btw I'm using pound with a Django application which has a session cookie
named "sessionid"). But this doesn't seem to work.

Is there any way to see if pound has managed to discover these cookies and
also get a dump of its internal table mapping "cookie values -> backends"? I
tried bringing up the log level to the highest value (=5) but that doesn't
tell me if pound has discovered the cookie or not. Other load balancers like
perlbal usually have an API to add/remove backends, etc. Is there something
similar for pound?

Cheers,
[...]

The poundctl command should show you the info.
Here's the output from my pound instance with cookie sessions:

  0. http Listener 0.0.0.0:7001 a
    0. Service "Weblogic" active (10)
      0. Backend PF_INET 10.120.3.52:7001 active (5 0.000 sec) alive
      1. Backend PF_INET 10.120.3.53:7001 active (5 0.000 sec) alive
      0. Session
I7zsENAGBiucwiLvESOHz18SA2B8ZTcK4cXJnmdqQgyS8vM17mTm!325152924 -> 0
      1. Session
I7zr2X6qqr9D1dFUQaySRd5iW5UwPEmG2LnhpKpHZ10SeDELlasl!1018771204 -> 1
      2. Session
I7zZa733VxdZMyqpOQ9Pd7fHd8uarCkq0VfgZtrveQN22fXoXEUh!325152924 -> 0
      3. Session
I7z3UK01YeSZmJ8mRc027hHYZ1365FOnuuK08TeCKoerOd4wT1db!1018771204 -> 1
      4. Session
I7yzA9ZW15pJTuiBHEsQ1eDJSfE11xGlugSR1tMqy15G6J8DAqyC!325152924 -> 0
      5. Session
I7ycV1s1Im4XlxHCQz8LveqQAl0H5FL2P3Ac1Ap2dN2fUDGWmSho!1018771204 -> 1


--
François Rejeté

On Tue, May 27, 2008 at 11:57 AM, Harish Mallipeddi
<harish.mallipeddi(at)gmail.com> wrote:[...]

Thanks. That's basically what I was looking for.

Cheers,
Harish

PS: For some reason, your reply didn't show up in GMail. I ended up looking
for it in the archive page.

On Tue, May 27, 2008 at 11:06 AM, Francois Rejete
<francois(at)rejete.com>
wrote:
[...]
[...]

We had problems when we set the TTL of the sessions to 20 minutes.
In 2.4.2 the session only lasts 20 minutes from the initial hit, so if a 
user is active on the site for 25 mins, at the 20 min mark pound expires 
the session and the next hit will start a new session and probably go to 
a different backend.

We expected the 20 minutes to be extended each time a hit is received.

I posted a patch to 2.4.2 here
http://www.apsis.ch/pound/pound_list/archive/2008/2008-05/1211419467000#1211419467000

The other alternative is to use a TTL of -1 which means the cookies will
always get hashed to the same backend

Harish Mallipeddi wrote:[...]