Undergassed transaction seems to get wedged #148

New Issue

dboreham · 2024-06-17T03:04:04Z

dboreham commented

2024-06-17 03:04:04 +00:00

I found this problem diagnosing issues with the snowball front-end deployment scripts.
What I see is a record publish transaction fails with this error:

account sequence mismatch, expected 51, got 50: incorrect account sequence

The submitted sequence seems correct, based on this:

$ laconic -c config.staging.yml cns account get
[
  {
    "address": "ethm1z9q04ggayq0dr5t9552nerrhfxahv7u0ewcm66",
    "pubKey": "A1XR98GmfIivOdm+k4Q92EHlmr8kf9JdnHiD6JwOjrRz",
    "number": 14,
    "sequence": 50,
    "balance": [
      {
        "type": "aphoton",
        "quantity": 490000000
      }
    ]
  }
]

Previous to this there was another issue where the gas submitted with the record publish txn was insufficient,
leading to the theory that the undergassed transaction got stuck in the server leading to this wedged sequence number state.
Also according to @telackey this error has been seen before, but seemed to be transient.
I waited a couple days but the error persists.

I found this problem diagnosing issues with the snowball front-end deployment scripts. What I see is a record publish transaction fails with this error: ``` account sequence mismatch, expected 51, got 50: incorrect account sequence ``` The submitted sequence seems correct, based on this: ``` $ laconic -c config.staging.yml cns account get [ { "address": "ethm1z9q04ggayq0dr5t9552nerrhfxahv7u0ewcm66", "pubKey": "A1XR98GmfIivOdm+k4Q92EHlmr8kf9JdnHiD6JwOjrRz", "number": 14, "sequence": 50, "balance": [ { "type": "aphoton", "quantity": 490000000 } ] } ] ``` Previous to this there was another issue where the gas submitted with the record publish txn was insufficient, leading to the theory that the undergassed transaction got stuck in the server leading to this wedged sequence number state. Also according to @telackey this error has been seen before, but seemed to be transient. I waited a couple days but the error persists.

ashwin self-assigned this 2024-06-17 04:21:55 +00:00

zramsay commented

2024-06-17 13:01:20 +00:00

can confirm i've see this before, also as a transient error ... retrying would often fix it.

it's common to get this error on various cosmos chains, the same message gets passed through in keplr to the user and the support answer is to retry, which almost always does the trick

can confirm i've see this before, also as a transient error ... retrying would often fix it. it's common to get this error on various cosmos chains, the same message gets passed through in keplr to the user and the support answer is to retry, which almost always does the trick

Sign in to join this conversation.