Arc Forumnew | comments | leaders | submitlogin
Broken pipe errors with the arc server
2 points by forwardslash 4243 days ago | 2 comments
We recently received a big spike in traffic to our site from reddit which brought our server to its knees. We ended up seeing a lot of requests dropping because they took too long, but even as we solved those problems we still broken pipe errors come up a lot:

    tcp-write: error writing
      system error: Broken pipe; errno=32
      context...:
       /app/racket/collects/racket/private/map.rkt:26:19: loop
       /app/prod/ac.scm:1422:0: ar-close
        handle-request-thread
    tcp-write: error writing
      system error: Broken pipe; errno=32
      context...:
 
       /app/racket/collects/racket/private/map.rkt:26:19: loop
       /app/prod/ac.scm:1422:0: ar-close
        th1
    
    tcp-write: error writing
      system error: Broken pipe; errno=32
      context...:
       /app/prod/ac.scm:957:13: writeb
        gf1287
        gf1253
        handle-request-thread
I'm just wondering if anyone has any experience with these kind of errors. Is just a case of the connection being closed to early?

Note: we usually have nginx in front of our arc server but we get the same error without it.



3 points by thaddeus 4243 days ago | link

Yes, you'll get broken pipe errors if the browser closes the connection and stops reading prior to completion. I'm guessing some of your users are probably reloading/leaving due to these long response times.

-----

2 points by forwardslash 4240 days ago | link

Ah, well, I suppose there's not a whole lot we can do about that other than decrease our response times.

-----