Project

General

Profile

Actions
Copy link

Defect #13114

closed

Cannot login after upgrade

Added by David Pettifor over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Accounts / authentication
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:
2.1.6

Description

Recently I patched my Ruby on Rails to 3.2.11 for Redmine 2.1.6. I have LDAP authentication for most of my users, however I cannot login with any of them. I get an internal server error, and my log looks like:

NoMethodError (undefined method `ord' for nil:NilClass):
  app/models/auth_source_ldap.rb:152:in `get_user_dn'
  app/models/auth_source_ldap.rb:43:in `authenticate'
  app/models/auth_source_ldap.rb:73:in `with_timeout'
  app/models/auth_source_ldap.rb:72:in `with_timeout'
  app/models/auth_source_ldap.rb:42:in `authenticate'
  app/models/user.rb:142:in `try_to_login'
  app/controllers/account_controller.rb:159:in `password_authentication'
  app/controllers/account_controller.rb:154:in `authenticate_user'
  app/controllers/account_controller.rb:30:in `login'

What's even more strange, is when I went to get information about my system by running:

RAILS_ENV=production script/about

This is what I get:

/usr/share/redmine/config/environments/production.rb:17: undefined method `level=' for nil:NilClass (NoMethodError)
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/railtie/configurable.rb:24:in `class_eval'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/railtie/configurable.rb:24:in `configure'
    from /usr/share/redmine/config/environments/production.rb:2
    from /usr/lib64/ruby/gems/1.8/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
    from /usr/lib64/ruby/gems/1.8/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
    from /usr/lib64/ruby/gems/1.8/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:236:in `load_dependency'
    from /usr/lib64/ruby/gems/1.8/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/engine.rb:571
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/initializable.rb:30:in `instance_exec'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/initializable.rb:30:in `run'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/initializable.rb:55:in `run_initializers'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/initializable.rb:54:in `each'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/initializable.rb:54:in `run_initializers'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/application.rb:136:in `initialize!'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/railtie/configurable.rb:30:in `send'
    from /usr/lib64/ruby/gems/1.8/gems/railties-3.2.11/lib/rails/railtie/configurable.rb:30:in `method_missing'
    from /usr/share/redmine/config/environment.rb:14
    from script/about:4:in `require'
    from script/about:4

I'm really at a loss on what's going on or how to fix it...I cannot find anything about my initial errors anywhere on the forums.

Actions
Copy link
 #1

Updated by David Pettifor over 11 years ago

I am on RHEL 6 with PostgreSQL, running Apache and passenger.

Actions
Copy link
 #2

Updated by David Pettifor over 11 years ago

I recently upgraded to the latest Redmine (2.2.2.stable.11336) with Ruby (1.8.7 (x86_64-linux)) and Rails (3.2.11). I can log in using local accounts, but when I test my LDAP authentication, I get the following error:

Unable to connect (undefined method `ord' for nil:NilClass)

I know the LDAP server is working because I also have subversion authenticate against it - and that works fine.

Actions
Copy link
 #3

Updated by David Pettifor over 11 years ago

  • Status changed from New to Resolved

Not a bug - incorrectly configured LDAP settings.

Actions
Copy link
 #4

Updated by Etienne Massip over 11 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid
Actions
Copy link

Also available in: Atom PDF