liang fei via FreeIPA-users wrote: > The 389ds service has crashed due to a pthread_mutex_lock. > Environment: Ubuntu 16.04, FreeIPA 4.3, 389-Directory/1.3.4.9 B2016.109.158 > Trigger condition: When Ambari operation concurrently adds five nodes, a new > Hadoop keytab file will be added. The 389ds service with a large number of > krb clients for authentication and adding service keytab to 389ds Replication > will deadlock, > while the 389ds service without krb client login is normal. Therefore, this > is a pthread_mutex_lock issue of (krb client -> search 389ds) + (add krb > service -> 389ds data replica). I understand that Berkeley Database (bdb) has > many problems, > according to this document: > https://www.port389.org/docs/389ds/howto/howto-use-lmdb.html. But I don't > understand why the freeipa 4.3 version is so fragile? My current environment > is reproducible. > Only when adding krb service keytab nodes in batches will it crash. How can I > solve this problem in a lightweight way without upgrading the version or > replacing bdb? > My current solution is to kill ns-slapd and then start-dirsrv. > > 389ds crashed logs
I'd suggest you reach out to the 389-ds project directly. It's possible that one of the developers will notice it here but you can reach them directly at [email protected]. I doubt the issue is related to bdb vs lmdb. But in the end you're running software released 11 years ago. rob -- _______________________________________________ FreeIPA-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.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
