after a few hours we finally figured it out.
a random package had this line in it:
logging.getLogger().setLevel(logging.DEBUG)
that only took... 5 hours to find after writing a few virtualenvs/services to
try and replicate this.
___
uWSGI m
Thanks for looking, robert.
the uwsgi log looks like this:
*** Starting uWSGI 2.0.15 (64bit) on [Tue May 16 16:22:13 2017] ***
compiled with version: 5.4.0 20160609 on 15 May 2017 19:45:42
os: Linux-4.9.15-x86_64-linode81 #1 SMP Fri Mar 17 09:47:36 EDT 2017
nodename: sextant
mach
> our logging broke after a redeployment and I can't seem to figure out what
> is going on. The loglevel keeps dropping to DEBUG as if nothing is
> configured. (it's support to be ERROR or CRITICAL)
>
> our stack looks like this:
>
> 1. supervisord invokes uwsgi
>
> /var/www/sites/virtuale
our logging broke after a redeployment and I can't seem to figure out what is
going on. The loglevel keeps dropping to DEBUG as if nothing is configured.
(it's support to be ERROR or CRITICAL)
our stack looks like this:
1. supervisord invokes uwsgi
/var/www/sites/virtualenv/bin/uwsgi
