/ Zope / Apsis / Pound Mailing List / Archive / 2005 / 2005-04 / Configuration Problem With Multiple BackEnds - Pound 1.8.2

[ << ] [ >> ]

[ Re: failover/config / "Timo Hummel" ... ] [ Pound and cookies / Egon <listaseu(at)yahoo.es&... ]

Configuration Problem With Multiple BackEnds - Pound 1.8.2
<F.Alcala-Soler(at)iaea.org>
2005-04-14 19:58:06 [ FULL ]
Hello,

I have compiled Pound 1.8.2 under the latest Cygwin (Windows 2000) and am
having problems with the following configuration directives:

	ListenHTTP  *,8080
	
	LogLevel	3
	
	UrlGroup    ".*"
	 BackEnd     server1.iaea.org,80,1
	 BackEnd     server2.iaea.org,80,2
	EndGroup

My problem is that although I have not set up session maintenance, I only get
Pound to request data from the first BackEnd (server1). I am not sure if I am
missing something obvious, but my understanding is that it would either
round-robin the requests or even place more weight on the second BackEnd, since
it has a higher priority.

Any help would be much appreciated.

Regards,

 Curro

This email message is intended only for the use of the named recipient.
Information contained in this email message and its attachments may be
privileged, confidential and protected from disclosure. If you are not the
intended recipient, please do not read, copy, use or disclose this
communication to others. Also please notify the sender by replying to this
message and then delete it from your system.

Re: Configuration Problem With Multiple BackEnds - Pound 1.8.2
Robert Segall <roseg(at)apsis.ch>
2005-04-15 18:35:43 [ FULL ]
On Thursday 14 April 2005 19:58, F.Alcala-Soler(at)iaea.org wrote:[...]

I suggest you either use the numeric addresses for the back-end servers or at 
least check what the names resolve to: it sounds like you may have a name 
resolution issue, with both servers resolving to the same address or (less 
likely) server2 not resolving at all.

You may also want to look in the logs to see if you get any error messages re. 
server2, such as its being declared "dead". This could happen even with a 
correct address if your back-end listens on some port other than 80.[...]

MailBoxer