Re: ldirectord spinning on SIGPIPE

Hi Simon,

On Tue, Jan 13, 2009 at 10:09:40AM +1100, Simon Horman wrote:
> I had a poke into the change log and found the commit that I was thinking
> about. It is below. However it seems to have been applied well
> before the release of 2.0.7 - the patch was applied in May 2004
> and 2.0.7 was released in August 2006. So unfortuantely I think
> that you have found a new problem that is likely to still be present
> in the latest version.

Yes, that patch is in our copy.

> I guess that what is happening is this:
> 
>   1. attempt to write to a socket/fd
>   2. recieve sigpipe - probably because the socket is closed
>   3. but sigpipe is ignored, so try the write again. repeat endlessly...
> 
> If that is correct, then it seems that simply ignoring sigpipe
> is not a good idea.  I'll have to shift my mind into perl-mode
> in order to think about what to do more clearly.

I'll see if I can persuade it to err by the careful introduction
of iptables rules; we now have a theory that it might be something
that's happening in the ldap check (my colleague has come to this
guess, I'm not exactly sure of the details just now). I have seen
cases where the ldap server (MS Exchange...) accepts the
connection and then just sits there; not what I consider "normal"
behaviour. This may be a trigger.

Thanks!

Matthew


-- 
Matthew Newton, Ph.D. <[email protected]>

Systems Architect (UNIX and Networks), Network Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <[email protected]>
_______________________________________________
Ultramonkey-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/ultramonkey-users