From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 0184D202A2;
	Thu, 19 Oct 2017 19:05:42 +0000 (UTC)
Date: Thu, 19 Oct 2017 19:05:42 +0000
From: Eric Wong <e@80x24.org>
To: Alberto De Gaspari <a.degaspari@18months.it>
Cc: unicorn-public@bogomips.org
Subject: Re: Reaping process with unknown worker
Message-ID: <20171019190542.GA14431@whir>
References: <da4adb1c-e609-fa12-eba8-4dc4e5f6b055@18months.it>
 <20171019182050.GA11899@whir>
 <42b8a217-e2f4-e06b-77ef-c86370a00083@18months.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <42b8a217-e2f4-e06b-77ef-c86370a00083@18months.it>
List-Id: <unicorn-public.bogomips.org>

Alberto De Gaspari <a.degaspari@18months.it> wrote:
> >> Both the standard_error_logs are full of messages like the following:
> >>
> >> INFO -- : reaped #<Process::Status: pid 23835 exit 0> worker=unknown
> >>
> >> is this a misconfiguration or something similar?
> > 
> > Does your application fork processes?  It may not be reaping
> > them.   Are your normal unicorn workers dying, too?
> no, workers never dies
> > 
> > You can check the process tree or periodically run "ps" to see
> > what was running as the reaped pid before it died.
> > 
> > I use "ps axf" from the "procps" package on some Linux sytems;
> > or "pstree" if installed to see the process tree.
> > 
> i'm sorry but i don't get it.

I mean, run "ps axf" to get a list of all processes before they exit,
then check the output against the pid shown in the log when the
log entry eventually shows up.

> with a line like this in the log:
> INFO -- : reaped #<Process::Status: pid 16101 exit 0> worker=unknown
> if i run
> # ps axf |grep 16101
> i only get the ps line:
> 10277 pts/4    S+     0:00          \_ grep 16101
> 
> consider that i have loads of this line in the log, like at least 1
> every minute.
> 
> what could cause those reaps?

Reaping happens after a process exits, so it won't show up
in "ps" once it's reaped.