Re: ldirectord spinning on SIGPIPE

Hi,

On Mon, Jan 12, 2009 at 08:49:10PM +1100, Simon Horman wrote:
> On Mon, Jan 05, 2009 at 01:13:57PM +0000, Matthew Newton wrote:
> > Recently the ldirectord process has stopped working fairly
> > frequently. Symptoms are that services are not being checked, and
> > the ipvs tables are not updated. The ldirectord process is still
> > running, but stracing it gives, for example:
> > 
> > --- SIGPIPE (Broken pipe) @ 0 (0) ---
> > write(4, "\27\3\1\0\33\r\310Q\347\n\230\375@\370 \372\263\322\256"..., 32) = -1 EPIPE (Broken pipe)
> 
> Almost certianly signal-handler badness = bug.
> 
> I strongly suspect that this has been fixed in more recent versions of
> ldirectord (I recall fixing it). I can try and verify that if it helps.

OK, thanks - I'll try the latest version first! It's been running
all week with strace, and no sign of a problem, annoyingly.

Is the latest 2.1.4 ldirectord a drop-in replacement for 2.0.8? If
so, I'll do so next time it crashes (or some other time if it
doesn't...).

I like the look of the new "fork" option - that was going to be my
next question! Checking is very slow at the moment due to the
number of services.

Cheers,

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