Hi Alfonso, I've tried swapping the location before and you're right, it
makes no difference.

Can you let me know which version of pound you're running?

Thanks,
 --Cameron



On Tue, Sep 30, 2008 at 5:30 PM, Alfonso Espitia <
aespitia(at)castleworldwide.com> wrote:
[...]

I'm currently using 2.4.3.


-----Original Message-----
From: interlnk(at)gmail.com [mailto:interlnk(at)gmail.com] On Behalf Of Cam
Roberts
Sent: Tuesday, September 30, 2008 7:03 PM
To: pound(at)apsis.ch
Subject: Re: [Pound Mailing List] load is not balanced when session
handling

Hi Alfonso, I've tried swapping the location before and you're right, it
makes no difference.

Can you let me know which version of pound you're running?

Thanks,
 --Cameron



On Tue, Sep 30, 2008 at 5:30 PM, Alfonso Espitia <
aespitia(at)castleworldwide.com> wrote:
[...]
[...]
pound(at)apsis.ch.[...]
pound(at)apsis.ch.[...]

--
To unsubscribe send an email with subject unsubscribe to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.

--
This message has been scanned for viruses and dangerous content by
SecureMail, and is believed to be clean.

On Tue, 2008-09-30 at 16:06 -0400, Cam Roberts wrote:[...]

Your current configuration is guaranteed not to work - you have defined
a "catch-all" service, so all the traffic goes there.

Your original configuration (assuming this is all you have in the file)
should work. Did you by any chance test it from a single client? Does it
work without session?

Finally, if one of the back-ends is not available, Pound will send all
the traffic to the other one. Check your logs and/or use poundctl.[...]

Thanks for all the assistance so far.

Over the weekend I adjusted by configuration back to its original state,
with a single service and 2 backends specified for both http and https. All
web traffic continues to go to a single web server (10.0.0.2) when  Session
with Type IP is defined.

Relevant portions of my configuration are below, I've been using the
listenHTTP service on port 2080 to confirm that requests do get forwarded to
both servers when Session is not defined.
Currently I'm running version 2.0 on debian.  (I have built 2.4.3, however I
encounter a separate problem with that version.)

ListenHTTP
        Address 205.207.162.162
        Port    80

        ## allow PUT and DELETE also (by default only GET, POST and HEAD)?:
#       xHTTP           0
#       AddHeader "X-Forwarded-Proto: http"

        Service
                BackEnd
                        Address 10.0.0.2
                        Port    80
                End
                BackEnd
                        Address 10.0.0.4
                        Port    80
                End
                Session
                        Type IP
                        TTL 300
                End
        End
End

ListenHTTPS
        Address 205.207.162.162
        Port 443

        Cert "/usr/local/ssl/crt/public.pem"
        VerifyList "/usr/local/ssl/crt/intermediate.crt"

        AddHeader "X-Forwarded-Proto: https"

        Service
                BackEnd
                        Address 10.0.0.2
                        Port 80
                End
                BackEnd
                        Address 10.0.0.4
                        Port 80
                End
                Session
                        Type IP
                        TTL 300
                End
        End
End

#
#temporary setup for load balance testing
#
ListenHTTP
        Address 205.207.162.162
        Port    2080

        ## allow PUT and DELETE also (by default only GET, POST and HEAD)?:
#       xHTTP           0
#       Cert "/usr/local/ssl/crt/public.pem"
#       AddHeader "X-Forwarded-Proto: https"

        Service
                BackEnd
                        Address 10.0.0.2
                        Port    80
                End
                BackEnd
                        Address 10.0.0.4
                        Port    80
                End
        End
End




On Wed, Oct 1, 2008 at 11:48 AM, Robert Segall <roseg(at)apsis.ch> wrote:
[...]

[...]

Don't know if this matters or not, but all of my configs have always had
the "service" directive outside of the listenhttp/listenhttps.

Basically, mine just define the listenhttp and listenhttps on top, and
then after that I have a list of different services. 

-----Original Message-----
From: interlnk(at)gmail.com [mailto:interlnk(at)gmail.com] On Behalf Of Cam
Roberts
Sent: Monday, October 06, 2008 10:27 AM
To: pound(at)apsis.ch
Subject: Re: [Pound Mailing List] load is not balanced when session
handling

Thanks for all the assistance so far.

Over the weekend I adjusted by configuration back to its original state,
with a single service and 2 backends specified for both http and https.
All web traffic continues to go to a single web server (10.0.0.2) when
Session with Type IP is defined.

Relevant portions of my configuration are below, I've been using the
listenHTTP service on port 2080 to confirm that requests do get
forwarded to both servers when Session is not defined.
Currently I'm running version 2.0 on debian.  (I have built 2.4.3,
however I encounter a separate problem with that version.)

ListenHTTP
        Address 205.207.162.162
        Port    80

        ## allow PUT and DELETE also (by default only GET, POST and
HEAD)?:
#       xHTTP           0
#       AddHeader "X-Forwarded-Proto: http"

        Service
                BackEnd
                        Address 10.0.0.2
                        Port    80
                End
                BackEnd
                        Address 10.0.0.4
                        Port    80
                End
                Session
                        Type IP
                        TTL 300
                End
        End
End

ListenHTTPS
        Address 205.207.162.162
        Port 443

        Cert "/usr/local/ssl/crt/public.pem"
        VerifyList "/usr/local/ssl/crt/intermediate.crt"

        AddHeader "X-Forwarded-Proto: https"

        Service
                BackEnd
                        Address 10.0.0.2
                        Port 80
                End
                BackEnd
                        Address 10.0.0.4
                        Port 80
                End
                Session
                        Type IP
                        TTL 300
                End
        End
End

#
#temporary setup for load balance testing # ListenHTTP
        Address 205.207.162.162
        Port    2080

        ## allow PUT and DELETE also (by default only GET, POST and
HEAD)?:
#       xHTTP           0
#       Cert "/usr/local/ssl/crt/public.pem"
#       AddHeader "X-Forwarded-Proto: https"

        Service
                BackEnd
                        Address 10.0.0.2
                        Port    80
                End
                BackEnd
                        Address 10.0.0.4
                        Port    80
                End
        End
End




On Wed, Oct 1, 2008 at 11:48 AM, Robert Segall <roseg(at)apsis.ch> wrote:
[...]
300.[...]
[...]
[...]
[...]
pound(at)apsis.ch.[...]


--
Thanks,
--Cameron Roberts

--
To unsubscribe send an email with subject unsubscribe to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.

--
This message has been scanned for viruses and dangerous content by
SecureMail, and is believed to be clean.

On Mon, 2008-10-06 at 10:27 -0400, Cam Roberts wrote:[...]

You really should go to 2.4.3 - a serious problem with IP sessions was
fixed in 2.4.[...]