Hi, On 06.03.2013 16:58, Olivier Desport wrote: > I've found the solution. I have enabled the line EXTRAOPTS="-de -m 16" > in /etc/default/haproxy. It works when this line is commented. > That means, you gave haproxy only 16MB of memory for his hard work. Maybe this was not enough.
> Thanks for your help. > > > > Le 23/01/2013 17:13, shouldbe q931 a écrit : >> Hi Olivier, >> >> Just to recap, you have a webserver in subnet A, you have a HAProxy >> instance in subnet B >> >> When you connect to the webserver directly, CSS works >> When you connect to the webserver via HAProxy, CSS fails >> >> You have now added a HAProxy instance in subnet A >> When you connect via the HAProxy instance in subnet A CSS works >> >> I have noticed that you are using >> >> acl acl_web hdr(host) -i mysite.mydomain.com <http://mysite.mydomain.com> >> use_backend web if acl_web >> >> I have inferred from this that you have more acls configured in the >> frontend, and that you have more then one backend. >> >> When you setup the HAProxy instance in subnet A, did you scp/rsync >> the config over and just change the bind IP address, or did you only >> use the relevant sections of the confg ? >> >> I wonder if there is another ACL that is causing the issue ? >> >> I would also be tempted to change the HAProy config on the instance >> in subnet B to point at the HAProxy in subnet A, then test connecting >> via the HAProxy instance in subnet B >> >> If the two HAProxy configurations are identical apart from the bind >> IP address and the backend server address and this works, then I >> would investigate if there are any IP restrictions configured on the >> web server, if it fails, then I would suggest further investigation >> on the HAProxy instance in subnet B >> >> Cheers >
