[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Cfengine] Re: cfexecd, FatalError(), leaves cfagent burning 100% cp
From: |
Chip Seraphine |
Subject: |
Re: [Cfengine] Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu |
Date: |
Thu, 7 Oct 2004 11:51:25 -0500 |
User-agent: |
KMail/1.5.4 |
On Wednesday 06 October 2004 09:57, Andrew Stribblehill wrote:
> Quoting Mark Burgess <Mark.Burgess@iu.hio.no> (2004-10-06 15:50:15 BST):
> > I have not understood this discussion. What is -Q ?
>
> -Q allows you to query the Cfagent-parsed configuration for
> variables. So:
>
> # cfagent -Q sysadm,schedule
> sysadm=20:ads@womble.dur.ac.uk
> schedule=8[Min00_05]
> schedule=8[Min15_20]
> schedule=8[Min30_35]
> schedule=8[Min45_50]
>
> This way, Cfagent doesn't need to know what Cfexecd considers to be
> special variables.
I like it. Of course, I'd be even happier if cfexecd had its own config
file-- all my ReturnsZero()s in groups: always fire when cfexecd does it's
"cfagent -z" calls.
> This wasn't actually the point of my message to you though, Mark.
> Because we broke the -Q code, one of the programs got into an
> infinite loop. The SIGPIPE handler wasn't masking out SIGPIPE calls,
> so the process was never exiting.
>
> The two URLs I posted describe it in more detail.
Just wanted to confirm that cfagent infinite looping, using 100% CPU, and
getting lots of SIGPIPEs also happens in Mandrake. Several times a day one
or more of my Mandrake boxes gets a 'stuck' cfagent and trussing it shows
this:
chip@billy-11:50:35-/home/titan/chip$ sudo strace -p 4473 2>&1 | head
Process 4473 attached - interrupt to quit
rt_sigaction(SIGPIPE, {0x40324ea0, [], SA_RESTORER, 0x40267718}, {0x808ec00,
[PIPE], SA_RESTORER|SA_RESTART, 0x40267718}, 8) = 0
send(5, "<11>Oct 7 11:50:40 cfagent: Re"..., 87, 0) = 87
rt_sigaction(SIGPIPE, {0x808ec00, [PIPE], SA_RESTORER|SA_RESTART, 0x40267718},
NULL, 8) = 0
getuid32() = 0
time([1097167840]) = 1097167840
rt_sigaction(SIGPIPE, {0x40324ea0, [], SA_RESTORER, 0x40267718}, {0x808ec00,
[PIPE], SA_RESTORER|SA_RESTART, 0x40267718}, 8) = 0
send(5, "<11>Oct 7 11:50:40 cfagent: Lo"..., 73, 0) = 73
rt_sigaction(SIGPIPE, {0x808ec00, [PIPE], SA_RESTORER|SA_RESTART, 0x40267718},
NULL, 8) = 0
getuid32()
--
Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com
- cfexecd, FatalError(), leaves cfagent burning 100% cpu, Will Lowe, 2004/10/04
- Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Andrew Stribblehill, 2004/10/05
- Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Will Lowe, 2004/10/05
- Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Tom Carlile, 2004/10/05
- Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Tod Oace, 2004/10/05
- Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Andrew Stribblehill, 2004/10/06
- Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Mark Burgess, 2004/10/06
- Message not available
- Re: [Cfengine] Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Bas van der Vlies, 2004/10/06
- Re: [Cfengine] Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Mark Burgess, 2004/10/06
- Re: [Cfengine] Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Andrew Stribblehill, 2004/10/06
- Re: [Cfengine] Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu,
Chip Seraphine <=
- what's cfexecd for? (was cfexecd, FatalError(), leaves cfagent), Will Lowe, 2004/10/07
- Re: what's cfexecd for? (was cfexecd, FatalError(), leaves cfagent), Chip Seraphine, 2004/10/07
- Re: what's cfexecd for? (was cfexecd, FatalError(), leaves cfagent), Andrew Stribblehill, 2004/10/07