Project

General

Profile

Actions
Copy link

Bug #19980

closed

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

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

Added by Nicolas CHARLES about 4 years ago. Updated almost 4 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:
0
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)

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

Also available in: PDF Atom