RE: Starting proxy [name]: cannot bind socket

Ok, thanks.
This is the problem, in one of my test, I put the "-D" at the end, and it fails, but the correct form is this: # haproxy -D -f /etc/haproxy/haproxy.conf -p /var/run/haproxy.pid -st 6351 Thanks for all,

Regards.

> From: cyril.bonte#free.fr
> To: rikr_#hotmail.com
> Subject: Re: Starting proxy [name]: cannot bind socket
> Date: Mon, 31 Oct 2011 17:59:20 +0100
> CC: haproxy#formilux.org
>
> I reintroduce the mailing list to my answer (please use "reply all" ;-) )
>
> Le lundi 31 octobre 2011 17:45:58, Ricardo F a écrit :
> > Hello Cyril,
> > Thanks for your reply.
> > If i put the "cat", the terminal wait for.. ¿I don't know?. Look this:
> > # ps auxf | grep hapr
> > root 6327 0.0 0.0 7544 844 pts/1 S+ 17:44 0:00 \_ grep hapr
> > root 6325 0.0 0.1 12056 1304 ? Ss 17:43 0:00 /usr/local/sbin/haproxy -f /etc/haproxy/haproxy.conf -D
> > # /usr/local/sbin/haproxy -f /etc/haproxy/haproxy.conf -p /var/run/haproxy.pid -st 6325
> > and the terminal don't return to the command line, whait in a blank line.
> > thanks
>
> OK, now this is because your new instance is not started as a daemon.
> As you see, your first instance has the option "-D", which means the command line indicates haproxy to be run as a daemon.
>
> With this :
> # /usr/local/sbin/haproxy -f /etc/haproxy/haproxy.conf -p /var/run/haproxy.pid -st 6325
> The new instance is not a daemon, which explains what you observe.
>
> 2 options :
> - add the -D option to your command line :
> # /usr/local/sbin/haproxy -D -f /etc/haproxy/haproxy.conf -p /var/run/haproxy.pid -st 6325
> - or add the "daemon" keyword in the global section of your configuration.
>
> Once this works, you can also try to use -sf instead of -st.
>
> Hope this helps.
>
>
> --
> Cyril Bonté
>
                                                Received on 2011/10/31 18:03