Project

General

Profile

500 error when accessing issue list

Added by Boudewijn van Liempd over 15 years ago

Hi since upgrading this morning I get internal 500 errors when clicking on pre-defined filters for the issue list. I have no idea where to start looking. the log gives me:

Processing IssuesController#index (for xxx.xxx.xxx.xxx at 2009-03-30 08:51:30) [GET]
Parameters: {"project_id"=>"pp2008", "action"=>"index", "controller"=>"issues"}

ArgumentError (wrong number of arguments (6 for 5)):
/app/models/query.rb:338:in `sql_for_field'
/app/models/query.rb:338:in `statement'
/app/models/query.rb:320:in `each_key'
/app/models/query.rb:320:in `statement'
/app/controllers/issues_controller.rb:59:in `index'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/base.rb:1253:in `send'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/base.rb:1253:in `perform_action_without_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/filters.rb:617:in `call_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/rescue.rb:136:in `perform_action_without_caching'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/active_record/query_cache.rb:8:in `cache'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/base.rb:524:in `send'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/base.rb:524:in `process_without_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/filters.rb:606:in `process_without_session_management_support'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/session_management.rb:134:in `process'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/base.rb:392:in `process'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:183:in `handle_request'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:123:in `dispatch'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:122:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:122:in `dispatch'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/dispatcher.rb:39:in `dispatch'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:101:in `process_request'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:151:in `with_signal_handler'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:99:in `process_request'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:76:in `process_each_request'
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:75:in `process_each_request'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:74:in `catch'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:74:in `process_each_request'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:49:in `process!'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/fcgi_handler.rb:23:in `process!'
/public/dispatch.fcgi:24

Rendering /data/webroot/boudewijn.biz/redmine/public/500.html (500 Internal Server Error)


Replies (4)

RE: 500 error when accessing issue list - Added by Boudewijn van Liempd over 15 years ago

I've found that the error only occurs when filtering on custom fields, if only standard redmine fields are used it works normally.

RE: 500 error when accessing issue list - Added by Boudewijn van Liempd over 15 years ago

further more after some searching I fond it has to do with the question plugin and current version from trunk. After disabling the plugin the issue no longer exists.

RE: 500 error when accessing issue list - Added by Mischa The Evil over 15 years ago

Boudewijn van Liempd wrote:

further more after some searching I fond it has to do with the question plugin and current version from trunk. After disabling the plugin the issue no longer exists.

Without further info I'd say you've missed an update of the Questions plugin (0.3.0, see http://theadmin.org/articles/2009/3/11/redmine-question-plugin-v0-3-0-released) which should solve compatibility issues with current Redmine trunk.
I've been doing some quick tests with it on Redmine trunk at r2641 and have not experienced any problems with it...

If this does not solve your issues please post with some more info (see Submissions)...

RE: 500 error when accessing issue list - Added by Brad Lang over 15 years ago

I've experienced the same problem with the same error trace when attempting to filter issues based on a custom field - reproduced on two installations.
Removing the Question plugin also solved the issue.

Question plugin: 0.3.0
Redmine: r2760 and r2630

    (1-4/4)