> Hi,
>
> I'm using nginx 0.8.54 + uWSGI 0.9.6.5 for a website (written in Pylons)
> with more or less 2000 pageviews per hour (and more in near future). I
> keep getting a lot of those in the uWSGI log:
>
> Sun Jan  9 12:26:43 2011 - SIGPIPE: writing to a closed pipe/socket/fd
> (probably the client disconnected) on request
> /portal/nto/gallery/20/element/2?c=64 !!!
> Sun Jan  9 12:26:43 2011 - writev(): Broken pipe [wsgi_headers.c line 168]
> Sun Jan  9 12:26:43 2011 - SIGPIPE: writing to a closed pipe/socket/fd
> (probably the client disconnected) on request
> /portal/nto/gallery/20/element/2?c=64 !!!
> Sun Jan  9 12:26:43 2011 - write(): Broken pipe [pyutils.c line 101]
>
> There are so many of those errors that after a few minutes the log grows
> to hundreds of KB. I run uWSGI with this command:
>
> --uid www --chdir $APP_PATH --ini production.ini --daemonize uwsgi.log
>
> The production.ini contains:
>
> [uwsgi]
> socket = /tmp/uwsgi.sock
> master = true
> pidfile = uwsgi.pid
> processes = 4
> disable-logging = true
> logdate = true
> #harakiri = 10
> #limit-as = 128
> enable-threads = true
> home = /storage/apps/pylons
> wsgi-file = wsgi.py
>
> I'm afraid that this hurts the performance as the website doesn't seem
> very responsive. Nothing like that occured when I tested it with
> ApacheBench or httperf. What could be the problem? How can I disable
> logging of this error?
>
> Regards,
> --
> Juliusz Gonera
> http://juliuszgonera.com/
> _______________________________________________
>

Hi Juliusz, check your nginx log, it could be a some form of 'attack',
where you receive the request but soon the client disconnects.

If you get tons of this error the performance will be hurt for sure as you
lose precious resources.

If its normal for your clients to have a big rate of prematurely closed
connections (but this looks strange to me) use this:

--logto /dev/null

to disable all the I/O on your disks

-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to