Actions
Bug #14569
closed
Empty generated policies
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
I had empty policies generated for a node
# ls -alh /var/rudder/share/7e47ff39-9ce0-4378-a5c7-44e03a794d51/rules/cfengine-community total 4,0K drwxr-s---. 7 root rudder-policy-reader 4,0K 1 avril 15:25 . drwxr-s---. 3 root rudder-policy-reader 32 1 avril 15:25 .. drwxr-s---. 5 root rudder-policy-reader 46 1 avril 15:25 common -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 failsafe.cf drwxr-s---. 3 root rudder-policy-reader 17 1 avril 15:25 inventory -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 promises.cf drwxr-s---. 2 root rudder-policy-reader 29 1 avril 15:25 properties.d -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 rudder-directives.cf -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 rudder.json -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 rudder-parameters.json -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 rudder_promises_generated -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 rudder-promises-generated -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 rudder-system-directives.cf -rw-r-----. 1 root rudder-policy-reader 0 1 avril 15:25 run_interval drwxr-s---. 3 root rudder-policy-reader 17 1 avril 15:25 service_starting drwxr-s---. 3 root rudder-policy-reader 17 1 avril 15:25 test_line_absent
logs finish by
[2019-04-01 15:17:16] INFO policy.generation - Configuration of following nodes were updated, their promises are going to be written: [7e47ff39-9ce0-4378-a5c7-44e03a794d51, root] [2019-04-01 15:17:17] INFO policy.generation - Timing summary: [2019-04-01 15:17:17] INFO policy.generation - Run pre-gen scripts hooks : 1 ms [2019-04-01 15:17:17] INFO policy.generation - Run pre-gen modules hooks : 0 ms [2019-04-01 15:17:17] INFO policy.generation - Fetch all information : 23 ms [2019-04-01 15:17:17] INFO policy.generation - Historize names : 13 ms [2019-04-01 15:17:17] INFO policy.generation - Build current rule values : 1 ms [2019-04-01 15:17:17] INFO policy.generation - Build target configuration : 10 ms [2019-04-01 15:17:17] INFO policy.generation - Write node configurations : 808 ms [2019-04-01 15:17:17] INFO policy.generation - Save expected reports : 1 ms [2019-04-01 15:17:17] INFO policy.generation - Run post generation hooks : 12 ms [2019-04-01 15:17:17] INFO policy.generation - Number of nodes updated : 2 [2019-04-01 15:17:17] INFO policy.generation - Policy generation completed in: 896 ms [2019-04-01 15:17:17] INFO policy.generation - Flag file '/opt/rudder/etc/policy-update-running' successfully removed [2019-04-01 15:17:17] INFO policy.generation - Successful policy update '29' [started 2019-04-01 15:17:16 - ended 2019-04-01 15:17:17]
and nothing is writen after, so nothing says why its empty
Updated by Nicolas CHARLES over 5 years ago
data are missing in Rudder logs, in postgresql also
maybe the VM got corrupted somehow
Updated by Nicolas CHARLES over 5 years ago
ok, VM was corrupted:
LOG: database system was interrupted; last known up at 2019-04-01 15:23:48 UTC LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 0/3891C18 LOG: record with zero length at 0/38FC7D0 LOG: redo done at 0/38FC7A0 LOG: last completed transaction was at log time 2019-04-01 15:25:42.068609+00
Actions