Zato server dies after gunicorn worker timeouts

Hi,

Our Zato instance has two servers. Every now and then one of the server processes just dies, the log shows:

2016-09-08 12:33:51,772 - ^[[1;33mCRITICAL^[[0m - 53253:Dummy-1 - gunicorn.main:204 - WORKER TIMEOUT (pid:21596)
2016-09-08 12:33:51,813 - ^[[1;33mCRITICAL^[[0m - 53253:Dummy-1 - gunicorn.main:204 - WORKER TIMEOUT (pid:21596)

So, both (we use the default number of gunicorn workers = 2) gunicorn workers are getting a timeout and the process dies, leaving this server in an crippled state.

Is there an option to get more debug information from the gunicorn workers?

Regards, Jan