GitLab

Created by: tylux

Upgraded to 6.6.1 to 6.7 using this guide https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/6.6-to-6.7.md#3-update-gitlab-shell-and-its-config

I get a login page but when I got to login using ldap auth I get this...

500

We're sorry, but something went wrong.

Please contact your GitLab administrator if this problem persists.

my production log shows....

Started GET "/" for 127.0.0.1 at 2014-03-22 12:17:51 -0600 Processing by DashboardController#show as HTML Completed 500 Internal Server Error in 11ms

Net::LDAP::LdapError (Invalid binding information): lib/gitlab/ldap/adapter.rb:7:in open' lib/gitlab/ldap/access.rb:7:inopen' app/controllers/application_controller.rb:204:in gitlab_ldap_access' app/controllers/application_controller.rb:185:inldap_security_check' app/controllers/application_controller.rb:58:in `set_current_user_for_thread'

Started GET "/static.css" for 127.0.0.1 at 2014-03-22 12:17:52 -0600

ActionController::RoutingError (No route matches [GET] "/static.css"): vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.3/lib/action_dispatch/middleware/debug_exceptions.rb:21:in call' vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.3/lib/action_dispatch/middleware/show_exceptions.rb:30:incall' vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/rack/logger.rb:38:in call_app' vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/rack/logger.rb:20:inblock in call' vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.3/lib/active_support/tagged_logging.rb:67:in block in tagged' vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.3/lib/active_support/tagged_logging.rb:25:intagged' vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.3/lib/active_support/tagged_logging.rb:67:in tagged' vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/rack/logger.rb:20:incall' vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.3/lib/action_dispatch/middleware/request_id.rb:21:in call' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:incall' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/runtime.rb:17:in call' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/lock.rb:17:incall' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in call' vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/engine.rb:511:incall' vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/application.rb:97:in call' vendor/bundle/ruby/1.9.1/gems/railties-4.0.3/lib/rails/railtie/configurable.rb:30:inmethod_missing' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:138:in call' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/urlmap.rb:65:inblock in call' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in each' vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/urlmap.rb:50:incall' vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:552:in process_client' vendor/bundle/ruby/1.9.1/gems/unicorn-worker-killer-0.4.2/lib/unicorn/worker_killer.rb:51:inprocess_client' vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:632:in worker_loop' vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:500:inspawn_missing_workers' vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:142:in start' vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/bin/unicorn_rails:209:in<top (required)>' vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in load' vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in'

When I do an extensive check it shows LDAP authentication works no problem and shows no problems. Not sure what the issue could be