Mercurial > hg > nginx-site
view xml/en/docs/faq/accept_failed.xml @ 504:695f83494c19
Emphasized on what the "updating" parameter of the "proxy_cache_use_stale"
directive achieves. Referenced the "proxy_cache_lock" directive from there,
which has similar effect when populating a new cache element.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Tue, 24 Apr 2012 06:54:47 +0000 |
parents | e58be01b1f4a |
children | be54c443235a |
line wrap: on
line source
<!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"> <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>