Just closing the loop on this, but what appeared to be happening was
that newly created nodes were not having the nginx master PID start up
with a custom ulimit set in /etc/security/limits.d/. The workers were
all fine since the worker_rlimit_nofile was set in the nginx.conf, but I
was running
I did see the changelog hadn't noted many changes and running a diff of
the versions shows what you mentioned regarding the 400 bad request
handling code. I'm not necessarily stating that nginx is the problem,
but it would seem like something had changed enough to cause the
backend's backlog t
Hello!
On Tue, Sep 02, 2014 at 11:00:10AM -0500, Jon Clayton wrote:
> I'm trying to track down an issue that is being presented only when I run
> nginx version 1.6.1-1~precise. My nodes running 1.6.0-1~precise do not
> display this issue, but freshly created servers are getting floods of these
>
I'm trying to track down an issue that is being presented only when I
run nginx version 1.6.1-1~precise. My nodes running 1.6.0-1~precise do
not display this issue, but freshly created servers are getting floods
of these socket connection issues a couple times a day.
/connect() to unix:/tmp/u
