Project

General

Profile

Actions
Copy link

Bug #16754

open

TLS connection error to a fresh relay - cf-serverd config not reloaded

Added by François ARMAND about 4 years ago. Updated 7 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Target version:
Rudder plugins - 7.3
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

I changed a node into a relay, policy generation was triggered, I did a rudder agent run -u on relay, and then on node, on node, with rudder agent run -u, I got:

[root@agent1 vagrant]# rudder agent run -u
Rudder agent 6.0.3.rc1.git202002180103
Node uuid: cfff1fe7-2d93-4a4d-814d-1614e8308aaf
   error: Failed to establish TLS connection: underlying network error (Connection reset by peer)
   error: No suitable server found
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by:                                                        *
*   * an agent key that has been changed                                        *
*   * if this node is not accepted or deleted node on the Rudder root server    *
*   * if this node has changed policy server without sending a new inventory    *
* Any existing configuration policy will continue to be applied without change. *
*********************************************************************************
error: Rudder agent promises could not be updated.
Start execution with config [0]

If I run the relay in debug (rudder server debug XXXX), then I don't get the TLS error:

[root@agent1 vagrant]# rudder agent run -u
Rudder agent 6.0.3.rc1.git202002180103
Node uuid: cfff1fe7-2d93-4a4d-814d-1614e8308aaf
R: *********************************************************************************
... etc ...

If I stop debug server, then I get back the TLS error.

After some time, it disappeared - most likely, after cf-serverd was finaly able to restart.

Actions
Copy link

Also available in: Atom PDF