The umask parameter seems does not effect or what wrong with my usage?

[xiaopeipei123]

I want modify the default logger file right 644 to 640. When i add umask = 0027 to gunicorn configuration file, it seems that does not work. what's wrong with my usage?
below is my usage:
gunicorn.conf
...
reuse_port = True
worker_class = "gevent"
umask = 0027
daemon = True
...
i delete the old log file, and restart the gunicorn server to generate new logs, here is the new files, but the file access right does not what i want.
this is the start command
gunicorn -c "${HOME}/etc/gunicorn.conf" "main:create_app()"

-rw-r--r-- 1 org users 0 Jan 21 15:58 gunicorn-access.log
-rw-r--r-- 1 org users 275 Jan 21 15:58 gunicorn-error.log

[xiaopeipei123]

any wrong with my usage???

[xiaopeipei123]

i try it again today, it actually take effect this time. but i don't what's wrong with my configuration for last time.
all in, it seem that is not a problem.

[xiaopeipei123]

i figure out that 'daemon = True' do effect, when i change the daemon to the default , the umask can take effect.

[tilgovi]

Is there a bug then?

[Sturmtiger]

Encountered the same problem. --umask parameter doesn't work when gunicorn runs in the foreground (which is preferred because I'm using docker).
But the regular system umask works fine.
So the workaround for me was to run umask before gunicorn.
Like so:

umask 002
gunicorn --bind 0.0.0.0:5000 application:application -u user -g group

[benoitc]

Does the user in foreground have the rights?

[elibroftw]

Use 0o since the config file is in Python (ps. gunicorn.conf.py is the default config file)

umask = 0o007

[adi-]

I want to open this ticket because gunicorn still doesn't respect umask setting for created files. I have set gunicorn's setting to umask = 0o002. Files are created with -rw-r--r-- permissions.

However, when I set umask 002 for the user it creates permissions as expected -rw-rw-r--.