I agree with Mark suggestion. If new connections are failing a pstack +
error logged msg would be helpful.
Regarding the error logged. LDAP server relies on a database that, under
pressure by multiple threads, may end into a db_lock deadlock. In such
situation the DB, selects one deadlocking thread, returns a DB_Deadlock
error to that thread while the others threads continue to proceed. This
is very normal error that is caught by the server that simply retries to
access the DB. If the same thread fails to many time, it stops retry and
return a fatal error to the request.
In your case it reports code 1601 that is transient deadlock with retry.
So the impacted request just retried and likely succeeded.
On 8/24/23 14:46, Mark Reynolds wrote:
> Hi Julian,
> It would be helpful to get a pstack/stacktrace so we can see where DS
> is stuck:
> On 8/24/23 4:13 AM, Julian Kippels wrote:
>> I am using 389-ds Version 2.3.1 and have encountered the same error
>> twice in three days now. There are some MOD operations and then I get
>> a line like this in the errors-log:
>> [23/Aug/2023:13:27:17.971884067 +0200] - ERR - ldbm_back_seq -
>> deadlock retry BAD 1601, err=0 Unexpected dbimpl error code
>> After this the server keeps running, systemctl status says everything
>> is fine, but new incoming connections are failing with timeouts.
>> Any advice would be welcome.
>> Thanks in advance
>> Julian Kippels
>> 389-users mailing list -- email@example.com
>> To unsubscribe send an email to firstname.lastname@example.org
>> Fedora Code of Conduct:
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> Do not reply to spam, report it:
389-users mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
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://email@example.com
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue