Project

General

Profile

Actions

Bug #19980

closed

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

Added by Nicolas CHARLES 9 months ago. Updated 6 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0

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 open1 closed)

Bug #19983: document ldap connection quantity, and scalability of RudderReleasedAlexis MoussetActions
Actions #1

Updated by Nicolas CHARLES 9 months 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 #2

Updated by Nicolas CHARLES 9 months 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 #3

Updated by Nicolas CHARLES 9 months ago

Workaroud: adding connexions allows the error to not happen anymore

Actions #4

Updated by Nicolas CHARLES 9 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #5

Updated by Nicolas CHARLES 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/3893
Actions #6

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #7

Updated by Nicolas CHARLES 7 months ago

  • Status changed from Pending technical review to Pending release
Actions #9

Updated by Vincent MEMBRÉ 6 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.18, 6.2.12 and 7.0.0~rc2 which were released today.

Actions

Also available in: Atom PDF