Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Gunicorn worker logs are incorrect #458

Closed
sk- opened this issue Aug 3, 2015 · 1 comment · Fixed by #572
Closed

[bug] Gunicorn worker logs are incorrect #458

sk- opened this issue Aug 3, 2015 · 1 comment · Fixed by #572
Labels

Comments

@sk-
Copy link

sk- commented Aug 3, 2015

Gunicorn workers log the date ('%(t)s' fields) with the apache format. However, for some reason the GunicornWorker is using another format. The same happens to the response size ('%(b) field'). Aiohttp instead of logging the size of the response body is logging the size of the whole response, including the headers.

The problem is in the helper.atoms function
https://github.com/KeepSafe/aiohttp/blob/51ea69d4c863b9a184293371b24e8d3e6651eb25/aiohttp/helpers.py#L228-L260

Below are the results for an app that simply returns Hello, world (12 characters).

Plain Gunicorn
127.0.0.1 - - [03/Aug/2015:14:59:09 -0300] "GET / HTTP/1.1" 200 12 "-" "curl/7.37.1"

Gunicorn + aiohttp.worker.GunicornWorker
127.0.0.1 - - Mon, 03 Aug 2015 17:51:39 GMT "GET / HTTP/1.1" 200 149 "-" "curl/7.37.1"
@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant