GitLab

Created by: moritzheiber

When setting up LDAP with Gitlab I encountered the following error:

(ldap) Authentication failure! ldap_error: Redis::InheritedError, Tried to use a connection from a child process without reconnecting. You need to reconnect to Redis after forking.

I suspect something is forking while trying to authenticate a user against LDAP and lateron tries to access the Redis database without having a proper handle.

Indications are that the user I was trying to login with actually seems to have been created, at least according to the log:

December 12, 2012 18:16: (LDAP) Creating user from ldap login {uid => uid=some.user,ou=people,dc=some,dc=domain, name => Some User, email => [email protected]}
December 12, 2012 18:16: User "Some User" ([email protected]) was created

However, upon closer inspection the database remains empty, except for the [email protected] user created by the setup.

My setup is fairly simple. Nothing out of the ordinary.

$ ruby -v
ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]
$ gem list --local

*** LOCAL GEMS ***

bundler (1.2.3)
charlock_holmes (0.6.9)
rake (10.0.2)
rubygems-bundler (1.1.0)
rvm (1.11.3.5)
$ redis-cli -v
redis-cli 2.6.7

Please let me know if you require any further information.