App get killed, no code changes and now its killed (using gunicorn)

1

Almost no changed code in the past weeks and I see now this kind of issues in “MAD” instance. Dont know whats is happening. (no db or cache its used)

[CRITICAL] WORKER TIMEOUT (pid:282)
[INFO] Worker exiting (pid: 282)
Worker with pid 282 was terminated due to signal 9
Booting worker with pid: 286

Using
gunicorn==20.1.0

Procfile
web: gunicorn app:app

Already even try to update machine (never was required before) rising to cpux2 and mem X2 and same issues. I really doubt that can be something from my side (almost two months without this ever).

2

Going to update to lastest gunicorn and look how i would use the workers for a shared cpu.
So many threads/workers fixes since 20.1.0
https://docs.gunicorn.org/en/stable/news.html

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.