Uncaught BrokenPipe: Broken pipe (os error 32) #659

ITS-NIGHTOWL · 2020-06-16T17:44:43Z

After running my ws client for 11 hours, I got this error (for the first time):

error: Uncaught BrokenPipe: Broken pipe (os error 32)   
    at unwrapResponse ($deno$/ops/dispatch_minimal.ts:63:11)
    at Object.sendAsyncMinimal ($deno$/ops/dispatch_minimal.ts:106:10)
    at async Object.write ($deno$/ops/io.ts:65:18)
    at async BufWriter.flush (https://deno.land/[email protected]/io/bufio.ts:479:25)
    at async writeFrame (https://deno.land/[email protected]/ws/mod.ts:144:3)

Any reasons as to why?

The text was updated successfully, but these errors were encountered:

wongjiahau · 2020-06-27T09:25:38Z

I'm also getting this error, but for different reasons

bartlomieju · 2020-07-14T12:55:58Z

Please provide more reproduction. Broken pipe might happen for number of reasons, eg. the other side of connection closes it abruptly.

colorhook · 2020-08-06T05:05:55Z

WebSocket demo reload web page and deno server exit

And I cannot catch the exception

async function dispatch(msg: string): Promise<void> {
  for (const client of clients.values()) {
    try {
      await client.send(msg)
    } catch (err) {}
  }
}

Exception Stack Message

Uncaught BrokenPipe: Broken pipe (os error 32)   
    at unwrapResponse (rt/10_dispatch_minimal.js:52:13)
    at sendAsync (rt/10_dispatch_minimal.js:95:12)
    at async write (rt/12_io.js:117:20)
    at async Object.writeAll (rt/13_buffer.js:223:19)
    at async BufWriter.flush (bufio.ts:467:7)
    at async writeFrame (mod.ts:141:3)

deno version

deno 1.2.0
v8 8.5.216
typescript 3.9.2

Caesar2011 · 2020-09-27T17:48:54Z

I get this error when starting a localhost webserver with for await (const req of server) { and then select a tab in Firefox from yesterday for the first time.

Probably the browser tries to use the previous connection and the server crashes because the connection is unknown.

lmiller1990 · 2020-09-30T09:43:08Z

I get this error every 24h or so, after which I need to restart the process. I'm on Ubuntu, behind nginx. Server serves HTML at about 30-60 request / h. Basically the "hello world" like setup, no extra dependencies. I am on deno 1.3.x.

rvdende · 2020-10-29T06:20:38Z

Running into this as well.. about 12 hours after starting the service. Might be that the client changed ip addresses and that confused deno or something like that? Also Deno error message doesn't tell me where in my code the issue originated from.

error: Uncaught BrokenPipe: Broken pipe (os error 32)
    at unwrapResponse (deno:cli/rt/10_dispatch_minimal.js:59:13)
    at sendAsync (deno:cli/rt/10_dispatch_minimal.js:98:12)
    at async write (deno:cli/rt/12_io.js:117:20)
    at async BufWriter.write (bufio.ts:499:29)
    at async writeResponse (_io.ts:273:15)
    at async ServerRequest.respond (server.ts:84:7)
    at async Response.end (response.ts:218:5)

leogreu · 2020-11-13T13:48:40Z

Same problem here. Very frequently after a few hours of running (between 6 and 12 hours I guess).

Edit: Ubuntu, behind nginx, no ws - just static files and a simple api over http.

error: Uncaught (in promise) BrokenPipe: Broken pipe (os error 32)
    at unwrapResponse (deno:cli/rt/10_dispatch_minimal.js:59:13)
    at sendAsync (deno:cli/rt/10_dispatch_minimal.js:98:12)
    at async write (deno:cli/rt/12_io.js:117:20)
    at async Object.writeAll (deno:cli/rt/13_buffer.js:223:19)
    at async BufWriter.flush (bufio.ts:468:7)
    at async writeResponse (_io.ts:288:3)
    at async Server.iterateHttpRequests (server.ts:154:11)
    at async Server.acceptConnAndIterateHttpRequests (server.ts:227:5)
    at async MuxAsyncIterator.callIteratorNext (mux_async_iterator.ts:30:31)

leogreu · 2020-11-16T06:23:58Z

Has anyone found a workaround for this? i.e., catching the error or restarting the server after the error occurs?

For me, Deno is currently unusable because of this, unfortunately ...

rvdende · 2020-11-16T07:20:08Z

Closest I found to a workaround is to switch to http and run a nginx reverse proxy with the certificate/key infront of deno

leogreu · 2020-11-16T15:29:31Z

Thanks for the suggestion!

However, this already is my configuration and Deno crashes even when using http only.

bartlomieju · 2020-11-16T15:31:42Z

Errors originating from HTTP server should be fixed by denoland/deno#8365

timonson · 2020-12-29T04:44:11Z

This BrokenPipe: Broken pipe (os error 32) error still happens with std 0.82.0 all the time using Firefox, not so much with Chrome (although there seem to be other issues, e.g. incomplete data sometimes). It happens when I make a request in Chrome, restart Firefox and make a request there. It is strange.

Please reopen this issue!

BrokenPipe: Broken pipe (os error 32)
at unwrapResponse (deno:runtime/js/10_dispatch_minimal.js:59:13)
at sendAsync (deno:runtime/js/10_dispatch_minimal.js:98:12)
at async write (deno:runtime/js/12_io.js:117:20)
at async Object.writeAll (deno:runtime/js/13_buffer.js:223:19)
at async BufWriter.flush (bufio.ts:468:7)
at async writeResponse (_io.ts:288:3)
at async ServerRequest.respond (server.ts:84:7)

lideming · 2021-02-12T12:53:56Z

@timonson

at async ServerRequest.respond (server.ts:84:7)

Do you use other library or call ServerRequest.respond directly? The caller have to catch and handle the error.

timonson · 2021-02-12T17:49:45Z

Thanks for coming back to this issue @lideming !

Although I still don't know what exactly causes this error, it looks like I made a mistake in my error handling function.
I caught the error on req.respond({status: 200}) correctly, but what I forgot is adding a catch statement to req.respond({status: 500}) inside my error handler function.

lideming · 2021-02-12T18:25:28Z

@timonson The BrokenPipe error usually means trying to send data to a closed/broken connection.
For example, the user interrupts loading while the browser is receiving content from the server, then the browser stops receiving, closes the connection, and causes the BrokenPipe error on the server which was sending data.

nuts-n-bits · 2021-02-26T03:30:11Z

For me this error tends to happen when I saturate the TCP connection, maybe some connection gets dropped by the os for whatever reason and now you're writing to a broken pipe. What makes it troubling is that this is uncatchable within the for await loop, from limited testing, it seems the way to catch it is this:

while(true) {
    try {
        for await (const request of server) {
            // serve the request
        }
    } 
    catch(e) {
         // handel error 
    }
}

The reason of which I'm sure can be made sense of by folks who understand how async iterators work better than I do, but I'm still confused by this lol.

Edit: So I know now that the error occurs at the point where the for await calls the .next() of the server iterator, and #761 fixes this where the error is a NotConnected.

OverGlass · 2021-03-16T14:27:02Z

Same problem for me. Every 6 -12 hours of running.
On Ubuntu, behind nginx. - Deno 1.8.0

static files server
api over HTTP

How can I help for debugging this ? This is in production and I really want to dig into this.

malimohub · 2021-03-16T16:26:50Z

Is there a fix coming out for this? Deno is pretty unusable at this point

lucacasonato · 2021-03-16T16:34:38Z

@malimohub The error is that you are not catching the error... see #659 (comment). It is totally expected for this error to happen (connections sometimes close unexpectedly). It might be more obvious what is happening if instead of using for await, you called const req = await server.next() in an infinite loop manually.

nuts-n-bits · 2021-03-21T14:40:25Z

@malimohub The error is that you are not catching the error... see [#659 (comment)]

Well, I have a minor objection. Because all the docs and tutorials, official or not, was pretty much using the pattern for await (req of server) directly at the top level it makes me feel like that's how it's intended to be used, so I expect it to not throw at all. If the intention of server is to throw, then the docs should really mention while true try catch (or whatever) instead, so that everyone isn't surprised by the behaviour. And I agree that some error deserves to be thrown, but without proper documentation, I was under the impression that all that can go wrong should go wrong during request.respond()

So anyways maybe update the docs to reflect this? On the other hand, while true try catch at top level is really ugly lol

hiral-kotadiya · 2021-03-26T06:23:51Z

0|app      |     at async Collection.findOne (https://raw.githubusercontent.com/manyuanrong/deno_mongo/refactor/src/collection/collection.ts:43:12)
0|app      | 2021-03-26T06:15:07.234Z [10] BrokenPipe: Broken pipe (os error 32) 
0|app      |     at unwrapResponse (deno:runtime/js/10_dispatch_minimal.js:60:13)
0|app      |     at sendAsync (deno:runtime/js/10_dispatch_minimal.js:99:12)
0|app      |     at async write (deno:runtime/js/12_io.js:118:20)
0|app      |     at async Object.writeAll (deno:runtime/js/13_buffer.js:224:19)
0|app      |     at async WireProtocol.command (https://raw.githubusercontent.com/manyuanrong/deno_mongo/refactor/src/protocol/protocol.ts:55:7)

In my case, broken pipe error generated from deno_mongo.

zigomir · 2021-04-15T18:54:22Z

I was also getting this error using http/serve. I now tried new unstable http api as described in Deno 1.9 blog post and couldn't reproduce the problem (yet) 🕶.

MrOggy85 · 2021-05-25T15:19:36Z

I also switch to the new api, but got the same error as mentioned previously in this issue.
However, I was not using await with respondWith. When I added await I successfully caught the error and the execution could continue.

await respondWith(
  new Response(body, {
    headers,
    status: 200,
  }),
);

I made the same mistake with the previous api, by not prefixing request.respond with await.

bartlomieju · 2021-11-09T17:04:57Z

std/http and std/ws implementations were rewritten to leverage native HTTP bindings available in Deno (Deno.serveHttp). This error should no longer occur. I'm going to tentatively close this issue, please let me know if the problem persists.

ralyodio · 2021-11-18T12:04:41Z

does this impact oak?

I'm runngin puppeteer and if I do 5 instances at a time it crashes.

bartlomieju · 2021-11-18T12:14:53Z

oak doesn't use std/http anymore in the latest version so it shouldn't be affected.

Jekahome · 2021-12-16T21:50:22Z

I get this error when I intensively fill with data of 64 kb 3000 iterations
But I'm using a different language)))

let size_byte = 65535; 
let buff = (0..=size_byte).map(|_|78).collect::<Vec<u8>>();
                
addr.do_send(ClientCommand( Item::FirstBinary( Bytes::from_iter(buff.clone()))));
for i in (0..3000){
    addr.do_send(ClientCommand( Item::Continue( Bytes::from_iter(buff.clone()))));
}
addr.do_send(ClientCommand( Item::Last( Bytes::from_iter(buff.clone()))));

Error: Io(Os { code: 32, kind: BrokenPipe, message: "Broken pipe" })

Currently, when you add your own license to modified files, it will complain. This changes the regex so that it can be multiline.

bartlomieju transferred this issue from denoland/deno Feb 1, 2021

This was referenced Feb 12, 2021

Broken pipe with deno. denoland/deno#8830

Closed

feat(std/http): add HTTP server "error" event #703

Closed

nayeemrmn mentioned this issue Feb 26, 2021

fix(http/server): Swallow NotConnected errors from listener.accept() #761

Merged

jpalvarezl mentioned this issue Mar 1, 2021

Rocket error crashing pod 5afe/safe-client-gateway#284

Closed

ry added the bug Something isn't working label May 25, 2021

Tc-001 mentioned this issue Jul 23, 2021

Broken pipe (os error 32) if cancellig request pluvial/svelte-adapter-deno#5

Closed

Tc-001 mentioned this issue Jul 23, 2021

[BUG] BrokenPipe Crash cmorten/opine#102

Closed

bartlomieju closed this as completed Nov 9, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uncaught BrokenPipe: Broken pipe (os error 32) #659

Uncaught BrokenPipe: Broken pipe (os error 32) #659

ITS-NIGHTOWL commented Jun 16, 2020

wongjiahau commented Jun 27, 2020

bartlomieju commented Jul 14, 2020

colorhook commented Aug 6, 2020 •

edited

Loading

Caesar2011 commented Sep 27, 2020 •

edited

Loading

lmiller1990 commented Sep 30, 2020 •

edited

Loading

rvdende commented Oct 29, 2020

leogreu commented Nov 13, 2020 •

edited

Loading

leogreu commented Nov 16, 2020

rvdende commented Nov 16, 2020 •

edited

Loading

leogreu commented Nov 16, 2020

bartlomieju commented Nov 16, 2020

timonson commented Dec 29, 2020 •

edited

Loading

lideming commented Feb 12, 2021

timonson commented Feb 12, 2021

lideming commented Feb 12, 2021

nuts-n-bits commented Feb 26, 2021 •

edited

Loading

OverGlass commented Mar 16, 2021

malimohub commented Mar 16, 2021

lucacasonato commented Mar 16, 2021

nuts-n-bits commented Mar 21, 2021

hiral-kotadiya commented Mar 26, 2021

zigomir commented Apr 15, 2021

MrOggy85 commented May 25, 2021

bartlomieju commented Nov 9, 2021

ralyodio commented Nov 18, 2021

bartlomieju commented Nov 18, 2021

Jekahome commented Dec 16, 2021 •

edited

Loading

Uncaught BrokenPipe: Broken pipe (os error 32) #659

Uncaught BrokenPipe: Broken pipe (os error 32) #659

Comments

ITS-NIGHTOWL commented Jun 16, 2020

wongjiahau commented Jun 27, 2020

bartlomieju commented Jul 14, 2020

colorhook commented Aug 6, 2020 • edited Loading

Caesar2011 commented Sep 27, 2020 • edited Loading

lmiller1990 commented Sep 30, 2020 • edited Loading

rvdende commented Oct 29, 2020

leogreu commented Nov 13, 2020 • edited Loading

leogreu commented Nov 16, 2020

rvdende commented Nov 16, 2020 • edited Loading

leogreu commented Nov 16, 2020

bartlomieju commented Nov 16, 2020

timonson commented Dec 29, 2020 • edited Loading

lideming commented Feb 12, 2021

timonson commented Feb 12, 2021

lideming commented Feb 12, 2021

nuts-n-bits commented Feb 26, 2021 • edited Loading

OverGlass commented Mar 16, 2021

malimohub commented Mar 16, 2021

lucacasonato commented Mar 16, 2021

nuts-n-bits commented Mar 21, 2021

hiral-kotadiya commented Mar 26, 2021

zigomir commented Apr 15, 2021

MrOggy85 commented May 25, 2021

bartlomieju commented Nov 9, 2021

ralyodio commented Nov 18, 2021

bartlomieju commented Nov 18, 2021

Jekahome commented Dec 16, 2021 • edited Loading

colorhook commented Aug 6, 2020 •

edited

Loading

Caesar2011 commented Sep 27, 2020 •

edited

Loading

lmiller1990 commented Sep 30, 2020 •

edited

Loading

leogreu commented Nov 13, 2020 •

edited

Loading

rvdende commented Nov 16, 2020 •

edited

Loading

timonson commented Dec 29, 2020 •

edited

Loading

nuts-n-bits commented Feb 26, 2021 •

edited

Loading

Jekahome commented Dec 16, 2021 •

edited

Loading