Create a cronjob/script that checks if cfexecd is running.
*/15 * * * * root /etc/cfengine/check_cfdaemons.cfIf you use cfagent as interpreter it will even send you an email if the daemons were restarted/crashed.
- Ramon.
root# cat /etc/cfengine/check_cfdaemons.cf
#!/usr/sbin/cfagent -K -x -f
#
control:
actionsequence = ( processes )
processes:
any::
"cfexecd"
filter=daemons matches=1 action=bymatch signal=kill inform=on
restart "/etc/init.d/cfexecd restart"
"cfservd"
filter=daemons matches=1 action=bymatch signal=kill inform=on
restart "/etc/init.d/cfservd restart"
"cfagent"
filter=daemons signal=kill
filters:
# only get processes that have PPID 1
#
{ daemons
PPID: "1"
Result: "PPID"
}
On 01/21/2010 10: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?- Erlend Leganger
-- R. Bastiaans, B.ICT :: Systems Programmer, HPC&V SARA - Computing& Networking Services Science Park 121 PO Box 94613 1098 XG Amsterdam NL 1090 GP Amsterdam NL P.+31 (0)20 592 3000 F.+31 (0)20 668 3167
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
