It happens from time to time that a NFS file system which cfengine uses
becomes unavailable. This usually results in cf-agent processes
building up until such time as connectivity is restored. In an attempt
to thwart this accumulation I implemented an abortclass as follows:
In promises.cf:
body agent control {
# Do not rely on DNS
skipidentify => "true";
abortclasses => { "cf-agent_out_of_range" };
}
In cf-execd.cf, "bundle agent executor":
processes:
"cf-agent"
process_count => check_range("cf-agent",1,2);
However the verbose output indicates that cf-agent "will not kill
itself!" which seems to defeat the whole purpose of "abortclasses."
Any ideas as to why I'm seeing this contradictory behaviour? I'm
running cfengine-community 3.1.2 on CentOS 5.5 x86_64.
Thanks,
Frans
cf3 =========================================================
cf3 processes in bundle executor (1)
cf3 =========================================================
cf3
cf3 Observe process table with /bin/ps -eo
user,pid,ppid,pgid,pcpu,pmem,vsz,pri,rss,nlwp,stime,time,args
cf3
cf3 .........................................................
cf3 Promise handle:
cf3 Promise made by: cf-execd
cf3 .........................................................
cf3
cf3 -> No signals to send for cf-execd
cf3 -> No restart promised for cf-execd
cf3
cf3 .........................................................
cf3 Promise handle:
cf3 Promise made by: cf-agent
cf3 .........................................................
cf3
cf3 cf-agent will not kill itself!
cf3 !! Process count for 'cf-agent' was out of promised range (6 found)
cf3 I: Report relates to a promise with handle ""
cf3 I: Made in version 'not specified' of
'/var/cfengine/inputs/cf-execd.cf' near line 25
cf3 -> No signals to send for cf-agent
cf3 -> No restart promised for cf-agent
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
