Alberto De Gaspari <a.degasp...@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. -- unsubscribe: unicorn-public+unsubscr...@bogomips.org archive: https://bogomips.org/unicorn-public/
