Skip to content

Fix: Add timeout gunicorn parameter

Wilhelm Becker requested to merge fix-local-timeouts into master

On my local machine i couldn't run the CV with the current setup. The worker had a timeout issue:

[2021-09-22 09:35:26 +0000] [246] [INFO] Starting gunicorn 20.1.0
[2021-09-22 09:35:26 +0000] [246] [INFO] Listening at: http://0.0.0.0:8000 (246)
[2021-09-22 09:35:26 +0000] [246] [INFO] Using worker: sync
[2021-09-22 09:35:26 +0000] [248] [INFO] Booting worker with pid: 248
[2021-09-22 09:49:30 +0000] [246] [CRITICAL] WORKER TIMEOUT (pid:248)
[2021-09-22 09:49:30 +0000] [248] [INFO] Worker exiting (pid: 248)
[2021-09-22 09:49:30 +0000] [258] [INFO] Booting worker with pid: 258
[2021-09-22 09:50:01 +0000] [246] [CRITICAL] WORKER TIMEOUT (pid:258)
[2021-09-22 09:50:01 +0000] [258] [INFO] Worker exiting (pid: 258)
[2021-09-22 09:50:01 +0000] [260] [INFO] Booting worker with pid: 260
[2021-09-22 09:56:29 +0000] [246] [CRITICAL] WORKER TIMEOUT (pid:260)
[2021-09-22 09:56:29 +0000] [260] [INFO] Worker exiting (pid: 260)
[2021-09-22 09:56:29 +0000] [262] [INFO] Booting worker with pid: 262

This solved my problem: stackoverflow

I would like to merge this solution for the local docker-compose file (which is not used for any deployment? Alternatively we could add this soltion on the readme.md but I think its easier with the change of the codeline.

@kotyba.alhaj-taha FYI

Merge request reports

Loading