Bug #13319
closed
Policy update process was stopped due to an error
Added by Simon Hintermann almost 6 years ago.
Updated almost 6 years ago.
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
Description
I just upgarded to the latest rudder version, and I get this error:
⇨ Policy update error for process '4859' at 2018-08-28 13:20:20
⇨ Cannot write configuration node
⇨ We reach the maximum number of relay depth (20), which is likely to denote a cycle in the chain of policy parents. The faulty chain of node ID is: 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 -> 0dd87dc1-5cae-4ef1-b967-2b5ce4577777
Nothing works anymore, all nodes are red.
I am using a central and two satellites.
Files
Dear Simon,
It seems you have an issue with your node with id 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 : it considers that its relay is itself. Can you check for this node that the /var/rudder/cfengine-community/policy_server.dat does refer to its expected server (either a relay, or the root server itself)
Regards,
Nicolas
Nicolas CHARLES wrote:
Dear Simon,
It seems you have an issue with your node with id 0dd87dc1-5cae-4ef1-b967-2b5ce4577777 : it considers that its relay is itself. Can you check for this node that the /var/rudder/cfengine-community/policy_server.dat does refer to its expected server (either a relay, or the root server itself)
Regards,
Nicolas
Hello,
thanks for your quick answer. Indeed the policy_server.dat are ok, but I recall having done a "rudder agent inventory" at least one time with the same IP than the master. I corrected this yesterday.
I just did a rudde ragent reset; rudder agent inventory, but my central node is still totally wrecked
Quick update and closure: I changed the hostname of a relay server. Bad idea! But the good news is that you can take it back to the old hostname and everything gets back to normal!
Thanks for the help
- Status changed from New to Rejected
Perfect, thank you for the update
I'm closing the ticket then
Also available in: Atom
PDF
Updated by 
Updated by 