Red Hat Bugzilla – Bug 1260312
lighttpd 1.4.36 has a problem. Please kindly update it to 1.4.37
Last modified: 2015-10-29 10:50:57 EDT
Description of problem: lighttpd 1.4.36 has this ( http://redmine.lighttpd.net/issues/2659 ) problem. Its filling up my log(s). Please kindly update lighttpd to a stable version 1.4.37. As per lighttpd changelog ( http://www.lighttpd.net/2015/8/30/1.4.37/ ), this and many other issues have been resolved in version 1.4.37. Version-Release number of selected component (if applicable): 1.4.36 How reproducible: We use django, with gunicorn as the proxy backend. Where-ever lighttpd 1.4.36 is installed, and a proxy backend is being used, its going to fill logs unnecessarily. Steps to Reproduce: 1. Install lighttpd 1.4.36 from epel on centos 6.x 2. run lighttpd, with any proxy backend 3. watch logs Actual results: Expected results: Additional info:
There is already 1.4.37 in testing, see https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7868 You should be able to get it with a "yum update --enablerepo=epel-testing" If it works for you, give positive karma in bodhi to get it pushed to stable sooner.
Created attachment 1070697 [details] lighttpd 1.4.37 log output on first run, after fresh update 1.4.37 from testing is working for me. Although it has a few kinks here and there, that need fixing/updating. I'v attached a text file with to show my log output. Its showing the \t and \n characters in log output for fastcgi
Looks like debug or debug logging was left turned on, out-of-the-box, in 1.4.37 build(s)
Nope. Not entirely comfortable with 1.4.37 "as it is" right now. I'm watching slight issue with API calls, after update. We run a django+gunicorn setup with lighttpd, for our main web + API calls. Not sure about the cause yet. I'v reverted back to 1.4.35-1.el6.x86_64, to keep things consistent. This is a production box. I'm going to leave it "as it is", for now. I'll wait for the stable version, for updating on production.