Mercurial > hg > nginx-site
view xml/en/docs/faq/accept_failed.xml @ 2060:237b67ef69a6
Improved win32 build instructions.
Added "--with-openssl-opt=no-asm" argument which is required since
OpenSSL 1.0.2, as OpenSSL started to use assembler by default in 1.0.0 and
then broke builds with MASM in OpenSSL 1.0.2 (ticket #1396).
While here, added "--with-debug", added missing "--http-scgi-temp-path" and
"--http-uwsgi-temp-path", updated OpenSSL to 1.0.2l, switched to slightly
more readable one-argument-per-line style in configure example, added
indentation to continuation lines, removed useless "--builddir=objs" argument
("objs" is the default), and removed useless "-f objs/Makefile" argument
in nmake (nginx generates appropriate Makefile in the current directory).
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Tue, 17 Oct 2017 17:57:36 +0300 |
parents | af3f38e349eb |
children |
line wrap: on
line source
<!-- Copyright (C) Nginx, Inc. --> <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> <article name="What does the following error mean in the log file: “accept() failed (53: Software caused connection abort) while accepting new connection on 0.0.0.0:80”?" link="/en/docs/faq/accept_failed.html" lang="en" rev="1"> <section> <para> <initial>Q:</initial> What does the following error mean in the log file: "accept() failed (53: Software caused connection abort) while accepting new connection on 0.0.0.0:80"? </para> <para> </para> <para> <initial>A:</initial> Such errors stem from the connections that the clients managed to close before nginx was able to process them. For instance, this can happen in a situation when the user didn’t wait for a page heavily populated with images to load fully, and clicked on a different link. In this case user’s browser would close all of the prior connections which aren’t longer necessary. It is a non-critical error. </para> </section> </article>