Eric Wong <[email protected]> wrote: > It seems io.close in the trap(:QUIT) handler of the worker process is > causing an IOError, which means an IO in the readers array already got > closed somehow. This shouldn't happen, and CRuby 2.x doesn't seem > to interrupt itself inside signal handlers[1].
Of course, the fake-signal mechanism of 4.8.0 could also cause this: * the master triggers a fake-signal (where the invoked trap handler is interruptible) * a real signal also triggered from an outside user I forget to mention this happened with unicorn-worker-killer 0.4.2 for that user, and that seems to just use normal Process.kill _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
