Open freak12techno opened 5 months ago
Might be the same issue: https://github.com/informalsystems/hermes/issues/3547
Hey @freak12techno is this still happening regularly?
@adizere I guess
Apr 02 23:46:59 monitoring-logging hermes[634298]: 2024-04-02T21:46:59.002990Z WARN ThreadId(25) worker.batch{chain=cosmoshub-4}:supervisor.handle_batch{chain=cosmoshub-4}:supervisor.process_batch{chain=cosmoshub-4}:worker.packet.cmd{src_chain=cosmoshub-4 src_port=transfer src_channel=channel-141 dst_chain=osmosis-1}:relay{odata=35f843ed ->Destination @4-19830002; len=1}:send_messages_and_wait_check_tx{chain=osmosis-1 tracking_id=35f843ed}:send_tx_with_account_sequence_retry{chain=osmosis-1 account.sequence=6071}:estimate_gas: failed to simulate tx, falling back on default gas because the error is potentially recoverable: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 6070, got 6071: incorrect account sequence [cosmos/cosmos-sdk@v0.47.8/x/auth/ante/sigverify.go:269] With gas wanted: '300000000' and gas used: '831344' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "14653501"} }
Summary of Bug
Getting a lot of "Account sequence mismatch" errors on osmosis-1 <=> cosmoshub-4 channel with the same sequence:
I guess when timing out it assumes that the tx went through and increases sequence while in fact the tx failed, but I may be wrong here.
Version
v1.8.0, although I've faced it a lot on 1.7.4 as well.
Steps to Reproduce
Logs illustrating the issue (I omitted some not relevant to this issue, let me know if you need all of them):
Acceptance Criteria
For Admin Use