-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP error when indexing many files #175
Comments
I get exactly the same error message with the following setup:
This is the output I'm getting:
EDIT: My Nextcloud instance connects to two different ldap servers(Active Directory and FreeIPA), if i disable one of them(doesn't matter which one) the index gets created without any problems. But when I try to create the index with both ldap connections enabled i get the error message from above. |
Can you try this patch for NC11 ? |
Since I already updated my nextcloud to version 12 I can't apply this patch anymore. But with the update the issue disappeared and the index creation finishes successfully! |
I linked the backport to NC11. This is the patch for NC12: nextcloud/server#5104 |
Tested patch with nextcloud 11.0.3: No more exception -> works. Thanks! |
While trying to index quite some files (~145k) with nextant, I always get the following error after all files were processed (which takes > 20h).
It looks like the (time consuming) data crawling part is finished when this happens, however the status seems to be not committed, as on restart the whole indexing process starts anew from the beginning.
The bug is obviously LDAP related, so I tried to increase the LDAP timeout limit (from 15s default to 120s) but this did not help either.
My setup:
LDAP server is Samba 4.6.2 (domain controller mode).
The text was updated successfully, but these errors were encountered: