Hello!

On Mon, May 15, 2017 at 11:37:54AM -0400, shivramg94 wrote:

> Hi Maxim,
>
> This is what I could find in the error logs
>
> 2017/05/15 11:32:18 [notice] 21499#0: signal process started
> 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (88: Socket operation
> on non-socket)
> 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (32: Broken pipe)
> 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (88: Socket operation
> on non-socket)
> 2017/05/15 11:32:19 [alert] 22030#0: sendmsg() failed (32: Broken pipe)
> 2017/05/15 11:32:20 [alert] 22030#0: sendmsg() failed (88: Socket operation
> on non-socket)
> 2017/05/15 11:32:20 [alert] 22030#0: sendmsg() failed (32: Broken pipe)
> 2017/05/15 11:32:20 [alert] 22030#0: sendmsg() failed (88: Socket operation
> on non-socket)
> 2017/05/15 11:32:20 [alert] 22030#0: sendmsg() failed (32: Broken pipe)

So, clearly comminication between master process and these workers
is now broken. You have to look for earlier errors to find out
what exactly caused this - likely it hit resource limit on number
of open files or something like this.

--
Maxim Dounin
http://nginx.org/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx