No response from gunicorn master within 120 seconds after pointing to external postgres

Asked Feb 15 '23 at 20:01

Active Feb 15 '23 at 20:01

Viewed 941 times

I am deploying airflow latest release using Docker, everything works fine until I point the database to an external Postgres Database. As soon as the database is pointed to an external database the webserver container doesn't get up.

The release is from apache/airflow:latest

The logs says the following

No response from gunicorn master within 120 seconds

What am I missing here ?

asked Feb 15 '23 at 20:01

anshul_cached

did you check the webserver container log? – Hussein Awala Feb 16 '23 at 22:00
Yes, its in the screenshot – anshul_cached Feb 17 '23 at 09:14
This error comes when the number of workers running does not match the expected number of workers for a period of time. check the number of workers in airflow.cfg file, try reducing it to a smaller number, probably 1. – AvnishSingh May 11 '23 at 07:45
@anshul_cached were you able to get this resolved? – Canovice May 24 '23 at 14:31
It still not working for me, using solution from @AvnishSingh – riodpp Jun 22 '23 at 04:03

No response from gunicorn master within 120 seconds after pointing to external postgres

0 Answers0