I want to save someone the hours of investigating the problem with Capistrano + rails 2.3.(3)
The problem is that in the newest Capistrano Release (2.5.8) and below this, capistranos restart task uses the reaper script. But this and the other processes scripts is removed in rails 2.3: http://github.com/rails/rails/commit/3b3c0507e2f67a0f64dc04b396c1d13411ab5890 So you get error messages because of this. On the offiziel site i found one entry about this in the FAQ: http://www.capify.org/index.php/How_to_use_Capistrano_with_Rails_2.3 But the text is also not exact right: "... if you still use the old inspector-reaper-spawner method to run Ruby on Rails instances. " Thats wrong because even when you dont use this scripts you get error messages about it because the restart task trys to use the old scripts: task :restart, :roles => :app, :except => { :no_release => true } do try_runner "#{current_path}/script/process/reaper" end A fix for me was to overwrite this task in my project with outcommented try_runner cmd: namespace :deploy do task :restart, :roles => :app, :except => { :no_release => true } do #try_runner "#{current_path}/script/process/reaper" end end I am not sure if that fixes all issues but a simple cap deploy works no without such "reaper" errors. The other solution would be to install that plugin mentiond in the FAQ, but I think to install a Plugin which you dont need only to get rid of error messages is not the right solution. There should be an update in Capistrano that fixes that problem. If capistrano gets not updated anymore or it takes some time for a new release the dependency in gem should either set rails <2.3 to a dependency for capistrano or someone should make a gem of this irs_process plugin and set this as dependency if rails 2.3 is installed, if that is possible ;) BTW I restart my app like all howtos in the net describe the server in a own task like that: namespace :passenger do desc "Restart Application" task :restart do run "touch #{current_path}/tmp/restart.txt" end end after :deploy, "passenger:restart" Like I said in the beginning I hope I can prevent someone from hours of investigating of this problem, because I did not find any Bugreport/ Forum-entry with someone else having that problem or a fix to it. Is nobody using Capistrano anymore or does nobody updates to Rails 2.3? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
