Sorry if this is the wrong place to ask, but when I run mongrel
evented using swiftiply and then send it the USR2 signal to restart
it, it dies. Without eventing, USR2 restarts mongrel as expected.
Anyone else seen this?
Here’s a dump:
$ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321
Using Evented Mongrel
** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded
$ kill -USR2 cat /tmp/m.pid
$ cat log/mongrel.log
** Daemonized, any open files are closed. Look at /tmp/m.pid and
log/mongrel.log for info.
** Starting Mongrel listening at 0.0.0.0:4321
** Starting Rails with development environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no
restart).
** Rails signals registered. HUP => reload (without restart). It
might not work well.
** Mongrel available at 0.0.0.0:4321
** Writing PID file to /tmp/m.pid
** USR2 signal received.
/opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:800:in
run': Mongrel::StopServer (Mongrel::StopServer) from /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:injoin’
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in
join' from /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:ineach’
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in
join' from /opt/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1/bin/mongrel_rails:145:inrun’
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/command.rb:211:in
run' from /opt/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1/bin/mongrel_rails:252 from /opt/local/bin/mongrel_rails:16:inload’
from /opt/local/bin/mongrel_rails:16