On Apr 30, 2012, at 3:19 PM, Nick Anderson wrote: > As far as how to stop it from happening I suspect that cf-serverd is > being started during your update/failsafe. Look in your body executor > control. What is the exec_command? I suspect its something like > "$(sys.cf_twin) -f failsafe.cf && $(sys.cf_agent)". Thats two seperate > processes, basically update the policy, and if successful then run the > policy. The default bootstrap policy does start cf-monitord and > cf-serverd. Look in failsafe.cf for handle update_processes_cf_serverd > and update_processes_cf_monitord.
Thanks for the clarification. I tested by commenting out the cf-serverd lines in failsafe and cf-serverd did not start. My understanding from the CF3 Reference Manual was that failsafe is read only if the main policy files cannot be read/parsed. Given the above, it would seem that starting cf-serverd should either be defined in failsafe or in one’s main policy files, but not both. I copied all the policy files from the master host to the client and ran cf-execd and got the errors below. So it would seem I’m right about not defining anything in one’s main policy files that are already defined in failsafe? Please advise. Apr 30 11:47:41 client01 user:err|error cf3[557178]: Could not bind server address Apr 30 11:47:41 client01 user:err|error cf3[557178]: !!! System error for bind: "Can't assign requested address" Apr 30 11:47:41 client01 user:err|error cf3[557178]: Couldn't open bind an open socket Apr 30 11:47:41 client01 user:notice cf3[581692]: Q: "...f-serverd"": Could not bind server address Q: "...f-serverd"": !!! System error for bind: "Can't assign requested address" Q: "...f-serverd"": Couldn't open bind an open socket Apr 30 11:47:41 client01 user:notice cf3[581692]: I: Last 3 quoted lines were generated by promiser ""/var/opt/TWWfsw/cfengine323/bin/cf-serverd"" _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
