2010/1/21 Tim Cutts <t...@sanger.ac.uk>

>
> On 21 Jan 2010, at 9:00 am, Erlend Leganger wrote:
>
>  I have played with cfengine for a while and set up an environment with
>> about
>> 20 client machines.One day /var/cfengine/inputs was empty on one of these
>> machines. I don't know why and it was easy to fix, but I wasn't warned
>> about
>> it - I came across it by accident. So, how many of my cfengine-activated
>> clients do really run cfengine? I ended up visiting all of them and found
>> a
>> few more with problems - such a brute force method doesn't scale well.
>>
>> How do you monitor this? Maybe activate a policy from time to time to send
>> an email to you? Analyse the log files to verify that all clients check in
>> every hour (my clients are on an hourly cf-execd)? Use other tools such as
>> ganglia/nagios/icinga? Any best practice here?
>>
>
> On my cfengine2 setup, I run a cron job on the policy server, which looks
> at the directory containing lastseen databases.  There should be a lastseen
> database in there for each host that cfengine has ever seen.  The script
> looks for any of these which haven't called in for more than 24 hours.  It
> looks them up in DNS - if they don't exist in DNS, it assumes it's an old
> machine that has been decommissioned, and removes the lastseen database for
> it.  Otherwise, it reports to me in a mail which machines have not reported
> in to cfengine in the last 24 hours.  Something like this one, from last
> night:
>
> Hmm, in my cfengine v3.0.2 setup, /var/cfengine/lastseen is empty. There is
a /var/cfengine/cf_LastSeen.db which probably contains the same info for
cf3, but that is not readily accessible to me - maybe I can crank up Perl to
look into cf_LastSeen.db - but then again, I have no idea of the schema for
the data in there. Any tips out there on how to access cf_LastSeen.db or is
this a dead end?

- Erlend
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to