provider stops/hangs for no reason

Ethers Version

5.6.1

Search Terms

hangs,provider,block

Describe the Problem

I use the following code with AlchemyWebsocket provider.

provider.on('block', async (blockNumber: number) => {
      const logs = await provider.getLogs(someFilter);
      // process logic
}

I run this in ECR container on AWS. Ideally, this should run continuously to listen to every block. The problem is that after some random hours it hangs and stops listening.

It doesn’t even log any errors. And it doesn’t seem like something to do with container memories etc. What’s interesting is that the health check endpoint that is exposed returns 200 OK responses, even after the provider stops listening - which means the docker container is still running.

It normally happens after 5-6 hours but in general, the timing is more or less random.

Code Snippet

No response

Contract ABI

No response

Errors

No response

Environment

node.js (older than v12)

Environment (Other)

docker, docker compose, AWS ECR

[varunsrin]

@ricmoo we’re running into this issue as well when using alchemy. the proximate cause is that their server fails for some reason, which i’m investigating with them.

but the underlying problem is that there is something in the getLogs call to a websocket provider that causes the process to hang and increase memory consumption constantly.

[mrunbanked]

Is it possible to implement some kind of reconnect logic upon timeout if the socket hangs?