help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cfservd 2.1.10 trouble?


From: Mark . Burgess
Subject: Re: cfservd 2.1.10 trouble?
Date: Mon, 23 Aug 2004 23:15:14 +0200 (MEST)

We had a similar problem here during a DOS attack, when things
were going very slowly, but it cleared itself when the offender
was killed. Keep me posted if the problem persists. I don't see
why it should.

M

On 23 Aug, Tod Oace wrote:
> Is anyone else having trouble with 2.1.10's cfservd? I've been getting 
> stale cfservd processes on my cfengine servers ever since I upgraded 
> from 2.1.3. The stale processes build up to MaxConnections and then the 
> fun begins (lots of cfengine email).
> 
> I also found some run-away cfagent processes which weren't helping 
> things any. I'm not sure if the two problems are directly related or 
> not. I strace'd the processes and they all do this forever:
> --- SIGPIPE (Broken pipe) ---
> write(1, "cfengine:nwlxsos01: Received sig"..., 259) = -1 EPIPE (Broken 
> pipe)
> sigreturn()                             = ? (mask now [])
> 
> I do have cfagent restart cfservd if it finds it not running. I used to 
> use "useshell=false" and then took that out for some reason during the 
> upgrade. I've put that back in now.
> 
> 
> When I try strace'ing the stale cfservd processes I just get a shell 
> prompt back. Which seems odd.
> 
> I started cfservd in debug mode but I'm still trying to match up debug 
> output with processes. It's tricky without timestamps and pids. "ps 
> alxww | fgrep cfservd" shows lots of processes sleeping in "wait_f" and 
> "tcp_da".
> 
> Anyway, thought I'd check and see if anyone else is seeing anything 
> similar before I continue troubleshooting.
> 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





reply via email to

[Prev in Thread] Current Thread [Next in Thread]