-
Notifications
You must be signed in to change notification settings - Fork 17
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
Evicting failed runtime instance error=Runtime panicked: Slot must increase #158
Comments
This error appears to be harmless (paritytech/polkadot-sdk#3282 (comment)). |
Yes the error is harmless. More information here. |
The two not invulnerables are kicked out of the active set tonight, only invulnerables left now. It seems more harmfull then thought. Also I cannot register as a candidate because my balance is insufficient although I've 15005 reserved TNKR and more then 500 TNKR tranferable. |
Is there any more info why they got kicked? Because they didn't produced any blocks or what? |
The error I described above turned out to be a bit more extensive after looking at the logs. This error precedes the error above: My node didn't produce any blocks since 02:46 h, only one block at 10:44 h. The errors stopped right after the node stopped producing blocks. |
Yes, the error is related to block production. Your node also did not try to build any blocks since 02:46. Looks like it got removed from the set? At 2:43 it for example still build successfully blocks:
|
It may be that the block has not reached the validator, because of this error? |
Should not be related. Did you check if any of the blocks it build made it into the canonical chain? |
After update to v1.7.0 the "[Parachain] Starting collation. relay_parent" stopped, so probably the blocks has never reached the validator. |
After the update of the collator or what? |
After updating collator to v1.7.0 and restarting node there is no collating. You can see in the tinkernet-collator.log I attached at a previous message.
|
There are collations:
And the block is also part of the canonical chain. |
I have no idea ;) Better to ask the experts like @arrudagates. |
Will do, thanks! |
After upgrade to v1.7.0 these errors showed up:
2024-05-09 18:38:19 [Parachain] Evicting failed runtime instance error=Runtime panicked: Slot must increase
2024-05-09 18:38:19 [Parachain] err=Error { inner: Proposing
0: Error at calling runtime api: Execution failed: Runtime panicked: Slot must increase
1: Execution failed: Runtime panicked: Slot must increase }
Ubuntu 22.04 LTS
Binary: tinkernet-collator 1.6.2-906e59161d7
ExecStart=tinkernet-collator
--collator
--chain tinker-raw.json
--base-path /path
--name "StakeWorks | Tinkernet | MEV02"
--force-authoring
--no-private-ipv4
--trie-cache-size 134217728
--max-runtime-instances 32
--bootnodes bootnode
--bootnodes bootnode
--bootnodes bootnode
--reserved-nodes node
--reserved-nodes node
--prometheus-port port
--prometheus-external
--listen-addr "/ip4/xx.xx.xx.xx/tcp/nnnnn/ws"
--listen-addr "/ip6/xx:xx:xx:xx:xx:xx/tcp/nnnnn/ws"
--rpc-port port
--out-peers 50
--in-peers 75
--relay-chain-rpc-urls "url"
--relay-chain-rpc-urls "url" \
The text was updated successfully, but these errors were encountered: