It may be completely irrelevant, but that's one of two issues I've seen with multiple instances of cfagent clobbering each other (somewhat) silently. The other is the correct "denying multiple connections" errors...
This was happening to me when cfexecd running in daemon mode was firing off a cfagent at the same time as a cron'd cfexecd->cfagent.
Just a thought. /eli PAUL WILLIAMSON wrote:
Here's the output from cfagent -q -v: Checking copy from <policyhost>:/var/cfengine/masterfiles/inputs to /var/cfengine/inputs Connect to comrcu02emsprod = x.x.x.x on port 5308 Updating last-seen time for <policyhost> Loaded /var/cfengine/ppkeys/root-x.x.x.x.pub cfengine:: Couldn't send cfengine:: send cfengine:: Received signal 13 (SIGPIPE) while doing [no_active_lock] cfengine:: Logical start time Wed Jan 18 11:56:21 2006 cfengine:: This sub-task started really at Wed Jan 18 11:56:21 2006 _______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
_______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
