 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
7 messages in ru.sysoev.nginxRe: nginx error log| From | Sent On | Attachments |
|---|---|---|
| Jeremy Hubert | Jan 12, 2007 10:06 am | |
| Igor Sysoev | Jan 12, 2007 10:12 am | |
| Jeremy Hubert | Jan 12, 2007 10:20 am | |
| Igor Sysoev | Jan 12, 2007 10:23 am | |
| Igor Sysoev | Jan 12, 2007 10:27 am | |
| Igor Sysoev | Jan 12, 2007 10:34 am | |
| David Gibbons | Jan 12, 2007 11:57 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: nginx error log | Actions... |
|---|---|---|
| From: | Igor Sysoev (is-G...@public.gmane.org) | |
| Date: | Jan 12, 2007 10:23:37 am | |
| List: | ru.sysoev.nginx | |
On Fri, 12 Jan 2007, Igor Sysoev wrote:
On Fri, 12 Jan 2007, Jeremy Hubert wrote:
I'm using nginx on a fairly high traffic site and I've noticed that my error log is growing really quickly. It seems to be filling up with "closed keepalive connection" statements.
2007/01/12 10:04:49 [info] 23278#0: *2295 client 216.73.65.67 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:49 [info] 23278#0: *2749 client 81.182.163.223 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:49 [info] 23278#0: *4069 client 216.124.112.140 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:49 [info] 23282#0: *4046 client 195.93.60.72 closed keepalive connection 2007/01/12 10:04:50 [info] 23281#0: *4078 client 216.124.112.140 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:50 [error] 23278#0: *4073 open() "/home/jhubert/ kidzworld/public/img/upload/quiz/qq11070482738906.jpg" failed (2: No such file or directory), client: 68.109.74.237, server: www.kidzworld.com, URL: "/img/upload/quiz/qq11070482738906.jpg", host: "www.kidzworld.com" 2007/01/12 10:04:50 [info] 23281#0: *4082 client 216.124.112.140 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:50 [info] 23281#0: *4088 client 216.124.112.140 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:50 [info] 23281#0: *1915 client 87.247.70.33 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:50 [info] 23281#0: *4091 client 216.124.112.140 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:51 [info] 23282#0: *4050 client 24.239.239.67 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:51 [info] 23282#0: *4049 client 24.239.239.67 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:51 [info] 23282#0: *4035 client 90.26.128.152 closed keepalive connection (104: Connection reset by peer) 2007/01/12 10:04:51 [info] 23282#0: *3997 client 200.38.11.107 closed keepalive connection 2007/01/12 10:04:51 [info] 23279#0: *2952 client 213.217.198.50 closed keepalive connection
I'm wondering if this is normal?
Yes, it's normal. You may increase the error log level to the "warn" level.
The messages "client ... closed keepalive connection (104: Connection reset by peer)" mean usually that MSIE closed keepalive connection: it closes keepalive connection using the RST packet.
Igor Sysoev http://sysoev.ru/en/