500 Internal Error

rubyonrails-talk
#1

I have on ubuntu a digital library application Kete which gives in the
log/production.log:

Please help, thnx.

/!\ FAILSAFE /!\ Fri Feb 05 19:05:08 +0200 2010
  Status: 500 Internal Server Error
  No connection to server (localhost:11211 DEAD (Errno::ECONNREFUSED:
Connection refused - connect(2)), will retry at Fri Feb 05 19:05:38
+0200 2010)
    /usr/local/lib/ruby/gems/1.8/gems/memcache-client-1.7.7/lib/
memcache.rb:855:in `with_socket_management'
    /usr/local/lib/ruby/gems/1.8/gems/memcache-client-1.7.7/lib/
memcache.rb:732:in `cache_get'
    /usr/local/lib/ruby/gems/1.8/gems/memcache-client-1.7.7/lib/
memcache.rb:253:in `get'
    /usr/local/lib/ruby/gems/1.8/gems/memcache-client-1.7.7/lib/
memcache.rb:878:in `with_server'
    /usr/local/lib/ruby/gems/1.8/gems/memcache-client-1.7.7/lib/
memcache.rb:251:in `get'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
session/mem_cache_store.rb:61:in `initialize'
    /usr/local/lib/ruby/1.8/cgi/session.rb:280:in `new'
    /usr/local/lib/ruby/1.8/cgi/session.rb:280:in
`initialize_without_cgi_reader'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
cgi_ext/session.rb:39:in `initialize'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
cgi_process.rb:132:in `new'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
cgi_process.rb:132:in `session'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
cgi_process.rb:168:in `stale_session_check!'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
cgi_process.rb:116:in `session'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
base.rb:1139:in `assign_shortcuts_without_flash'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
flash.rb:166:in `assign_shortcuts'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
base.rb:523:in `process_without_filters'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
filters.rb:568:in `process_without_session_management_support'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
session_management.rb:130:in `process'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
base.rb:389:in `process'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
dispatcher.rb:149:in `handle_request'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
dispatcher.rb:107:in `dispatch'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
dispatcher.rb:104:in `synchronize'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
dispatcher.rb:104:in `dispatch'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
dispatcher.rb:120:in `dispatch_cgi'
    /home/kete/apps/kato/vendor/rails/actionpack/lib/action_controller/
dispatcher.rb:35:in `dispatch'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/railz/request_handler.rb:50:in `process_request'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/railz/application_spawner.rb:378:in
`start_request_handler'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/railz/application_spawner.rb:336:in
`handle_spawn_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/utils.rb:183:in `safe_fork'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/railz/application_spawner.rb:334:in
`handle_spawn_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:352:in `__send__'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:352:in `main_loop'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:196:in `start_synchronously'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:163:in `start'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/railz/application_spawner.rb:213:in `start'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
      /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/spawn_manager.rb:154:in `spawn_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:352:in `__send__'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:352:in `main_loop'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/
phusion_passenger/abstract_server.rb:196:in `start_synchronously'
    /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-
spawn-server:61

#2

Looks like your app is trying to use memcache but it couldn't talk to
the memcache server.

Fred

#3

Hello,
       As per your post, i think you are trying to run application on
the already used port. so try to use some alternate port and try to run
application.

#4

Hi Fred,

I can't telnet localhost 112111 either. I will dig in and notify what
happened. Thank you for the prompt suggestion

Ahmet

#5

By the adventrous KETE installation on Ubuntu server, 500 error is
gone, but I'm missing still some crucial intallation steps (?) Upon
ruby script/server command the server generates the following error.
The development database is empty. I entered in to basket table just a
dummy name.

Thanks being patient with me.

#6

By the adventrous KETE installation on Ubuntu server, 500 error is
gone, but I'm missing still some crucial intallation steps (?) Upon
ruby script/server command the server generates the following error.
The development database is empty. I entered in to basket table just a
dummy name.

Thanks being patient with me.
----------------------------------------------------------------
=> Booting WEBrick...
Rails Error: Unable to access log file. Please ensure that /home/kete/
apps/
kato/
log/development.log exists and is chmod 0666. The log level has been
raised to
W
ARN and the output directed to STDERR until the problem is fixed.