Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Custom-flood after some time is not capable of producing new transactions with "AlreadyKnown" error #276

Open
kamilchodola opened this issue Oct 9, 2023 · 1 comment
Open

Custom-flood after some time is not capable of producing new transactions with "AlreadyKnown" error #276

kamilchodola opened this issue Oct 9, 2023 · 1 comment

Comments

@kamilchodola
Copy link
Contributor

Custom-flood recently works much more stable but recently recognized new issue.
After some time it started to output me plenty of "Already Known" errors when sending raw transactions:

root@localhost ➜  ~ kurtosis service logs verdant-forest mev-custom-flood -a | grep eth_sendRawTransaction | grep "Already"
20:10:16,624 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:19,659 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:22,686 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:25,714 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:28,742 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:31,774 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:34,803 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:37,830 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:40,858 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:43,886 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:46,915 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:49,942 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}
20:10:52,968 web3.providers.HTTPProvider DEBUG Getting response HTTP. URI: http://172.16.4.8:8545, Method: eth_sendRawTransaction, Response: {'jsonrpc': '2.0', 'error': {'code': -32010, 'message': 'AlreadyKnown'}, 'id': 5}

Once it start happening, it is being this way all the time.
@h4ck3rk3y
Copy link
Collaborator

Wonder if #283 will solve it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@h4ck3rk3y @kamilchodola