-
Notifications
You must be signed in to change notification settings - Fork 314
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
ERROR failed to spawn chain runtime: relayer error: RPC error to endpoint #3658
Comments
Thanks for the report! Can you please re-run the command that failed with the eg.
|
Here we go: 2023-10-13T20:27:57.281928Z INFO ThreadId(01) running Hermes v1.6.0+1c1cf02
2023-10-13T20:27:57.283746Z DEBUG ThreadId(01) Outgoing request: {
"jsonrpc": "2.0",
"id": "de361d46-3b8b-4fb1-8d24-1046c7dced11",
"method": "status",
"params": null
}
2023-10-13T20:27:57.484373Z DEBUG ThreadId(01) Incoming response: {"jsonrpc":"2.0","id":"de361d46-3b8b-4fb1-8d24-1046c7dced11","result":{"node_info":{"protocol_version":{"p2p":"8","block":"11","app":"0"},"id":"0d194f5236a420147b05d9556ac0cf928c36e647","listen_addr":"65.109.23.114:11756","network":"pisco-1","version":"0.37.2","channels":"40202122233038606100","moniker":"hello-terra-testrelay","other":{"tx_index":"on","rpc_address":"tcp://0.0.0.0:11757"}},"sync_info":{"latest_block_hash":"2B6CD648B9355F4A7294779B49892618C0A35FCAEB01314A97737B608464BE24","latest_app_hash":"6B403B26E89CAA0893D18E496F3573AC027A960C4E66231D62B39E567EB3543E","latest_block_height":"7873519","latest_block_time":"2023-10-13T20:27:50.456001077Z","earliest_block_hash":"F9A088A259FC93FED2B053BEB5C097DEC0B3984D975D5E23C882795D9F2AB2E6","earliest_app_hash":"48D600F209AAA3EA64A18444CD99B3E24EA1E65F4DC1925055BA36C424A0724E","earliest_block_height":"6660741","earliest_block_time":"2023-07-25T13:58:54.797854271Z","catching_up":false},"validator_info":{"address":"99281AC70CA77998969E24A595363E81BCF6FFCE","pub_key":{"type":"tendermint/PubKeyEd25519","value":"L1HjhqkxoL+lVG3hgZSR2ktUoil3aJvyxpUNWHSDNkE="},"voting_power":"0"}}}
2023-10-13T20:27:57.487989Z DEBUG ThreadId(04) Outgoing request: {
"jsonrpc": "2.0",
"id": "1578544c-7f58-4721-b61a-a20b7c07a586",
"method": "abci_query",
"params": {
"path": "store/ibc/key",
"data": "6368616E6E656C456E64732F706F7274732F7761736D2E7465727261316C756879326E676A3779306C717933766A656B33786D37373770797770747A7A656130736335796D7534706D61666A726E30377335726C6D78742F6368616E6E656C732F6368616E6E656C2D333534",
"prove": false
}
}
2023-10-13T20:27:57.611200Z DEBUG ThreadId(04) Incoming response: {"jsonrpc":"2.0","id":"1578544c-7f58-4721-b61a-a20b7c07a586","result":{"response":{"code":0,"log":"","info":"","index":"0","key":"Y2hhbm5lbEVuZHMvcG9ydHMvd2FzbS50ZXJyYTFsdWh5Mm5najd5MGxxeTN2amVrM3htNzc3cHl3cHR6emVhMHNjNXltdTRwbWFmanJuMDdzNXJsbXh0L2NoYW5uZWxzL2NoYW5uZWwtMzU0","value":"CAMQARpUCkV3YXNtLnN0YXJzMTY1ZnI1ajNlYTBkazV5cjVzcjRoOHV3NzZ6NWZkMzRscG5xYzJ4ODB5YTl4a3g5dTBrM3FqcnFwenESC2NoYW5uZWwtNTkwIg5jb25uZWN0aW9uLTQwOSoIaWNzNzIxLTE=","proofOps":null,"height":"7873519","codespace":""}}}
2023-10-13T20:27:57.730925Z DEBUG ThreadId(04) Outgoing request: {
"jsonrpc": "2.0",
"id": "f48d17d7-3934-43aa-b27f-6f3270219aec",
"method": "abci_query",
"params": {
"path": "store/ibc/key",
"data": "636C69656E74732F30372D74656E6465726D696E742D3435322F636C69656E745374617465",
"prove": false
}
}
2023-10-13T20:27:57.789098Z DEBUG ThreadId(04) Incoming response: <html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<hr><center>nginx/1.18.0 (Ubuntu)</center>
</body>
</html>
ERROR supervisor error: relayer error: RPC error to endpoint https://terra-testnet-rpc.polkachu.com/: serde parse error: expected value at line 1 column 1 |
Seems like |
I guess rate limiter gets into account. Depending in what state hermes is
|
Sometime I also get an Which is quite misleading, since channel does exist! |
Agreed, that's a very misleading error message, we'll fix it. |
Are you connecting to a public node? If so then there is not much that Hermes can do. I mean we could rate limit the requests that Hermes performs but that would totally kill performance. In general, one cannot expect to be able to operate a relayer using a public node, and should instead use a private, appropriately configured, node. |
Yes, connecting to a public node - so not locally. It would be great for having a |
Running Hermes 1.6.0. This error appears only when doing 2 hermes calls:
hermes start
hermes clear packets
Calling 1) or 2) works fine. You can test it like this: run 1)
hermes start
and then call 2) a couple of timeshermes --config ./config.toml clear packets --chain uni-6 --channel channel-721 --port wasm.juno1uvflayc34fs9r3tzcausztks2058ecpt5kqtzf3sz5kwnu7fjtfqn7zmtj
Then you get this error:
For testing use this config.toml:
The text was updated successfully, but these errors were encountered: