Bug #19980: spurious "connection_read(9): no connection!" in /var/log/rudder/ldap/slapd.log - Rudder - Issue Tracker

Actions

Copy link

Bug #19980

closed

spurious "connection_read(9): no connection!" in /var/log/rudder/ldap/slapd.log

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

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Performance and scalability

Target version:

6.1.18

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

To do

Fix check:

Checked

Regression:

Description

Sep 20 14:51:24 server rudder-slapd[7888]: connection_read(9): no connection!
Sep 20 14:51:57 server rudder-slapd[7888]: connection_read(20): no connection!
Sep 20 15:01:50 server rudder-slapd[7888]: connection_read(16): no connection!
Sep 20 15:01:51 server rudder-slapd[7888]: connection_read(15): no connection!

This happens mainly when there are no enough ldap connection in ldap.maxPoolSize

Impact seem mostly cosmetic, but it happens that it prevents a node from updating its inventory

inventory-processing - Error when trying to process report: Can't merge inventory report in LDAP directory, aborting; cause was: Exception when commiting inventory, abort.; cause was: BackendException: Error when doing action 'modify' with and LDIF change request: null; cause was: com.unboundid.ldap.sdk.LDAPException: A client-side timeout was encountered while waiting 30000ms for a response to modify request with message ID 108308 for entry 'nodeId=uuid,ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration' from server localhost:389.

Subtasks 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES over 3 years ago

To reproduce: use too much LDAP

API queries to get inventories/nodes
API search on nodes
API queries on compliance
copy inventory in /var/rudder/incoming
update node properties

all at once, massively parralel

Actions

Copy link

Updated by Nicolas CHARLES over 3 years ago

with only 2 ldap connections and even more api calls, I get the

[2021-09-20 15:44:54] ERROR nodes.pending - Error when trying to accept node ea67550f-22a4-4ca6-843f-a1e1583ead7f. Rollbacking. <- Error when executing accept node process named accept_new_server:inventory <- Error when moving node with ID 'ea67550f-22a4-4ca6-843f-a1e1583ead7f' from 'pending' to 'accepted'  <- BackendException: Error when doing action 'modify DN' with and LDIF change request: null; cause was: com.unboundid.ldap.sdk.LDAPException: A client-side timeout was encountered while waiting 30000ms for a response to modify DN request with message ID 11 for entry 'nodeId=ea67550f-22a4-4ca6-843f-a1e1583ead7f,ou=Nodes,ou=Pending Inventories,ou=Inventories,cn=rudder-configuration' from server localhost:389. 
 -> com.normation.ldap.sdk.RwLDAPConnection.$anonfun$move$2(LDAPConnection.scala:606)
 -> com.normation.ldap.sdk.RwLDAPConnection.$anonfun$applyMod$1(LDAPConnection.scala:514

Actions

Copy link