On 11 May 2016 at 20:07, Alex Hall <[email protected]> wrote: > Hi all, > Sometimes, when I start my uwsgi from an ini file in which a log file is > specified, I get an error 288. This says that permission to write to the log > file was denied. The file is > /var/log/uwsgi/myapp.log > and I've done > chown www-data /var/log/uwsgi > and > chmod 755 /var/log/uwsgi > then > chmod 777 /var/log/uwsgi > (www-data is the user used by Nginx, so I'm using that one). > > Yet, this error persists. I'm not well versed in managing permissions or > owners, having not dealt much with a Linux shell (this is a Debian 8 > system). Am I doing something wrong in uwsgi, or is this a problem with my > chown or chmod commands that has nothing to do with anything? The confusing > thing is that logging sometimes works, and sometimes doesn't. My best guess > is that it fails when uwsgi wants to create a new log file and archive the > previous one--it seems to like to make gz versions of logs on its own. I > can't confirm that, though.
again, insufficient info. how do you run uwsgi? my advice, forget log files, run uwsgi from a systemd service and let the journal collect the logs -- damjan _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
