[critical] worker timeout

Support System Administrator
1

Good morning,
Since switching to version 7, when I have to print more than 10 invoices at once the process crashes with this single message in the logs:

[CRITICAL] WORKER TIMEOUT

The process worked perfectly in previous versions and I can’t find how to increase this timeout.

Thank you in advance for your feedback

Olivier

2

Good morning,
it seems you have the workers activated in the trytond.conf file. Did you also start at least one trytond-worker service?

3

Hello,

In my configuration file I specified:

[queue]
worker=false

But actually I have this line in the logs after restarting the server:

[INFO] Using worker: sync

4

What happens when you remove the complete section (the default of worker is False)?

5

Basically there was nothing in this section, I tried a bit of everything before coming to talk about it here.

6

Which process?
Is it the exact content of the log?
What is your setup?

7

I solved the problem by adding:

timeout=3600

in the file /etc/gunicorn.conf.py

8

FTR, it was already reported and was closed and classified as “expected behavior”.

9

@ced , in the corresponding MR you say, there is an environment variable to set the gunicorn timeout in docker. I am facing also the problem @pokoli experienced, that using GUNICORN_CMD_ARGS="--timeout 0" doesn’t work. Can you help and explain, how to do it? Thank you.

10

If it does not work for you, you should see with gunicorn project.