GitHub user BBQing added a comment to the discussion: GUNICORN_CMD_ARGS arguments aren't applied
I have checked it for v2.11-testing branch - in general GUNICORN_CMD_ARGS are passed in and they work But in case of acce-logfile due to precedence defined here https://docs.gunicorn.org/en/latest/configure.html it is overwritten by cli arguments. Now the cli fror webserver has --access-logfile parameter, that has a default value whatever is in airflow.cfg - webserver - access_logfile - here it is just '-' meaning standard output, now since you are not starting webserver with explicit value set - it resolves to '-'. webserver function there has this check: ```python if args.access_logfile: run_args += ["--access-logfile", str(args.access_logfile)] ``` since args.access_logile is equal to '-', it is True in the check and it is then added to run args used further down in the code and therefore it overrides your GUNICORN_CMD_ARGS settings so if you want manipulate the logfile from env variable - use the AIRFLOW__WEBSERVER__ACCESS_LOGFILE or change the value in airflow.cfg Hopefully it will help you. In versions 3.0.0+ I haven't find any relevant connection to gunicorn GitHub link: https://github.com/apache/airflow/discussions/53550#discussioncomment-13819170 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
