From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn failed to handle signals
Date: Thu, 6 Oct 2011 23:35:47 -0700 [thread overview]
Message-ID: <20111007063547.GB9790@dcvr.yhbt.net> (raw)
In-Reply-To: <EAC7D710-D4C0-4E88-96B3-3EE4C7EF1891@gmail.com>
(please don't send the same message twice in a short time period)
Andrey Cherkashin <andoriyu@gmail.com> wrote:
> I have a problem with unicorn and signals.
> FreeBSD freebsd 9.0-BETA3 FreeBSD 9.0-BETA3 #0 r225816+a1b6562: Thu Sep 29 06:46:06 PDT 2011 root@freebsd:/sys/i386/compile/XEN i386
> ruby 1.9.2p290 (2011-07-09 revision 32553) [i386-freebsd9.0]
> unicorn (4.1.1)
> Every time when I trying to send a signal (HUP, TERM, etc) I get this:
> Illegal instruction: 4 (core dumped) I have no idea how to deal with
> core dump, so here it is: http://www.misprint.org.ru/ruby.core
You can run gdb on it:
$ gdb /path/to/ruby /path/to/core
Then type "bt" to get a backtrace and you can learn other commands.
I suspect this is a bug somewhere in FreeBSD 9.0 BETA3 itself, and
not Unicorn or Ruby.
Can you test some simple scripts using trap?
Something along the lines of:
---------------------- 8< ---------------------
trap(:HUP) do
puts "HUP received"
end
puts "#$$ ready to receive SIGHUP"
sleep
------------------------------------------------
Thanks.
_______________________________________________
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
next prev parent reply other threads:[~2011-10-07 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 4:44 Unicorn failed to handle signals Andrey Cherkashin
2011-10-07 6:35 ` Eric Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-07 0:46 Andrey Cherkashin
2011-10-07 0:34 Andrey Cherkashin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111007063547.GB9790@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).