[Buildbot-devel] lazy logs a bit too lazy and que'ed requests not being processed

Dustin J. Mitchell dustin at v.igoro.us
Fri Oct 3 12:46:41 UTC 2014

My googling is failing to find previous threads about the proxy issue
and the nginx fix for it -- there's a parameter of some sort to turn
off buffering, similar to what Charles has suggested.

In 0.9.0, we're no longer using the technique of dripping out an HTTP
response slowly, so the header change isn't necessary.  However, the
header or at least a note about Apache and Nginx configuration in the
docs, would be a good addition to the 'eight' branch.


On Thu, Oct 2, 2014 at 11:10 PM, Charles Lepple <clepple at gmail.com> wrote:
> Definitely not a 1:1 mapping, but in Apache, I dropped the proxy buffer from the default of 8 kB to 512 bytes, and logs stream fine. The nginx parameters look a bit more complicated:
> http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffering
> Here's the Apache parameter I tweaked:
> http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxyiobuffersize
> One thing that Buildbot could potentially do on the logs is add "X-Accel-Buffering: no" for nginx (I think; unless I got it backwards).
> --
> - Charles Lepple
> http://ghz.cc/charles/
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel

More information about the devel mailing list