Hello Ludovic,

Could you please be more accurate ? Or explain what is wrong in my config file ?

<Proxy balancer://sogocluster>
  BalancerMember http://127.0.0.1:20000 retry=3 max=1 timeout=120
  BalancerMember http://127.0.0.1:20001 retry=3 max=1 timeout=120
  BalancerMember http://127.0.0.1:20002 retry=3 max=1 timeout=120
  ProxySet lbmethod=byrequests maxattempts=1
  Allow from all
  AddDefaultCharset UTF-8
</Proxy>

SetEnv proxy-nokeepalive 1
ProxyRequests Off
ProxyPreserveHost On
ProxyPass /SOGo balancer://sogocluster/SOGo retry=0

Thanks all for your feedback !!

Edouard.

Le 23/11/2010 15:42, Ludovic Marcotte a écrit :
On 10-11-23 9:37 AM, Edouard Leib wrote:
Hi Martin,

It looks like, you're right, but sometimes everything is right !! I don't understand what happens ....

Please find my apache logs below :
[Tue Nov 23 15:34:14 2010] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:20000 (127.0.0.1) failed
[Tue Nov 23 15:34:14 2010] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Tue Nov 23 15:34:14 2010] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:20001 (127.0.0.1) failed
[Tue Nov 23 15:34:14 2010] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)

May be there is a mistake with the sogo cluster ?
Look for "exceptions" in your sogod.log, use more than 1 sogod worker and put retry=0 in your ProxyPass section from your SOGo Apache configuration.
-- 
Ludovic Marcotte
[email protected]  ::  +1.514.755.3630  ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) 

--


PERAX SA - Automates de télégestion
Edouard Leib - [email protected]
Administrateur réseaux, systèmes et téléphonie
Tél. +33 (0)5 62 75 95 71
PERAX SA - Automates de télégestion / Automates de télégestion - w w w . p e r a x . f r
Avant d'imprimer, ayez une pensée pour notre environnement

Reply via email to