Parachain RPC errors since Polkadot 0.9.36 client upgrade

Question

Astar uplifted to Polkadot 0.9.36 in v4.47.1 Client upgrade introduces 2 new errors on RPC nodes, both WS and HTTP.

HTTP serve connection failed hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })

WS: few of these errors - seems just informative of a connection terminated on client side

    WS transport error: i/o error: Connection reset by peer (os error 104); terminate connection: 11

Load balancer shows a massive increase of 4xx errors on backend side since nodes upgrade.

Any idea what this may be due to, especially on the HTTP interface?

This issue may be related: github.com/paritytech/polkadot/issues/6461 — Bruno, Mar 6 at 20:28
Unfortunately no, this issue is pointing a bad termination of WS connection. We also have this message on WS endpoints but it is not a big deal, most probably the client that ends connection on its side. My errors are related to HTTP endpoint and we have a lot of them. — bLd, Mar 7 at 7:28
I have edited the description to make difference of both errors clear — bLd, Mar 7 at 7:35

Niklas Adolfsson · Accepted Answer · 2023-03-07 09:18:16Z

0

HTTP serve connection failed hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })

That could actually happen on regular HTTP requests or during the initial WebSocket handshake (HTTP upgrade request to WebSocket).

The error itself occurs when reading looks like a TLS/SSL error, are you sure that you have configured TLS/SSL on the server correctly?

Otherwise, please open another issue how to reproduce this.

WS transport error: i/o error: Connection reset by peer (os error 104); terminate connection: 11

These are harmless and will be downgraded to debug in the next release, so just ignore them it's something else.

answered Mar 7 at 9:18

Niklas Adolfsson

1165 bronze badges

Thanks, the thing is nothing has been changed on our side, the error only appears when switching from an older version to Astar v4.47.1 which contains Polkadot v0.9.36 uplift. I can't help but think this is coming from this one much probably. github.com/paritytech/substrate/pull/12663
– bLd
Mar 7 at 13:50
Yes, it does but this is not necessarily an issue in the server for instance it could be client the dropped the socket prematurely or something. So again, if you find a way to reproduce it would help and create an issue in substrate or jsonrpsee. Thus, the error is really that hyper couldn't upgrade the socket to a service....
– Niklas Adolfsson
Mar 7 at 22:28

Add a comment |

1 Answer 1