Forum Discussion

Adam_Kramer_150's avatar
Adam_Kramer_150
Icon for Nimbostratus rankNimbostratus
Jul 29, 2005

use pool member problem and weird universal persistence error

I have two separate issues but both are related to solving the same problem:

 

 

 

I have the code:

 

 

set node [session lookup universal $hexid]

 

log "found node $node in session table"

 

use pool socks member $node

 

 

This doesn't seem to direct connections to the node that is found with session lookup. I get the output:

 

 

Rule adam_socks_ssl_persist : found node 172.20.20.1 in session table

 

Rule adam_socks_ssl_persist : Connected to backend server 172.20.20.2

 

 

 

This is consistent.

 

 

If I use the "node" command instead of "use pool" then I *do* get sent to the same node every time. This "works" except that it won't send the client anywhere if it doesn't already have a session. If there is session information already it persists properly.

 

 

set node [session lookup universal $hexid]

 

log "found node $node in session table"

 

node $node

 

 

 

Rule adam_socks_ssl_persist : found node 172.20.20.3 in session table

 

Rule adam_socks_ssl_persist : Connected to backend server 172.20.20.3
  • I figured out my other issue before I finished the post - when I was using "node" instead of "use pool" I was getting this error when trying to set the session again later in SERVER_DATA:

     

     

    TCL error: Rule adam_socks_ssl_persist - Prerequisite operation not in progress (line 1) invoked from within "session add universal $hexid [IP::remote_addr]"

     

     

     

    I'm pretty sure that's because the default session add adds to the "pool" session but there isn't exactly a pool selected when you choose a node directly.