The timestamp on the applicable key is last Feb. "cf-key -s" shows two
identical entries for the policy server, not sure how that happened, but 3.1.4
doesn't have a problem with it. The cf-promises from 3.2.1 gave my files a
clean bill of health. I'm guessing there's something in my syntax the newer
version don't like ...
I replaced all of the vars here w/ full paths, no change;
bundle server access_rules()
{
access:
"${sys.workdir}/masterfiles"
admit => { "10." };
"${sys.workdir}/modules"
admit => { "10." };
"${global.repo}"
admit => { "10." };
"${global.cfpath}"
admit => { "10." };
roles:
".*" authorize => { "root" };
}
Maybe something here?
body server control
{
allowconnects => { "10\..*" };
allowallconnects => { "10\..*" };
allowusers => { "root" };
cfruncommand => "/usr/local/sbin/cf-agent -f failsafe.cf &&
/usr/local/sbin/cf-agent";
denybadclocks => "false";
logallconnections => "true";
maxconnections => "500";
serverfacility => "LOG_LOCAL6";
trustkeysfrom => { "10\..*" };
}
On Nov 1, 2011, at 12:14 PM, [email protected] wrote:
> Forum: CFEngine Help
> Subject: Re: "REFUSAL of request from connecting host" after 3.1.4 > 3.2.1
> update
> Author: neilhwatson
> Link to topic: https://cfengine.com/forum/read.php?3,23868,23869#msg-23869
>
> Did any of the keys get changed?
>
> _______________________________________________
> Help-cfengine mailing list
> [email protected]
> https://cfengine.org/mailman/listinfo/help-cfengine
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
