Welcome! Log In Create A New Profile

Re: Reload of NGinX doesnt kill some of the older worker processes

Forum List Message List New Topic Print View

shivramg94

May 15, 2017 11:37AM

Registered: 7 years ago
Posts: 25

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)

Reply Quote

RSS

Subject	Author	Posted
Reload of NGinX doesnt kill some of the older worker processes	shivramg94	May 15, 2017 06:54AM
Re: Reload of NGinX doesnt kill some of the older worker processes	Maxim Dounin	May 15, 2017 10:04AM
Re: Reload of NGinX doesnt kill some of the older worker processes	shivramg94	May 15, 2017 11:37AM
Re: Reload of NGinX doesnt kill some of the older worker processes	shivramg94	May 15, 2017 11:41AM
Re: Reload of NGinX doesnt kill some of the older worker processes	Maxim Dounin	May 15, 2017 12:26PM
Re: Reload of NGinX doesnt kill some of the older worker processes	shivramg94	May 15, 2017 12:41PM
Re: Reload of NGinX doesnt kill some of the older worker processes	Maxim Dounin	May 15, 2017 01:00PM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 177

Record Number of Users: 8 on April 13, 2023

Record Number of Guests: 421 on December 02, 2018