Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 500 accessing an equipment. #58

Open
zordor opened this issue Nov 26, 2013 · 1 comment
Open

Error 500 accessing an equipment. #58

zordor opened this issue Nov 26, 2013 · 1 comment
Labels

Comments

@zordor
Copy link

zordor commented Nov 26, 2013

When I access one test equipment we created from my browser at my computer it works great, here is the log (my username has been modified):

Started GET "/redmine/ci/1" for 202.94.145.1 at Tue Nov 26 11:53:06 +0900 2013
Processing by AssetCheckInsController#new as HTML
Parameters: {"equipment_asset_id"=>"1"}
Current user: user.name (id=125)
Rendered plugins/redmine_equipment_status_viewer/app/views/asset_check_ins/new.html.erb within layouts/base (4.5ms)
Rendered plugins/clipboard_image_paste/app/views/clipboard_image_paste/_headers.html.erb (1.0ms)
Rendered plugins/clipboard_image_paste/app/views/clipboard_image_paste/_add_form.html.erb (1.6ms)
Completed 200 OK in 156ms (Views: 146.1ms | ActiveRecord: 1.3ms)
Started GET "/redmine/plugin_assets/redmine_equipment_status_viewer/javascripts/autocomplete.js" for 202.94.145.1 at Tue Nov 26 11:53:06 +0900 2013

ActionController::RoutingError (No route matches [GET] "/plugin_assets/redmine_equipment_status_viewer/javascripts/autocomplete.js"):
actionpack (3.2.13) lib/action_dispatch/middleware/debug_exceptions.rb:21:in call' actionpack (3.2.13) lib/action_dispatch/middleware/show_exceptions.rb:56:incall'
railties (3.2.13) lib/rails/rack/logger.rb:32:in call_app' railties (3.2.13) lib/rails/rack/logger.rb:16:incall'
activesupport (3.2.13) lib/active_support/tagged_logging.rb:22:in tagged' railties (3.2.13) lib/rails/rack/logger.rb:16:incall'
actionpack (3.2.13) lib/action_dispatch/middleware/request_id.rb:22:in call' rack (1.4.5) lib/rack/methodoverride.rb:21:incall'
rack (1.4.5) lib/rack/runtime.rb:17:in call' activesupport (3.2.13) lib/active_support/cache/strategy/local_cache.rb:72:incall'
rack (1.4.5) lib/rack/lock.rb:15:in call' actionpack (3.2.13) lib/action_dispatch/middleware/static.rb:63:incall'
rack-cache (1.2) lib/rack/cache/context.rb:136:in forward' rack-cache (1.2) lib/rack/cache/context.rb:245:infetch'
rack-cache (1.2) lib/rack/cache/context.rb:185:in lookup' rack-cache (1.2) lib/rack/cache/context.rb:66:incall!'
rack-cache (1.2) lib/rack/cache/context.rb:51:in call' railties (3.2.13) lib/rails/engine.rb:479:incall'
railties (3.2.13) lib/rails/application.rb:223:in call' railties (3.2.13) lib/rails/railtie/configurable.rb:30:insend'
railties (3.2.13) lib/rails/railtie/configurable.rb:30:in method_missing' passenger (3.0.19) lib/phusion_passenger/rack/request_handler.rb:96:inprocess_request'
passenger (3.0.19) lib/phusion_passenger/abstract_request_handler.rb:516:in accept_and_process_next_request' passenger (3.0.19) lib/phusion_passenger/abstract_request_handler.rb:274:inmain_loop'
passenger (3.0.19) lib/phusion_passenger/classic_rails/application_spawner.rb:321:in start_request_handler' passenger (3.0.19) lib/phusion_passenger/classic_rails/application_spawner.rb:275:insend'
passenger (3.0.19) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in handle_spawn_application' passenger (3.0.19) lib/phusion_passenger/utils.rb:470:insafe_fork'
passenger (3.0.19) lib/phusion_passenger/classic_rails/application_spawner.rb:270:in handle_spawn_application' passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:insend'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in server_main_loop' passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:206:instart_synchronously'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:180:in start' passenger (3.0.19) lib/phusion_passenger/classic_rails/application_spawner.rb:149:instart'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:219:in spawn_rails_application' passenger (3.0.19) lib/phusion_passenger/abstract_server_collection.rb:132:inlookup_or_add'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:214:in spawn_rails_application' passenger (3.0.19) lib/phusion_passenger/abstract_server_collection.rb:82:insynchronize'
passenger (3.0.19) lib/phusion_passenger/abstract_server_collection.rb:79:in synchronize' passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:213:inspawn_rails_application'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:132:in spawn_application' passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:275:inhandle_spawn_application'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in __send__' passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:inserver_main_loop'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
passenger (3.0.19) helper-scripts/passenger-spawn-server:99

But when I try to the same from safari or chrome at my iphone I get a error 500, with this output in the logs:

Started GET "/redmine/ci/1" for 49.98.141.43 at Tue Nov 26 11:56:24 +0900 2013
Processing by AssetCheckInsController#new as HTML
Parameters: {"equipment_asset_id"=>"1"}
Current user: user.name (id=125)
Rendered plugins/redmine_equipment_status_viewer/app/views/asset_check_ins/new_iphone.html.erb within layouts/equipment_status_viewer_mobile (1.3ms)
Completed 500 Internal Server Error in 8ms

ActionView::Template::Error (undefined method upcase' for 114:Fixnum): 4: 5: <% content_for :page_header do %> 6: <h1><%= t :lable_chek_plural %></h1> 7: <%= edit_button_for @equipment_asset %> 8: <% end %> 9: 10: <h3><%= t :check_in_for, :asset => @equipment_asset.name %></h3> app/helpers/application_helper.rb:1145:incontent_for'

Is this a bug or am I doing something wrong? We are using a self-signed certificate, could this be part of the problem?

Thank you!

@sukima
Copy link
Owner

sukima commented Nov 26, 2013

I'm pretty sure this has been a long outstanding bug. It's unfortunate but I no long have the resources to continue maintaining this project and am hoping others are willing to step up and help fix bugs. Pull requests are always addressed with gusto!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants