Unresponsive to calls requiring archive node after long time

[JasperTimm]

This is an issue created from the discussion here: #2588

To summarise, it seems like after ganache has been running for more than a day or so as a fork of mainnet, calls which require use of an archive node are not responded to. The calls can be seen in logs but there's no response. Other transactions such as ETH transfers between accounts seem fine.

Details: ganache: 7.0.2 Node: v14.19 OS: Both MacOS and Ubuntu

After further testing, it seems like the issue always occurs when using the default mainnet provider (--fork.network 'mainnet') or when using the HTTP link for a custom node. It looks like the issue doesn't occur when using the WSS URL for the node.

[382303784]

Hi, is there an update on this question, I'm also having this problem now, is there a way I can fix this?

[davidmurdoch]

My hunch is that the default use of websockets instead of http is to blame. Use your own http url instead of the built in provider and see if that works.

[382303784]

At present, I have changed the http url, and used the archive node of the Ethereum-mainnet, and tested it for 10 hours, and there seems to be no problem.

[davidmurdoch]

Let me know if it makes it longer (or doesn't). I've personally run it for several weeks via HTTP with about 3 archive-access-required transactions per second.

[382303784]

Hi, I've been running the test for three days now with no issues and I'm still running, thanks for your help.