Re: Troubleshoot Starting proxy http_proxy: cannot bind socket

2009-06-12 Thread Malcolm Turnbull
Aron, Either the socket you are trying to use is already in use... or the IP doesn't exist on the host. 2009/6/12 Aaron Rosenthal > > I don't know how to troubleshoot this issue, any suggestions would be > helpful. Thanks > > [r...@lb1 haproxy-1.3.17]# /etc/init.d/haproxy start > Starting HApro

direct data to users

2009-06-12 Thread Michal Krajcirovic
hello, I need to do on one server balancer, which will operate as follows: one of its IP will come all the requests, and he is sent to one server. in the event of failure, it will send one to the other. I need but to date correspond to those sites (eg large avi) netekly through the server with

Re: direct data to users

2009-06-12 Thread benoit
Michal Krajcirovic a écrit : hello, I need to do on one server balancer, which will operate as follows: one of its IP will come all the requests, and he is sent to one server. in the event of failure, it will send one to the other. I need but to date correspond to those sites (eg large avi) ne

Re: Troubleshoot Starting proxy http_proxy: cannot bind socket

2009-06-12 Thread Ryan Schlesinger
Usually when I run across a daemon that can't bind, I'll run 'netstat -lpn' as root. This will give you a list of all the open sockets and what process has each socket open. Look for the address and port you're trying to bind to. On 06/11/2009 05:17 PM, Aaron Rosenthal wrote: I don't know ho

Re: haproxy include config

2009-06-12 Thread Holger Just
On 12.06.2009 23:08 Uhr, Joe Williams wrote: > I looked through the docs but didn't see anything. Is it possible to > include config files from the main config file? So you could do > something similar to a vhosts.d directory in Apache or Nginx. Hello Joe! Unfortunately, this is not supported by

Re: direct data to users

2009-06-12 Thread Willy Tarreau
On Fri, Jun 12, 2009 at 09:28:23PM +0200, benoit wrote: > Michal Krajcirovic a écrit : > >hello, > >I need to do on one server balancer, which will operate as follows: > >one of its IP will come all the requests, and he is sent to one > >server. in the event of failure, it will send one to the oth