Forum List Message List New Topic Print View

shivramg94

May 15, 2017 11:41AM

Registered: 7 years ago
Posts: 25

At times, the error logs say

2017/05/15 11:37:01 [notice] 22229#0: signal process started
2017/05/15 11:37:02 [alert] 22030#0: sendmsg() failed (32: Broken pipe)
2017/05/15 11:37:02 [alert] 22030#0: sendmsg() failed (32: Broken pipe)
2017/05/15 11:37:04 [alert] 22030#0: sendmsg() failed (9: Bad file descriptor)
2017/05/15 11:37:04 [alert] 22030#0: sendmsg() failed (32: Broken pipe)
2017/05/15 11:37:04 [alert] 22030#0: sendmsg() failed (9: Bad file descriptor)
2017/05/15 11:37:04 [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