Eric Wong <[email protected]> wrote: > "Yeung, Jeffrey" <[email protected]> wrote: > > Sorry for the delay. It looks like disabling preload_app did the > > trick. A new master was created after sending the USR2. Now the $$$ > > question is, what in the world is intercepting the signal? :S > > Good to know, I'd just grep the installation directories for all your > Ruby libs + gems for USR2. I haven't seen this problem before, but it'd > be good to document the conflict, at least.
Btw, did you ever figure out what was causing the conflict? Pushing this out to git://bogomips.org/unicorn.git >From 1e13ffee3469997286e65e0563b6433e7744388a Mon Sep 17 00:00:00 2001 From: Eric Wong <[email protected]> Date: Tue, 20 Mar 2012 19:51:35 +0000 Subject: [PATCH] KNOWN_ISSUES: document signal conflicts in libs/apps Jeffrey Yeung confirmed this issue on the mailing list. ref: <e8d9e7ccc2621343a0a3bb45e8dedfa91c682dd...@crpmboxprd04.polycom.com> --- KNOWN_ISSUES | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/KNOWN_ISSUES b/KNOWN_ISSUES index f323c68..38263e7 100644 --- a/KNOWN_ISSUES +++ b/KNOWN_ISSUES @@ -3,6 +3,11 @@ Occasionally odd {issues}[link:ISSUES.html] arise without a transparent or acceptable solution. Those issues are documented here. +* Some libraries/applications may install signal handlers which conflict + with signal handlers unicorn uses. Leaving "preload_app false" + (the default) will allow unicorn to always override existing signal + handlers. + * Issues with FreeBSD jails can be worked around as documented by Tatsuya Ono: http://mid.gmane.org/cahbukrj09fdxagzsefjwotexw-7jyzgjmtgup_dhjpz9vbk...@mail.gmail.com _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
