Hi all,
we still struggeling with multiple problems in our 389-ds setup.
I already opened the threads "disk i/o: very high write rates" and
"ldapsearch performance problem".
Another (the biggest) problem is, that dirsrv becomes suddenly totally
unresponsive. The server is still running, no errors in error-log - but
ldap queries are not answered and run in timeouts.
The only way is to restart it. After restart everything is fine - for a
while. But sometimes it hangs immediately again after restart.
I logged a straces while dirsrv was unresponsive:
https://nextcloud.datenkollektiv.net/s/qD8ojQZztMqbQtp
Maybe someone has an idea?
Thanks and regards.
Jan
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/message/GVPVQT4CT4VZD6F7YAKFJDFNS2PWGCVF/
No comments:
Post a Comment