Broken Pipe Error
January 12, 2022 10:57AM
Hello

I received an error message in my error log yesterday and my NGINX server stopped functioning. The error is below. I have done a search on this error but everything comes up referencing a 502 error. That is not what I am experiencing here. The server has been running for almost a year now error free and after a restart it is functioning again. Can anyone help me interpret this error so that I may proactively prevent future occurrences?

2022/01/11 09:54:45 [error] 13598#13598: *1851043 writev() failed (32: Broken pipe) while proxying and sending to upstream, client: 10.x.x.x, server: 0.0.0.0:1977, upstream: "10.x.x.x:7701", bytes from/to client:44176/188, bytes from/to upstream:188/41256
Re: Broken Pipe Error
May 19, 2022 06:02AM
I'm facing exactly same issue when modsec rule engine is turned ON and the request content-length is above 1mb
Which version of Nginx are you using ?
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 81
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready