On Thu, Jan 24, 2013 at 10:52 AM, Eric Wong <[email protected]> wrote: > Charles Hornberger <[email protected]> wrote: >> On Mon, Jan 21, 2013 at 11:28 AM, Eric Wong <[email protected]> wrote: >> > Charles Hornberger <[email protected]> wrote: >> >> E, [2013-01-18T17:54:21.502915 #59285] ERROR -- : reaped >> >> #<Process::Status: pid 59288 SIGSEGV (signal 11)> worker=1 > > <snip> > >> >> I, [2013-01-18T17:54:21.605077 #59285] INFO -- : master complete >> >> >> >> Just wondering if it's something I should be concerned about? I saw no >> >> obvious symptoms of problems before or after… >> >> >> >> We currently restart unicorn (which is on a freebsd jail) like so: >> > >> > A SEGV at shutdown is likely an ordering problem at VM shutdown >> > (probably GC/finalization handling). It could be specific to the >> > malloc/pthread implementation on FreeBSD, even. >> > >> > Which version of Ruby are you using? >> >> 1.9.3p-125 > > Can you give 1.9.3-p374 a try? There were several GC-related segfault > fixes along the way (fairly large and drastic changes, even).
We'll be moving to that soon. Since the problem has only occurred *once* afaik, and there was nothing special that I can think of to do to reproduce it, we may never know if the change fixed anything. :) But if I happen to see it again, I will attempt to provide more info. > > <snip> > > Also, did you manage to get any backtrace from Ruby at all? The Ruby VM > should show a partial stack trace on SEGV (or at least attempt to, but > it may not during shutdown). Otherwise, you'd have to get gdb-able core > dumps the old-fashioned way (ulimit -c unlimited) and show us (or > ruby-core) the backtrace. Nothing was emitted at the time -- what I sent before was all that appeared in stderr.log. _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
