From e795d82eef8d7a25c1209d68966b11fe3812a7a0 Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Mon, 11 Jul 2016 12:22:05 +0000 Subject: [PATCH] Include timeout error troubleshooting --- doc/administration/auth/ldap.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/administration/auth/ldap.md b/doc/administration/auth/ldap.md index 0410da34733c29..040767ba719dce 100644 --- a/doc/administration/auth/ldap.md +++ b/doc/administration/auth/ldap.md @@ -315,3 +315,15 @@ If you are getting 'Connection Refused' errors when trying to connect to the LDAP server please double-check the LDAP `port` and `method` settings used by GitLab. Common combinations are `method: 'plain'` and `port: 389`, OR `method: 'ssl'` and `port: 636`. + +### Timeout error + +If active directory has nested groups timeouts may be experienced when enumerating LDAP groups. The symptoms are "LDAP search timed out after" errors in the `production.log` + +1. Look for a timeout error `LDAP search timed out after` in `production.log` + + ``` + grep 'LDAP search timed out after' /var/log/gitlab/gitlab-rails/production.log + ``` + +1. Increase the `timeout` value in the LDAP settings - e.g `timeout: 90` -- GitLab