When multiples cf-execd are running at the same time, agent is not behaving properly, and node is in NoAnswer state
It happens quitte often that some or more statuses on a node are in NoAnswer state. For example all reports on node1 are green, except for the Add User directive. However, in this example the status of the Password component is Succes. That sounds weird, doesn't it? If Rudder doesn't know if the user exists, how can it check the passwords of that users? Cf-agent is running and there's only one cf-execd process. After running cf-agent -KI manually all Statuses turn to green again. It looks like the user Management technique is the technique where it happens most often.
Today exactly the same happened on the Rudder server with the Distribute Policy technique. However the Check configuration-repository object was red and showed a nasty error message:
EMERGENCY: THE /var/rudder/configuration-repository DIRECTORY IS *ABSENT*. THIS ORCHESTRATOR WILL *NOT* OPERATE CORRECTLY.
However, after running cf-agent -KI manually everything went back to green.
This strange reporting doesn't only happen on one node, but also not on all nodes. Could it be that logs get lost somehow? I'm sorry I can't provide more info about the prob. Please ask if you need something from me. This problem is there for a long time, but since everything goes back green after manually rubnning cf-agent -KI, and since I can't tackle the problem I didn't created a ticket earlier.