Sunday, January 21, 2024

[389-users] 389ds connection not successful


I use FreeIPA and encountered a 389ds connection problem when new hosts was added to FreeIPA server with the rate of 14 hosts per min.
I don't know how many times FreeIPA server actually accesses LDAP in this scenario.
Can you give us advice to resolve my problem, with regard to following logs?
I'd like to find out configuration to fix this error.

access log
[18/Jan/2024:23:34:13.087718471 +0000] conn=788 fd=258 slot=258 connection from to
[18/Jan/2024:23:34:13.088018506 +0000] conn=788 op=0 EXT
oid="" name="start_tls_plugin"
[18/Jan/2024:23:34:13.088053934 +0000] conn=788 op=0 RESULT err=0 tag=120 nentries=0
wtime=0.000228592 optime=0.000040018 etime=0.000268106
[18/Jan/2024:23:34:13.158931686 +0000] conn=788 TLS1.3 128-bit AES-GCM
[18/Jan/2024:23:34:13.159223459 +0000] conn=788 op=-1 fd=258 Disconnect - Bad Ber Tag or
uncleanly closed connection - B1

security log
{ "date": "[18\/Jan\/2024:23:34:13.159227408 +0000] ",
"utc_time": "1705620853.159227408", "event":
"TCP_ERROR", "client_ip": "",
"server_ip": "", "ldap_version": 3,
"conn_id": 788, "msg": "Bad Ber Tag or uncleanly closed
connection - B1" }

I tested with FreeIpa fedora-39-4.11.0 docker with the recent version of 389ds.

ldapsearch -V
ldapsearch: @(#) $OpenLDAP: ldapsearch 2.6.6 (Jul 31 2023 00:00:00) $

Thank you.
389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

No comments:

Post a Comment