Bug 53601 – Import of large ldif via LDAPI:// may fail

Bug 53601 - Import of large ldif via LDAPI:// may fail


Summary:	Import of large ldif via LDAPI:// may fail

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 minor (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-07-21 11:53 CEST by Arvid Requate
Modified:	2021-08-10 01:38 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2021-07-21 11:53:11 CEST

When importing a large ldif via LDAPI:// the import can abort like this:

# ldapmodify -x -H ldapi:// -f example.ldif 
modifying entry "cn=foo,ou=bar,dc=mydom,dc=com"
ldapmodify: update failed: cn=foo,ou=bar,dc=mydom,dc=com
ldap_modify: Can't contact LDAP server (-1)

In this case it was necessary to temporarily increase sockbuf_max_incoming (as the connection is anonymous). Please be aware that this increases the possibility of DoS attacks, so it should only be a temporary measure.

The purpose of this bug is mainly to document the knowledge for others running into this issue. We could additionally make sockbuf_max_incoming/sockbuf_max_incoming_auth configurable in slapd.conf to simplify this.