gunicorn icon indicating copy to clipboard operation
gunicorn copied to clipboard

More verbose exit logging

Open tilgovi opened this issue 4 years ago • 6 comments

  • Add logging at error level for abnormal worker exit codes.
  • Make arbiter shutdown log at error level for abnormal exits.

tilgovi avatar Apr 21 '20 02:04 tilgovi

I installed gunicorn from this branch, but I dont see below in logs, note: I am running gunicorn with DEBUG log level

'Worker (pid:%s) exited with code %s'

but I do see

Out of memory: Kill process 14666 (gunicorn) score 319 or sacrifice child

in dmesg in debian buster container

nakulcg avatar May 28 '20 07:05 nakulcg

@benoitc any changes you still want here? I responded to your earlier feedback.

tilgovi avatar Dec 31 '20 16:12 tilgovi

Bump, I'd really like to see this merged.

kosciCZ avatar Jan 22 '21 16:01 kosciCZ

@benoitc can you please take another look at this one?

tilgovi avatar Jan 24 '21 03:01 tilgovi

Hello, this would be useful for us too :)

harto avatar Aug 10 '21 22:08 harto

@tilgovi Should it pass the exitcode to child_exit function? This will give client more flexibility to play around. In my case I would like to log the exitcode as well as based on certain logic also predict if it is OOM or not. Also I like the proposal to add the exit code to worker.

sp1rs avatar Mar 29 '22 10:03 sp1rs