Il 22/08/2011 19:13, zodman ha scritto:
why happen this ?[pid: 32096|app: 0|req: 75/75] 189.203.7.69 () {56 vars in 1057 bytes} [Mon Aug 22 12:09:43 2011] GET /admin/ => generated 0 bytes in 100221 msecs (HTTP/1.1 200) 7 headers in 428 bytes (0 switches on core 0) SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /admin/ (ip 189.203.7.69) !!! write(): Broken pipe [plugins/python/wsgi_subhandler.c line 189] [pid: 32096|app: 0|req: 76/76] 189.203.7.69 () {56 vars in 1057 bytes} [Mon Aug 22 12:11:24 2011] GET /admin/ => generated 0 bytes in 1882 msecs (HTTP/1.1 200) 7 headers in 428 bytes (0 switches on core 0) SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /admin/ (ip 189.203.7.69) !!! write(): Broken pipe [plugins/python/wsgi_subhandler.c line 189] [pid: 32096|app: 0|req: 77/77] 189.203.7.69 () {56 vars in 1058 bytes} [Mon Aug 22 12:11:26 2011] GET /admin/ => generated 0 bytes in 228 msecs (HTTP/1.1 200) 7 headers in 428 bytes (0 switches on core 0) SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /admin/ (ip 189.203.7.69) !!! write(): Broken pipe [plugins/python/wsgi_subhandler.c line 189] [pid: 32096|app: 0|req: 78/78] 189.203.7.69 () {56 vars in 1058 bytes} [Mon Aug 22 12:11:26 2011] GET /admin/ => generated 0 bytes in 142 msecs (HTTP/1.1 200) 7 headers in 428 bytes (0 switches on core 0) it is very ramdonly
Please post uwsgi version, platform, configuration, app you are running, every other information that can help people debug / reproduce your issue.
thanks, riccardo _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
