Architecture #19895: ldap error when accepting 100 nodes at once - Rudder - Issue Tracker

Actions

Copy link

Architecture #19895

open

ldap error when accepting 100 nodes at once

Added by Nicolas CHARLES over 3 years ago. Updated about 3 years ago.

Status:

New

Priority:

N/A

Assignee:

Category:

Performance and scalability

Target version:

Pull Request:

Effort required:

Name check:

To do

Fix check:

To do

Regression:

Description

[2021-08-31 19:46:15+0000] INFO  nodes - New node accepted and managed by Rudder: 22d9d349-cbf7-43d3-8870-0e24b63f233a
[2021-08-31 19:46:15+0000] WARN  explain_compliance.22d9d349-cbf7-43d3-8870-0e24b63f233a - Can not get compliance for node with ID '22d9d349-cbf7-43d3-8870-0e24b63f233a' because it has no configuration id initialised nor sent reports (node just added ?)
[2021-08-31 19:46:15+0000] ERROR nodes.pending - Error when trying to accept node 03bb0219-957d-4851-b472-cd2c855749ce. Rollbacking. <- Error when executing accept node process named accept_new_server:inventory <- Error when moving node with ID '03bb0219-957d-4851-b472-cd2c855749ce' from 'pending' to 'accepted'  <- BackendException: Error when doing action 'modify DN' with and LDIF change request: null; cause was: com.unboundid.ldap.sdk.LDAPException: The connection is not established. 
 -> com.normation.ldap.sdk.RwLDAPConnection.$anonfun$move$2(LDAPConnection.scala:606)
 -> com.normation.ldap.sdk.RwLDAPConnection.$anonfun$applyMod$1(LDAPConnection.scala:514)
[2021-08-31 19:46:15+0000] ERROR nodes.pending - Error when rollbacking server node id 03bb0219-957d-4851-b472-cd2c855749ce in process 'accept_new_server:inventory', you should delete it by hand. Error messages: Error when moving node with ID '03bb0219-957d-4851-b472-cd2c855749ce' from 'accepted' to 'pending'  <- BackendException: Error when doing action 'modify DN' with and LDIF change request: null; cause was: com.unboundid.ldap.sdk.LDAPException: no such object 
 -> com.normation.ldap.sdk.RwLDAPConnection.$anonfun$move$2(LDAPConnection.scala:606)
 -> com.normation.ldap.sdk.RwLDAPConnection.$anonfun$applyMod$1(LDAPConnection.scala:514)
[2021-08-31 19:46:15+0000] INFO  nodes - New node accepted and managed by Rudder: 13daa44a-d14a-437c-a5ac-2c00a4a7e600

no error in slapd logs, and it was up and running

Actions

Copy link

Updated by Nicolas CHARLES over 3 years ago

moving from 2 to 6 ldap connections improves dratically the perfs and removes the issue

Actions

Copy link

Updated by François ARMAND over 3 years ago

Target version changed from 7.0.0~beta1 to 899

So, we need at least to update documentation on that fact.

Plus, it would be more actionnable for the user (and ourselves) to have a meaningfull info regarding that, but I'm not sure how to do that. Check for The connection is not established and add a message If not related to network condition, this problem can be triggered by a number of LDAP connection to small for you load. Please look at doc here ?

Actions

Copy link