diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-05 09:08:43 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-05 09:08:43 +0000 |
commit | 26384c9a61da9922b8fa4b8351d4e42d51661b37 (patch) | |
tree | ef3decbed644db3c97dcdbb5b71d4ade77f3155d /doc/administration/auth | |
parent | 79cbe31b18159ea394c6f6e3027c1dc69bdabb75 (diff) | |
download | gitlab-ce-26384c9a61da9922b8fa4b8351d4e42d51661b37.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/auth')
-rw-r--r-- | doc/administration/auth/ldap.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/administration/auth/ldap.md b/doc/administration/auth/ldap.md index 6f6c2e0068e..339710624fa 100644 --- a/doc/administration/auth/ldap.md +++ b/doc/administration/auth/ldap.md @@ -609,3 +609,16 @@ Could not authenticate you from Ldapmain because "Connection timed out - user sp If your configured LDAP provider and/or endpoint is offline or otherwise unreachable by GitLab, no LDAP user will be able to authenticate and log in. GitLab does not cache or store credentials for LDAP users to provide authentication during an LDAP outage. Contact your LDAP provider or administrator if you are seeing this error. + +### No file specified as Settingslogic source + +If `sudo gitlab-ctl reconfigure` fails with the following error, or you are seeing it in +the logs, you may have malformed YAML in `/etc/gitlab/gitlab.rb`: + +```plaintext +Errno::ENOENT: No such file or directory - No file specified as Settingslogic source +``` + +This issue is frequently due to the spacing in your YAML file. To fix the problem, +verify the syntax with **spacing** against the +[documentation for the configuration of LDAP](#configuration). |