You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a tornado app, that uses gunicorn 0.17.3 (I also tested with 19.6.0), and it's using logging.{info|error|debug} throughout the project.
If I run the app using gunicorn --access-logfile - --error-logfile - -b 0.0.0.0:3000 -w 1 -k tornado server:application, every logging method is not displayed on my console.
If I run the app using gunicorn --log-config logging.conf -b 0.0.0.0:3000 -w 1 -k tornado server:application, every logging method starts to be displayed on my console.
Hello!
I have a tornado app, that uses gunicorn 0.17.3 (I also tested with 19.6.0), and it's using
logging.{info|error|debug}
throughout the project.If I run the app using
gunicorn --access-logfile - --error-logfile - -b 0.0.0.0:3000 -w 1 -k tornado server:application
, every logging method is not displayed on my console.If I run the app using
gunicorn --log-config logging.conf -b 0.0.0.0:3000 -w 1 -k tornado server:application
, every logging method starts to be displayed on my console.The conf file is like below:
For example, consider these lines:
Using the first method to run the app, the output is:
Using the second method to run the app, the output is:
Starting App with Tornado DEBUG = False Connected to MongoDB. Hosts: localhost:27017. User: None. ReplicaSet: =============== print - before =============== =============== foobar - before =============== =============== foobar [debug] =============== =============== print - after =============== =============== foobar - after =============== =============== foobar [debug] =============== GET on "/foo/bar" with filters: {} 304 GET /foo/bar (127.0.0.1) 9.29ms
Why those logging methods only work when using a config file? And why they only work with this
logger_root
directive?Is there any relation to issues #379, #832, #1020, #1124, #1184, #1271, #1293, #1358 ?
How can I have those logging methods showing messages on console without using a config file? Is that possible?
The text was updated successfully, but these errors were encountered: