-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
file:scan --all causing ldap connection lost (timeout) #26821
Comments
@jvillafanez maybe need to somehow automatically reconnect to the LDAP server after a specific time. |
Note: this issue will disappear once we have a central user table #23558 which will remove the need to connect to LDAP when iterating over all users. |
There are few choices to tackle this:
Doing rebind on some timer seems complicated and unreliable. |
There is the additional problem of LDAP pagination. Reconnecting blindly will cause issues. I think the easiest workaround would be fetch all the LDAP users and scan their files one by one. |
I am not a php person but from other interactions with ldap (python / perl) I never had problems with pagination... so unless this would be a php specific thing I can't think of a problem. |
No longer uses leap since the introduction of the account table |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
Expected behaviour
If LDAP connection is lost it should be re-initiated and whole process not dropped in the middle
Actual behaviour
It seems ldap bind is done at the beginning of scan and then search queries are executed... but if scan takes a long time connection dies in the middle and then on next user whole scan dies with following error:
Server configuration
Operating system:
Debian 8.5
Web server:
Nginx + php7.0-fpm
Database:
Postgres
PHP version:
7.0
ownCloud version: (see ownCloud admin page)
9.1.2
Updated from an older ownCloud or fresh install:
Update
Where did you install ownCloud from:
Owncloud apt repo
The text was updated successfully, but these errors were encountered: