On Mon, Jul 18, 2011 at 05:46:55PM -0400, Jonathan Simms wrote:
> Hello all,
> 
> I've been tearing my hair out trying to get soft-restarts to work reliably, 
> and
> have been frustrated for about a week solid. I'm running 1.4.15 on Ubuntu 
> 10.04
> amd64, kernel version 2.6.32-32-generic.
> 
> The behavior I'm seeing is that -sf restarts will work sporadically from the
> command-line.
> 
> it prints the output:
> 
> [ALERT] 198/213054 (23213) : Starting frontend http-in: cannot bind socket
> [ALERT] 198/213054 (23213) : Starting frontend openstack-ssl-in:
> cannot bind socket
> [ALERT] 198/213054 (23213) : Starting frontend mother-ssl-in: cannot bind 
> socket
> [ALERT] 198/213054 (23213) : Starting frontend authoritae-ssl-in:
> cannot bind socket
> [ALERT] 198/213054 (23213) : Starting frontend encoders-in: cannot bind socket
> [ALERT] 198/213054 (23213) : Starting frontend encoders-v2-in: cannot
> bind socket
> [ALERT] 198/213054 (23213) : Starting frontend redis-in: cannot bind socket

Wow this is very concerning, this bug was a regression in 2.6.38, and it looks
like it was backported to their 2.6.32-32 kernel ! It was fixed in 2.6.38.8 if
my memory serves me right. It seems rather strange they'd backport a patch that
is known to break some products (haproxy and amavis are at least two identified
victims), but it's possible they didn't notice the later fix.

It would be nice to know what exact kernel their 2.6.32 is based on, and ideally
what patches were applied on top of that.

Regards,
Willy


Reply via email to