Redmine

I cannot reproduce on Ruby 2.1.0-p0.

But, Ruby 2.1 has some problems and Redmine does not support Ruby 2.1 officially (#16194).
I recommend you to downgrade Ruby to 2.0 or upgrade to 2.1.2.

Thanks for the quick response! Well, I downgraded to 2.0, but I still have the problem (was not able to upgrade to 2.1.2). Current versions are listed below. Any other ideas? This really puts a damper on my hopes to use Redmine. Are there known issues with p353?

Environment:
Redmine version 2.5.0.stable
Ruby version 2.0.0-p353 (2013-11-22) [x86_64-linux]
Rails version 3.2.17
Environment production
Database adapter Mysql2

For the record: I just tried Ruby 1.9.3-p484. Same problem.

I downgraded Redmine to 2.4.5.stable. Still the same problem!

I upgraded to Redmine 2.5.1.stable. I am still having the same problem. What else could it be??? Note: OS is CentOS 6.5

Update: I ran Redmine using webrick to test the issue. On webrick, I was able to delete members of groups and projects. Therefore, it must be an issue with Passenger or Apache. I will work on it from that angle. I am using Passenger version 4.0.43. Anyone know of any issues with that?

I tried a complete re-install with an older version of passenger. I re-installed Redmine. I tried all kinds of apache configurations. Same problem in all instances.

Oooh! I found something in another log! Now to find out why this is happening?

Started OPTIONS "/redmine/memberships/17" for ###.###.###.### at 2014-05-30 14:14:02 -0700

ActionController::RoutingError (No route matches [OPTIONS] "/memberships/17"):
actionpack (3.2.17) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
actionpack (3.2.17) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
railties (3.2.17) lib/rails/rack/logger.rb:32:in `call_app'
railties (3.2.17) lib/rails/rack/logger.rb:16:in `block in call'
activesupport (3.2.17) lib/active_support/tagged_logging.rb:22:in `tagged'
railties (3.2.17) lib/rails/rack/logger.rb:16:in `call'
actionpack (3.2.17) lib/action_dispatch/middleware/request_id.rb:22:in `call'
rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'
rack (1.4.5) lib/rack/runtime.rb:17:in `call'
activesupport (3.2.17) lib/active_support/cache/strategy/local_cache.rb:72:in `call'
rack (1.4.5) lib/rack/lock.rb:15:in `call'
actionpack (3.2.17) lib/action_dispatch/middleware/static.rb:63:in `call'
rack-cache (1.2) lib/rack/cache/context.rb:136:in `forward'
rack-cache (1.2) lib/rack/cache/context.rb:143:in `pass'
rack-cache (1.2) lib/rack/cache/context.rb:155:in `invalidate'
rack-cache (1.2) lib/rack/cache/context.rb:71:in `call!'
rack-cache (1.2) lib/rack/cache/context.rb:51:in `call'
railties (3.2.17) lib/rails/engine.rb:484:in `call'
railties (3.2.17) lib/rails/application.rb:231:in `call'
railties (3.2.17) lib/rails/railtie/configurable.rb:30:in `method_missing'
passenger (4.0.41) lib/phusion_passenger/rack/thread_handler_extension.rb:74:in `process_request'
passenger (4.0.41) lib/phusion_passenger/request_handler/thread_handler.rb:141:in `accept_and_process_next_request'
passenger (4.0.41) lib/phusion_passenger/request_handler/thread_handler.rb:109:in `main_loop'
passenger (4.0.41) lib/phusion_passenger/request_handler.rb:448:in `block (3 levels) in start_threads'

Interesting note--I get the above error when I am using Google Chrome, but I get no error at all when I am using Safari. I assume the above error is going to lead me to the issue. I hope.

I get the above error when I am running on a sub-URI (i.e. acme.com/redmine). When run without a sub-uri (i.e. redmine.acme.com), I have the same problem. But I get a slightly different error (though I suspect it has to do with the same problem):

Started GET "/501.shtml" for ###.###.###.### at 2014-05-30 19:22:41 -0700

ActionController::RoutingError (No route matches [GET] "/501.shtml"):
actionpack (3.2.17) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
actionpack (3.2.17) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
railties (3.2.17) lib/rails/rack/logger.rb:32:in `call_app'
railties (3.2.17) lib/rails/rack/logger.rb:16:in `block in call'
activesupport (3.2.17) lib/active_support/tagged_logging.rb:22:in `tagged'
railties (3.2.17) lib/rails/rack/logger.rb:16:in `call'
actionpack (3.2.17) lib/action_dispatch/middleware/request_id.rb:22:in `call'
rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'
rack (1.4.5) lib/rack/runtime.rb:17:in `call'
activesupport (3.2.17) lib/active_support/cache/strategy/local_cache.rb:72:in `call'
rack (1.4.5) lib/rack/lock.rb:15:in `call'
actionpack (3.2.17) lib/action_dispatch/middleware/static.rb:63:in `call'
railties (3.2.17) lib/rails/engine.rb:484:in `call'
railties (3.2.17) lib/rails/application.rb:231:in `call'
railties (3.2.17) lib/rails/railtie/configurable.rb:30:in `method_missing'
passenger (4.0.41) lib/phusion_passenger/rack/thread_handler_extension.rb:74:in `process_request'
passenger (4.0.41) lib/phusion_passenger/request_handler/thread_handler.rb:141:in `accept_and_process_next_request'
passenger (4.0.41) lib/phusion_passenger/request_handler/thread_handler.rb:109:in `main_loop'
passenger (4.0.41) lib/phusion_passenger/request_handler.rb:448:in `block (3 levels) in start_threads'

Found this issue, and learned that users are unable to UNWATCH tickets--which leads me to believe it is related to this issue (though we are not using pound).
http://www.redmine.org/boards/2/topics/40022