Rocket error crashing pod

[jpalvarezl]

[2021-02-25T13:17:19Z ERROR rocket::rocket] Failed to write response: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

Error causes the pod to crash. The issue has been documented here:

• The restriction on the length of the content with a high RPS rwf2/Rocket#286
• Stabilize HTTP library rwf2/Rocket#17

Seems like the cause can be the size of the Content-Length or spikes in requests/second.

[jpalvarezl]

I have been reading a bit more about this. The issue could be associated with write! as some links might suggest:

• Weird error message on heavy usage of RPC openethereum/parity-ethereum#10342 (they have the same issue)
• Uncaught BrokenPipe: Broken pipe (os error 32)  denoland/std#659

As far as I get it there is a stream into which we are trying to write that somehow becomes inaccessible from our end? Could be the changes we did in the responder to handle errors better that's somehow tripping up with deserialising errors or something like that?

Solutions? Not sure if we can call them solutions, maybe just workarounds worth trying:

• Uncaught BrokenPipe: Broken pipe (os error 32)  denoland/std#659
• http://yukimemi.github.io/post/2018-01-07_fix-broken-pipe-in-rust/ (in Japanese)

[mtb-pro]

I had this problem before
your rpc port is under attack
your rpc port should be restricted to a specific IP