Connection reset by peer (os error 54) when trying to get best block about eth-archive HOT 8 CLOSED

Hey, can you share all of the logs? I tried it locally, and there doesn't seem to be any problem with handling ports in the URL string.

from eth-archive.

Sure

[2023-02-08T12:07:07Z WARN  eth_archive_core::eth_client] excluding rpc url http://127.0.0.1:9650/ext/bc/2s8sfTnx6K5kEanTnaZcKVK6uvBnFPGC74g7CbYgPGphRkXnkZ/rpc because couldn't get best block:
    failed to execute http request:
    error sending request for url (http://127.0.0.1:9650/ext/bc/2s8sfTnx6K5kEanTnaZcKVK6uvBnFPGC74g7CbYgPGphRkXnkZ/rpc): connection closed before message completed
[2023-02-08T12:07:07Z ERROR eth_archive_core::retry] failed to run operation: no healthy rpc url found., retrying
[2023-02-08T12:07:20Z WARN  eth_archive_core::eth_client] excluding rpc url http://127.0.0.1:9650/ext/bc/2s8sfTnx6K5kEanTnaZcKVK6uvBnFPGC74g7CbYgPGphRkXnkZ/rpc because couldn't get best block:
    failed to execute http request:
    error sending request for url (http://127.0.0.1:9650/ext/bc/2s8sfTnx6K5kEanTnaZcKVK6uvBnFPGC74g7CbYgPGphRkXnkZ/rpc): connection error: Connection reset by peer (os error 54)
[2023-02-08T12:07:20Z ERROR eth_archive_core::retry] failed to run operation: no healthy rpc url found., retrying

Rpc endpoint is working, I checked it with postman:

from eth-archive.

thanks! can you send me your setup to reproduce this?

from eth-archive.

You can use this repo, I am testing eth-archive with it: https://github.com/metmirr/mini-network/. You need to install avalanchego binary https://github.com/ava-labs/avalanchego/releases/tag/v1.9.8 scripts/node*.sh assume the binary is installed globally but you can refer to the exact location by editing the scripts.

Only do this step: running nodes that all you need: https://github.com/metmirr/mini-network/#run-network

Optional Avalanche will not produce blocks without txs so if you want to test that just run npm hardhat run ./scripts/deploy.ts

from eth-archive.

It works on my m1 mac if I follow these steps

nevermind, It reproduces. sorry for impatience :)

from eth-archive.

I have found that the issue is because it has intermittent connection problems. Everything seems to be functional even though there are errors. It seems to be related to connection pooling and keep-alive configurations.

from eth-archive.

Glad that helped :)

from eth-archive.

thank you! closing this

from eth-archive.