-
Notifications
You must be signed in to change notification settings - Fork 139
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.
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
indexer-agent always exits with fatal error: CALL_EXCEPTION for method: paused() #207
Comments
I found that I set the indexer address the same as the operator address initially ( before the token distribution) So I did the following steps.
All transactions succeded for an account: https://rinkeby.etherscan.io/address/0x3ad34B9dFaEefaeD3CdB2C60Ea93EAe60463DedF And the result is absolutely the same. I think there is a general issue in the interaction between index-agent and testnet contract dispatching address: Logs after step 3 |
The root cause of this error was the incorrect Ethereum node endpoint in the indexer agent and the indexer service configurations. It was set for Mainnet instead of Rinkeby. Anyway, it could be nice to implement better error handling for such a case. So I would like to keep it open untill the dev team makes a decision. |
I have the same error message when running on Mainnet. https://gist.github.com/begetan/6e4b2fb5021ee6b5b4917284ba9e40ec This time I doubled checked everything. The issue was with indexer-agent which doesn't work with OpenEthereum endpoint, while indexer-service does. It would be great to add here all kind of network checking and provides a correct error message instead of a fatal exception |
Issue created for adding more types of indexer configurations check such as ethereum endpoints: #448 |
Versions:
Environment:
Expected behavior:
After launch container should check all settings and provide notifications like "waiting for the node operator wallet approval from staking contract" It could be checked in the loop every 1-5 minutes.
Actual behavior:
Service exits with a fatal error. It makes it very hard to verify the configuration.
Logs:
https://gist.github.com/begetan/74d28161bb9ce7eb8fdc15eb1811fc8c
The text was updated successfully, but these errors were encountered: