Hi Charles,

On Thu, Mar 31, 2011 at 02:42:54PM -0500, Charles Duffy wrote:
> Howdy! I'm having trouble with the haproxy reload command. The below happens
> on my VPS vendor's builds of Linux 2.6.38 but not their 2.6.35:
> 
> + /usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid
> -sf 27913
> [ALERT] 089/191251 (27947) : Starting frontend pgsql-master-in: cannot bind
> socket
> [ALERT] 089/191251 (27947) : Starting frontend pgsql-slave-in: cannot bind
> socket
> + retval=1
> 
> ...stopping and starting from scratch works fine. The global, default and
> frontend sections from the configuration are given below.
> 
> global
>         maxconn 4096
>         chroot  /var/lib/haproxy
>         user    haproxy
>         group   haproxy
>         stats   socket /var/lib/haproxy/haproxy.sock mode 0600 level admin
> 
> defaults
>         mode    http
>         balance roundrobin
>         retries 3
>         option  redispatch
>         timeout connect 5s
>         timeout client 10h
>         timeout server 10h
> 
> frontend pgsql-master-in
>         mode    tcp
>         bind    0.0.0.0:15432
>         default_backend pgsql-master-out
> 
> frontend pgsql-slave-in
>         mode    tcp
>         bind    0.0.0.0:25432
>         default_backend pgsql-slave-out
> 
> ...If any guidelines are available on kernel configuration options necessary
> for this support, I'd be happy to raise those with the relevant folks.

I'm not aware of any required kernel config option for this. It's scary, it
sounds like a kernel regression preventing the process from binding to a TCP
port it was using a few seconds ago. Do you know if you still have established
connections when you reload ? We could imagine that the kernel refuses to bind
in this case (which still would be a regression which should be reported).

Thanks,
Willy


Reply via email to