ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Internal server error for LDAP actions with 2.6.0 (Bug #818)
Description
I've (stupidly) updated my ChiliProject 2.5 production server to the current 2.6.0 version - which has a critical bug inside the LDAP code:
Since the update it's not possible to login via LDAP or open any LDAP configuration page ("New LDAP Controller" or "Edit LDAP Controller") - while the LDAP connection test still works.
To prevent getting lynched by my colleagues (because nobody can login anymore), I'll try to restore the old 2.5.0 version.
Here the production.log
for the action "New LDAP Controller":
Processing LdapAuthSourcesController#new (for 192.168.10.30 at 2012-01-05 15:18:13) [GET] Parameters: {"action"=>"new", "controller"=>"ldap_auth_sources"} Rendering template within layouts/admin Rendering auth_sources/new ActionView::TemplateError (undefined method `custom_filter' for #<AuthSourceLdap:0xb5c2ce90>) on line #30 of app/views/ldap_auth_sources/_form.rhtml: 27: <%= check_box 'auth_source', 'onthefly_register' %></p> 28: 29: <p><label for="auth_source_custom_filter"><%=l(:field_custom_filter)%></label> 30: <%= text_field 'auth_source', 'custom_filter', :size => 60 %></p> 31: </div> 32: 33: <fieldset class="box"><legend><%=l(:label_attribute_plural)%></legend> app/views/ldap_auth_sources/_form.rhtml:30:in `_run_rhtml_app47views47ldap_auth_sources47_form46rhtml_locals_form_object' app/views/auth_sources/new.rhtml:4:in `_run_rhtml_app47views47auth_sources47new46rhtml' app/views/auth_sources/new.rhtml:3:in `_run_rhtml_app47views47auth_sources47new46rhtml' app/controllers/auth_sources_controller.rb:31:in `new' /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:92:in `process_request' /usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:in `main_loop' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:418:in `start_request_handler' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:358:in `handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:in `safe_fork' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:354:in `handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:163:in `start' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:213:in `start' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:80:in `synchronize' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:154:in `spawn_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously' /usr/lib/phusion_passenger/passenger-spawn-server:61 Rendering /var/chiliproject-git/public/500.html (500 Internal Server Error)
Any hints/help are appreciated - I'll try to support debugging this error as far as I can (and if I'm not lynched in between).
History
Updated by Chris Dähn at 2012-01-05 02:37 pm
I luckily work with the git repository of ChiliProject stable and managed to checkout the 2.5.0, which works well again.
For tests/debuggin I'm able to switch to the buggy 2.6.0 version very fast.
Updated by Felix Schäfer at 2012-01-05 02:54 pm
Have you run the database migrations when you upgraded to 2.6?
Updated by Chris Dähn at 2012-01-05 03:16 pm
Oh, ups. What a pity.
I missed the documented steps for the last updates, which seemed to work curiously enough :)
Following the upgrade docs solved the problem.
Thanks for the extremely fast reply!
Ach ja: Und Frohes Neues Felix!
ciao,
Chris
- Status changed from Open to Closed