Charles Hornberger <[email protected]> wrote: > Hi! > > I recently noticed this error message when restarting unicorn after a > code deployment (and I don't think I recall having seen it before): > > I, [2013-01-18T17:54:21.502554 #59285] INFO -- : reaped > #<Process::Status: pid 59293 exit 0> worker=6 > I, [2013-01-18T17:54:21.502692 #59285] INFO -- : reaped > #<Process::Status: pid 59294 exit 0> worker=7 > I, [2013-01-18T17:54:21.502754 #59285] INFO -- : reaped > #<Process::Status: pid 59292 exit 0> worker=5 > I, [2013-01-18T17:54:21.502819 #59285] INFO -- : reaped > #<Process::Status: pid 59291 exit 0> worker=4 > E, [2013-01-18T17:54:21.502915 #59285] ERROR -- : reaped > #<Process::Status: pid 59288 SIGSEGV (signal 11)> worker=1 > I, [2013-01-18T17:54:21.502967 #59285] INFO -- : reaped > #<Process::Status: pid 59287 exit 0> worker=0 > I, [2013-01-18T17:54:21.604829 #59285] INFO -- : reaped > #<Process::Status: pid 59290 exit 0> worker=3 > I, [2013-01-18T17:54:21.604935 #59285] INFO -- : reaped > #<Process::Status: pid 59289 exit 0> worker=2 > 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? Which C extensions do you have loaded? What at_exit/END handlers does your app have? What finalizers does your have? Probably not a major issue as long as you don't have SEGVs at normal runtime, but still annoying to see. IIRC, there have been a couple of these bugs fixed by ruby-core over the years. _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
