4 messages in ru.sysoev.nginxRe: writev() failed (104: Connection ...
FromSent OnAttachments
Zsu FrogFeb 5, 2009 11:21 pm 
Igor SysoevFeb 6, 2009 2:01 am 
Glen LumanauApr 26, 2009 8:06 pm 
Maxim DouninApr 27, 2009 1:25 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: writev() failed (104: Connection reset by peer)Actions...
From:Glen Lumanau (gl@lumanau.web.id)
Date:Apr 26, 2009 8:06:07 pm
List:ru.sysoev.nginx

2009/2/6 Igor Sysoev <is@rambler-co.ru>

On Fri, Feb 06, 2009 at 08:22:01AM +0100, Zsu Frog wrote:

every time, when I login in my site ,they happened. I just can get a error blank page.

These lines:

2009/02/06 11:19:51 [info] 32745#0: *1 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer)

are usually normal: MSIE closes keepalie connection using RST packet. However, these ones:

2009/02/06 11:24:06 [info] 370#0: *11 writev() failed (104: Connection reset by peer) while sending to client, client: 202.116.94.64, server: 202.116.94.254, request: "GET /zsuxg/image/skin/0/main_13.gif HTTP/1.1", upstream: "http://202.116.64.11:9080/zsuxg/image/skin/0/main_13.gif", host: "202.116.94.254", referrer: "http://202.116.94.254/zsuxg/"

are strange.

I also got this error on my nginx error log. Is there any way to fix this?

---LOGS------------------------------------------------------------------------

2009/02/06 11:19:51 [info] 32745#0: *1 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:20:01 [info] 32745#0: *3 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:21:09 [info] 32745#0: *6 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:23:03 [notice] 368#0: using the "epoll" event method 2009/02/06 11:23:03 [warn] 368#0: 2048 worker_connections are more than open file resource limit: 1024 2009/02/06 11:23:03 [notice] 368#0: nginx/0.6.34 2009/02/06 11:23:03 [notice] 368#0: built by gcc 4.3.2 (Ubuntu 4.3.2-1ubuntu11) 2009/02/06 11:23:03 [notice] 368#0: OS: Linux 2.6.27-7-server 2009/02/06 11:23:03 [notice] 368#0: getrlimit(RLIMIT_NOFILE): 1024:1024 2009/02/06 11:23:03 [notice] 369#0: start worker processes 2009/02/06 11:23:03 [notice] 369#0: start worker process 370 2009/02/06 11:23:11 [info] 370#0: *1 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:23:11 [info] 370#0: *4 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:24:06 [info] 370#0: *9 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:24:06 [info] 370#0: *11 writev() failed (104: Connection reset by peer) while sending to client, client: 202.116.94.64, server: 202.116.94.254, request: "GET /zsuxg/image/skin/0/main_13.gif HTTP/1.1", upstream: "http://202.116.64.11:9080/zsuxg/image/skin/0/main_13.gif", host: "202.116.94.254", referrer: "http://202.116.94.254/zsuxg/" 2009/02/06 11:26:01 [info] 370#0: *15 client 202.116.94.64 closed keepalive connection 2009/02/06 11:26:01 [info] 370#0: *17 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) 2009/02/06 11:26:01 [info] 370#0: *19 writev() failed (104: Connection reset by peer) while sending to client, client: 202.116.94.64, server: 202.116.94.254, request: "GET /zsuxg/image/skin/0/page_bg.gif HTTP/1.1", upstream: "http://202.116.64.11:9080/zsuxg/image/skin/0/page_bg.gif", host: "202.116.94.254", referrer: "http://202.116.94.254/zsuxg/" 2009/02/06 15:00:04 [notice] 3035#0: using the "epoll" event method 2009/02/06 15:00:04 [warn] 3035#0: 2048 worker_connections are more than open file resource limit: 1024 2009/02/06 15:00:04 [notice] 3035#0: nginx/0.6.34 2009/02/06 15:00:04 [notice] 3035#0: built by gcc 4.3.2 (Ubuntu 4.3.2-1ubuntu11) 2009/02/06 15:00:04 [notice] 3035#0: OS: Linux 2.6.27-7-server 2009/02/06 15:00:04 [notice] 3035#0: getrlimit(RLIMIT_NOFILE): 1024:1024 2009/02/06 15:00:04 [notice] 3036#0: start worker processes 2009/02/06 15:00:04 [notice] 3036#0: start worker process 3037 2009/02/06 15:00:12 [info] 3037#0: *3 writev() failed (104: Connection reset by peer) while sending to client, client: 202.116.94.64, server: 202.116.94.254, request: "GET /zsuxg/image/skin/0/page_bg.gif HTTP/1.1", upstream: "http://202.116.64.11:9080/zsuxg/image/skin/0/page_bg.gif", host: "202.116.94.254", referrer: "http://202.116.94.254/zsuxg/" 2009/02/06 15:01:00 [info] 3037#0: *8 client 202.116.94.64 closed keepalive connection (104: Connection reset by peer) ~

----------------------------------------------------------------------------

my nginx.conf setting:

#user nobody; worker_processes 1;

#error_log logs/error.log; #error_log logs/error.log notice; #error_log logs/error.log info; error_log logs/error.log debug;

#pid logs/nginx.pid;

events { worker_connections 2048; }

http { include mime.types; default_type application/octet-stream;

log_format up_head '$remote_addr - $remote_user [$time_local] $request ' 'upstream_http_content_type $upstream_http_content_type';

log_format main '$remote_addr - $remote_user [$time_local] $request ' # '"$status" $body_bytes_sent "$http_referer" ' # '"$http_user_agent" "$http_x_forwarded_for"';

access_log logs/access.log debug;

sendfile on; #tcp_nopush on;

#keepalive_timeout 0;

#gzip on;

upstream mysvr { server 202.116.64.11:9080; server 202.116.64.11:9080; hash $request_uri; }

server { listen 80; server_name 202.116.94.254;

keepalive_timeout 10000; proxy_connect_timeout 2400; proxy_read_timeout 2400; proxy_send_timeout 2400; client_max_body_size 10m; proxy_ignore_client_abort on;

client_header_buffer_size 4000k;

#charset koi8-r;

#access_log logs/host.access.log main;

location / { root html; index index.html index.htm; }

location /zsuxg/ { proxy_pass http://mysvr/zsuxg/; proxy_redirect default; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }

}

}

why writev() failed (104: Connection reset by peer) while sending to client ??

-- Igor Sysoev http://sysoev.ru/en/