Open Stack

On Wed, 8 Aug 2018, Thomas Goirand wrote:

> If you don't configure uwsgi to do any special logging, then then only
> thing you'll see in the log file is client requests, without any kind of
> logging from the wsgi application. To have proper logging, one needs to
> add, in the uwsgi config file:
>
> paste-logger = true
>
> If you do that, then you need the python3-pastescript installed, which
> itself depends on the python3-paste package.
>
> Really, I don't see how an operator could run without the paste-logger
> option activated. Without it, you see nothing in the logs.

I'm pretty sure your statements here are not true. In the uwsgi
configs for services in devstack, paste-logger is not used. In the
uwsgi set up [1] I use in placedock [2], paste-logger is not used.

Yet both have perfectly reasonable logs showing a variety of log
levels, including request logs at INFO, and server debugging and
warnings where you would expect it to be.

Can you please point me to where you are seeing these problems?
Clearly something is confused somewhere. Is the difference in our
experiences that both of the situations I describe above are happy
with logging being on stderr and you're talking about being able to
config logging to files, within the application itself? If that's
the case then my response would b: don't do that. Let systemd, or
your container, or apache2, or whatever process/service orchestration
system you have going manage that. That's what they are there for.

[1] https://github.com/cdent/placedock/blob/master/shared/placement-uwsgi.ini
[2] https://github.com/cdent/placedock

-- 
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent