Hello,
This error is logged when the server fails to send back data
(entry/result) to the ldap client. It may happen when a client is too
slow to read the response (large number of entries) or is not reading at
all or if there is a network issue. Then after some time, defined by
nsslapd-ioblocktimeout the server disconnect the connection. You may
increase ioblocktimeout but with the risk that "lazy" clients will
consume all the DS workers.
To know which client (connection) you may look at the access log and see
what connection get closed when the 'Time out' occurs. Then looking at
the connection opening record/bind (access log) try to identify the
problematic clients.
regards
thierry
On 8/15/25 8:18 PM, Ghiurea, Isabella via 389-users wrote:
Hello List,
We are running a old ldap version:389-ds-base-1.3.7.5-24.el7_5.x86_64
and seeing the following error in ldap logs every couple of secs . A
389-ldap reboot did not help , where we shall look next ? ( this is a
slave read-only ldap cfg master-slave replication)
Also is there a way t find which connections is generating this
errorm in top of ldap we have l/b ( load balancer)
:11:11:08.497659877 -0700] - ERR - slapd_poll - (166) - Timed out
:11:11:11.597441065 -0700] - ERR - slapd_poll - (235) - Timed out
thank you !
--
_______________________________________________
389-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
