ChiliProject - SystemStackError (stack level too deep)

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.

SystemStackError (stack level too deep)

Added by Wiki Bit at 2013-01-04 12:49 pm

Hi,

anyone who can help here?

I moved the install of chili to a new server, because the old one has failing hardware
I moved the databases, and all files
to be sure, I did a git fetch origin on the new server, and a checkout of version v3.3.0 again

then the usual :

bundle exec rake generate_session_store
bundle exec rake db:migrate RAILS_ENV=production
bundle exec rake db:migrate:plugins RAILS_ENV=production
bundle exec rake tmp:cache:clear
bundle exec rake tmp:sessions:clear
sudo service apache2 restart

and it seems to work, I can see the gui, check or view users, issue summary, etc.... but when I click on "view all issues", I get

Internal error

An error occurred on the page you were trying to access.
If you continue to experience problems please contact your ChiliProject administrator for assistance.

If you are the ChiliProject administrator, check your log files for details about the error.

in the browser, and I see this in the production log:

Processing IssuesController#index (for x.x.x.x at 2013-01-04 12:40:17) [GET]
  Parameters: {"category_id"=>"26", "set_filter"=>"1", "subproject_id"=>"!*", "controller"=>"issues", "action"=>"index", "project_id"=>"test"}

SystemStackError (stack level too deep):

also, I can go e.g. to the screen to create a new issue, but when I click submit, similar error

Any help would be really welcome!

Thanks

Replies (2)

RE: SystemStackError (stack level too deep) - Added by Felix Schäfer at 2013-01-04 12:52 pm

The part under "SystemStackError (stack level too deep):" would be interesting. Furthermore, did you have any plugins installed that aren't installed anymore?

RE: SystemStackError (stack level too deep) - Added by Wiki Bit at 2013-01-04 01:37 pm

Hi,

no, there are no plugins installed
and I believe I've all required gems (otherwise I would get different errors/complaints)

and the part below the "systemstackerror" ... sadly, that is empty

SystemStackError (stack level too deep):

Rendering /opt/chiliproject/public/500.html (500 Internal Server Error)

that's about it

much earlier today I had errors like this :

Processing IssuesController#index (for x.x.x.x at 2013-01-04 12:37:01) [GET]
  Parameters: {"category_id"=>"35", "set_filter"=>"1", "subproject_id"=>"!*", "controller"=>"issues", "action"=>"index", "project_id"=>"test"}

ArgumentError (wrong number of arguments (3 for 1)):
  app/controllers/issues_controller.rb:56:in `index'
  <internal:prelude>:10:in `synchronize'
  passenger (3.0.18) lib/phusion_passenger/rack/request_handler.rb:96:in `process_request'
  passenger (3.0.18) lib/phusion_passenger/abstract_request_handler.rb:516:in `accept_and_process_next_request'
  passenger (3.0.18) lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop'
  passenger (3.0.18) lib/phusion_passenger/classic_rails/application_spawner.rb:321:in `start_request_handler'
  passenger (3.0.18) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `block in handle_spawn_application'
  passenger (3.0.18) lib/phusion_passenger/utils.rb:470:in `safe_fork'
  passenger (3.0.18) lib/phusion_passenger/classic_rails/application_spawner.rb:270:in `handle_spawn_application'
  passenger (3.0.18) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop'
  passenger (3.0.18) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
  passenger (3.0.18) lib/phusion_passenger/abstract_server.rb:180:in `start'
  passenger (3.0.18) lib/phusion_passenger/classic_rails/application_spawner.rb:149:in `start'
  passenger (3.0.18) lib/phusion_passenger/spawn_manager.rb:219:in `block (2 levels) in spawn_rails_application'
  passenger (3.0.18) lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add'
  passenger (3.0.18) lib/phusion_passenger/spawn_manager.rb:214:in `block in spawn_rails_application'
  passenger (3.0.18) lib/phusion_passenger/abstract_server_collection.rb:82:in `block in synchronize'
  <internal:prelude>:10:in `synchronize'
  passenger (3.0.18) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
  passenger (3.0.18) lib/phusion_passenger/spawn_manager.rb:213:in `spawn_rails_application'
  passenger (3.0.18) lib/phusion_passenger/spawn_manager.rb:132:in `spawn_application'
  passenger (3.0.18) lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application'
  passenger (3.0.18) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop'
  passenger (3.0.18) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
  passenger (3.0.18) helper-scripts/passenger-spawn-server:99:in `<main>'

Rendering /opt/chiliproject/public/500.html (500 Internal Server Error)

but they seemed to be gone now

(1-2/2)