Hi list,
 
I'm having an issue adding a third backend to a service on my Pound load 
balancer. 
 
The issue is this:
When running poundctl -c /var/lib/pound/pound.cfg | grep node1 |wc -l I can see 
roughly 200 sessions connected to node1. The same command for node2 shows 92 
sessions, running the command for node3 shows zero. However, running a packet 
sniffer (tethereal port 80 | grep 143.160.xx.xxx) shows that there is indeed 
traffic flowing via port 80 to the new backend. Furthermore, if node1 and node2 
are both shutdown, the load balancer still forwards all traffic to the new 
backend. Pounctl just does not show any sessions when queried. 
 
Here's how my configuration looks:
 
Pound load balancer:
Pound-2.5-1.el6.1.x86_64
RHEL 6.1
Config from file:
Service
    URL ".*"
    HeadRequire "Host:.*service.example.com.*"
    BackEnd
        Address 143.160.xx.xxx
        Port    80
        TimeOut 120
    End
    BackEnd
        Address 143.160.xx.xxx
        Port    80
        TimeOut 120
    End
    BackEnd
        Address 143.160.xx.xxx
        Port    80
        TimeOut 120
    End
 
    Session
        Type COOKIE
        ID "JSESSIONID"
        TTL 7200
    End
End
 
Backends:
node1
httpd-2.2.3-11.el5_1.3
Tomcat5
RHEL 5.2
mod_proxy_ajp
node2
httpd-2.2.3-11.el5_1.3
Tomcat5
RHEL 5.2
mod_proxy_ajp
node3
httpd-2.2.3-53.el5_7.3
Tomcat5
RHEL 5.7
mod_proxy_ajp
As you can see, we're using Apache and mod_proxy_ajp to contact a webapp 
running on Tomcat on all three servers. I've been wondering if this problem is 
not perhaps cookie related, but I'm unsure how to go about testing this. Any 
help would be greatly appreciated.
 
Greetings,
 
Jonathan van der Watt
 
 

Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html

Reply via email to