# Evented mongrel dies on USR2

**URL:** <https://www.ruby-forum.com/t/evented-mongrel-dies-on-usr2/118577>\
**Category:** Mongrel\
**Created:** [October 29, 2007, 4:54am UTC](https://www.ruby-forum.com/t/evented-mongrel-dies-on-usr2/118577 "2007-10-29T04:54:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [October 29, 2007, 4:54am UTC](https://www.ruby-forum.com/t/evented-mongrel-dies-on-usr2/118577/1 "2007-10-29T04:54:47Z")

</div>

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:in`join’  
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:in`each’  
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:in`run’  
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:in`load’  
from /opt/local/bin/mongrel\_rails:16

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [October 29, 2007, 5:32am UTC](https://www.ruby-forum.com/t/evented-mongrel-dies-on-usr2/118577/2 "2007-10-29T05:32:45Z")

</div>

On 10/29/07, Eden Li [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> 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.

50/50, since evented\_mongrel is a live patch of what mongrel is supposed  
to do.  
Even that is mongrel in the back running, the people who created  
Evented (Kirk?) should came with a solution for this.

Maybe that was one of the things that remain unpatched?

## – Luis L. Multimedia systems

Leaders are made, they are not born. They are made by hard effort,  
which is the price which all of us must pay to achieve any goal that  
is worthwhile.  
Vince Lombardi