Update from the trenches: I've traced this down to the newrelic_rpm agent Noticed this is not the 1st time this has been brought up, since newrelic spins up the stats collector in its own thread.
Attempted the (old) logger mutex monkeypatch mentioned in the unicorn docs without luck. Noodled with various permutations of NewRelic::Agent.shutdown in before/after_fork without success. NewRelic apparently has some compat issues with bundler, but that didn't affect it, nor did switching to the plugin. I'm running the latest newrelic_rpm agent (2.11.2) and the latest unicorn (0.97.1). I imagine this is contention over its logfile. Is there any low-hanging fruit I should try? I've also filed a bug with NewRelic: http://support.newrelic.com/discussions/support/2577-newrelic-agentbundler-causing-stillborn-unicorn-processes?unresolve=true -jamie On Apr 19, 2010, at 11:21 AM, Eric Wong wrote: > Hi Jamie, any more news on this issue? I plan on doing a minor release > later today or tomorrow with a few minor bug fixes in unicorn.git > > -- > Eric Wong _______________________________________________ Unicorn mailing list - mongrel-unicorn@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
