The machine in question was running 3.3.3.
On Thu, Jun 21, 2012 at 11:11 AM, wrote:
> Forum: CFEngine Help
> Subject: Re: 180+ instances of cf-execd and cf-agent
> Author: davidlee
> Link to topic: https://cfengine.com/forum/read.php?3,26261,26266#msg-26266
>
> Sorry, my pr
Forum: CFEngine Help
Subject: Re: 180+ instances of cf-execd and cf-agent
Author: davidlee
Link to topic: https://cfengine.com/forum/read.php?3,26261,26266#msg-26266
Sorry, my previous message may have confused two distinct things about managing
this:
Assuming 3.1.4 (or thereabouts) with
Forum: CFEngine Help
Subject: Re: 180+ instances of cf-execd and cf-agent
Author: davidlee
Link to topic: https://cfengine.com/forum/read.php?3,26261,26265#msg-26265
What version of cfengine? This might matter... see below.
Over the last 15 months or so, our cfengine3 installation has grown
As Mike pointed out NFS is a usual culprit.
--
Sent from my Android phone with probably ridiculous and involuntary spelling
corrections.
Brian Bennett wrote:
Ron,
It looks to me like you have a promise that's getting hung on something. Run
`cf-agent -KIv` (cap k, cap i, little v) and watch t
Ron,
It looks to me like you have a promise that's getting hung on something. Run
`cf-agent -KIv` (cap k, cap i, little v) and watch the output. You should be
able to see where it's hanging.
--
Brian
On Jun 21, 2012, at 8:01 AM, Ron Parker wrote:
> In testing that the promises for a given m
Hey Ron
I have the following in a promise. You may want to adjust the values of
"ago" there. I execute cf-agent once an hour. If I see a cf-agent
process older than 2 hours old, I have the current execution kill that
process and I raise a class that I report on. You could use this same
thing
In testing that the promises for a given machine were sufficient to
reconfigure it from scratch, I did a fresh OS install to a VM,
bootstrapped CFE and manually started cf-agent. After about 30
minutes and the fourth email from the system, it had converged. I
noted a few things that were missing,
