On 04/30/2012 10:54 AM, Abid Khwaja wrote: > 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.
That is true in the sense that is the only time failsafe.cf is run when you haven't manually specified it. The default policy has the exec_command running cf-agent -f failsafe.cf to do your policy update, so technically its specifically called. If you never specify to run the failsafe like that and you have not included it in your body agent control inputs list and additionally called the update bundle it contains then the only time failsafe.cf will get executed is on a policy error. I hope that helps. The short version is "failsafe.cf is only _automatically_ executed if the 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. You could have it defined in both, the default policy only defines daemon start in the failsafe.cf which pulls double duty and also functions as the update mechanism. You could of course have a seperate update policy in addition to the failsafe but I think that gets a little verbose and harder to maintain which I believe is why most people just use the failsafe to perform updates for them. > 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"" I would need to see your policy for the specifics of those errors. That looks like the policy is just starting the daemon without regard for the fact that its currently started. -- Nick Anderson <n...@cmdln.org> _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
