On 04/24/2012 07:58 AM, Neil Watson wrote: > On Tue, Apr 24, 2012 at 10:18:32AM +0200, no-re...@cfengine.com wrote: >> I believed that there was a postinstall script in the previous package >> to copy /var/cfengine/bin/cf-agent to /var/cfengine/bin/cf-twin if it >> does not exist and when $(sys.cf_twin) is used and there is no >> /var/cfengine/bin/cf-twin, CFE will use /var/cfengine/bin/cf-agent >> instead. > > I saw cf-execd error out yesterday because the execd agent variable > referenced cf-twin that was not there. No attempt was made to use > cf-agent instead.
When I upgraded to 3.3.0 using the rpm this is what I found. CFEngine was running before I upgraded the rpm. After upgrading CFEngine was not running, I believe it should be restarted if it is running already. If you start CFEngine after the upgrade, with the default promises.cf the agent is unable to update its policy from the master because body executor control uses $(sys.cf_twin) as part of the exec_command to run a policy update and running that results in the error /var/cfengine/bin/cf-twin: symbol lookup error: /var/cfengine/bin/cf-twin: undefined symbol: SYSLOGPORT deleting the cf-twin binary without restarting cfengine results in the following error sh: /var/cfengine/bin/cf-twin: No such file or directory restarting cf-execd after deleting /var/cfengine/bin/cf-twin restores the agent to a runnable/updateable state this still leaves /usr/local/sbin/cf-twin as cruft This looks like it along with other things will be addressed in bug 1066 https://cfengine.com/bugtracker/view.php?id=1066 -- Nick Anderson <n...@cmdln.org> _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
