Can anyone shed any light on why “reaper” (whilst seemingly working re
restarting my mongrel ruby process) does not pick up changes to my
application? (e.g. changing a title in a view for example). It’s like
“mongrel_rails start etc…” is just restarting the current process but
ignoring the new details re where the new application directory is.
is with capistrano the new releases are put in different directories,
are referenced in the command line options to “mongrel_rails”, however
seems these are being picked up. I basically have to do a “reaper -a
kill” and then a “nohup script/spin” to get it to recognize the new
Here’s an example of the scenario when I run reaper, the ruby processes
restarted, but it doesn’t pick up the new directory (i.e. application
– CONSOLE OUTPUT —
[root@home ~]# cd /u/apps/equity/current/
[root@home current]# ./script/process/reaper
– MONGREL LOG EXTRACT –
** USR2 signal received.
** Restarting with arguments: ruby
-a 0.0.0.0 -p 3001 -P
production -c /u/apps/equity/releases/20090209050120 -l
** Daemonized, any open files are closed. Look at
/u/apps/equity/releases/20090209050120/log/mongrel.log for info.
** Starting Mongrel listening at 0.0.0.0:3001
** Starting Rails with production environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no
** Rails signals registered. HUP => reload (without restart). It might
** Mongrel 1.1.5 available at 0.0.0.0:3001
** Writing PID file to