stacks-subnets icon indicating copy to clipboard operation
stacks-subnets copied to clipboard

sync halts at specific subnet block heights

Open deantchi opened this issue 1 year ago • 1 comments

it appears the subnet node halts syncing blocks at certain heights.
block 1 block 284 block 485

Restarting the subnet node at each halt seems to get it moving along again, but it stops progressing at 485.
This behavior has been repeatable consistently.
I've attached the subnet node chain state and logs for your review

subnet-node.log subnet.zip

deantchi avatar Apr 02 '23 20:04 deantchi

I'm seeing something similar on my local machine. Subnets stops minting blocks at height 495. I also see lots of messages in the logs that look like this:

Apr 25 14:03:00.705458 WARN Failed to submit miner commitment L1 transaction: ControllerError(RPCError: {"error":"transaction rejected","reason":"NotEnoughFunds","reason_data":{"actual":"0x0000000000000000000000a168746553","expected":"0x000000000000000000000389a591b6c3"},"txid":"2083ab4e0f1727fac3c808ca394e83a77d62d6b7d7ffdb1f8afaaf9f54d62d96"}) (ThreadId(21), testnet/stacks-node/src/neon_node.rs:2020)

It could be that around this height, whatever balance is given to the subnet during setup runs out, and the subnet is unable to pay the transaction fees to anchor a block in L1

jbencin avatar Apr 25 '23 14:04 jbencin