Rudder

Hi,

I am not sure if this is a bug, but I experienced it after a 3.1->4.1 update, after the first time the agent was run on the rootserver:

rudder41:~ # rudder agent run
Rudder agent 4.1.5.release (CFEngine Core 3.10.0)
Node uuid: root
Start execution with config [20170710-170037-3ece51e7]

M| State         Technique                 Component                 Key                Message
E| repaired      Common                    Update                                       Rudder policy, tools or ncf instance were updated or CFEngine service restarted
Formal =  {"message","old_class_prefix"}, Actual =  {"Check if the service apache2 is started using ps","service_check_running_apache2","cf_null","@{args}"}
error    Rudder agent was interrupted during execution by a fatal error
         Run with -i to see log messages.

## Summary #####################################################################
1 components verified in 2 directives
   => 1 components in Enforce mode
      -> 1 repaired
execution time: 2.07s
################################################################################
rudder41:~ # rudder agent reset
ok: Rudder agent state has been reset.
rudder41:~ # rudder agent update
 warning: NEW SETGID root PROGRAM '/var/rudder/ncf/local/50_techniques/new_tests/new_tests.cf'
 warning: Method 'update_action' invoked repairs, but only warnings promised
ok: Rudder agent promises were updated.
rudder41:~ #
rudder41:~ # rudder agent run -u -i
Rudder agent 4.1.5.release (CFEngine Core 3.10.0)
Node uuid: root
ok: Rudder agent promises were updated.
Start execution with config [20170710-170037-3ece51e7]

rudder     info: Automatically promoting context scope for 'heartbeat_sent' to namespace visibility, due to persistence
M| State         Technique                 Component                 Key                Message
   info          Common                    Update                                       Rudder ncf common instance updated
   info          Common                    Update                                       Rudder ncf local instance updated
E| repaired      Common                    Update                                       Rudder policy, tools or ncf instance were updated or CFEngine service restarted
rudder     info: Executing 'no timeout' ... '/var/rudder/tools/check-rsyslog-version 5.6.4'
rudder     info: Completed execution of '/var/rudder/tools/check-rsyslog-version 5.6.4'
rudder     info: Executing 'no timeout' ... '/var/rudder/tools/check-rsyslog-version'
rudder     info: Completed execution of '/var/rudder/tools/check-rsyslog-version'
rudder     info: Deleted file '/var/rudder/cfengine-community/outputs/cf_rudder41_local__1497798625_Sun_Jun_18_17_10_25_2017_0x7fcba572f700'
rudder     info: Executing 'no timeout' ... '/var/rudder/tools/check-zypper-version'
rudder     info: Completed execution of '/var/rudder/tools/check-zypper-version'
R: [INFO] Executing is-active-process on apache2 using the service method
   error: While constructing scope '_logger_default'
Formal =  {"message","old_class_prefix"}, Actual =  {"Check if the service apache2 is started using ps","service_check_running_apache2","cf_null","@{args}"}
   error: Fatal CFEngine error: Augment scope, formal and actual parameter mismatch is fatal

error    Rudder agent was interrupted during execution by a fatal error

## Summary #####################################################################
1 components verified in 2 directives
   => 1 components in Enforce mode
      -> 1 repaired
execution time: 2.37s
################################################################################
rudder41:~ #