paritytech/polkadot-launch

Rococo polkadot-launch parachain doesn't create blocks

mffrench opened this issue · 2 comments

Hello,

I pushished some question in substrate stack exchange, however looking that this will close soon and I don't get helpfull answer to understand why my parachain is not producing blocks I do a try here. Also mainly cause I've the impression there is a bug somewhere and probably something to improve in polkadot-launch.

I tested rococo parachains launched thanks polkadot-launch. However I don't see any blocks created from the parachain so I'm wondering if this is normal and if I need to do extra steps to see blocks creation on the parachain.

Version double checks :

  • I'm using parity polkadot node version : 0.9.17-de0ecd4760-x86_64-linux-gnu
  • I'm using cumulus polkadot-collator node version : 5.2.0-76479e7f-x86_64-linux-gnu (the 76479e7f is the commit id for cumulus tag polkadot-v0.9.17)

Polkadot-launch input configuration :

{
	"relaychain": {
		"bin": "./bin/polkadot",
		"chain": "rococo-local",
		"nodes": [
			{
				"name": "alice",
				"wsPort": 9944,
				"port": 30444
			},
			{
				"name": "bob",
				"wsPort": 9955,
				"port": 30555
			},
			{
				"name": "charlie",
				"wsPort": 9966,
				"port": 30666
			},
			{
				"name": "dave",
				"wsPort": 9977,
				"port": 30777
			}
		],
		"genesis": {
			"runtime": {
				"runtime_genesis_config": {
					"configuration": {
						"config": {
							"validation_upgrade_frequency": 10,
							"validation_upgrade_delay": 10
						}
					}
				}
			}
		}
	},
	"parachains": [
		{
			"bin": "./bin/polkadot-collator",
			"id": "200",
			"balance": "1000000000000000000000",
			"nodes": [
				{
					"wsPort": 9988,
					"port": 31200,
					"name": "alice",
					"flags": ["--", "--execution=wasm"]
				}
			]
		},
		{
			"bin": "./bin/polkadot-collator",
			"id": "300",
			"balance": "1000000000000000000000",
			"nodes": [
				{
					"wsPort": 9999,
					"port": 31300,
					"name": "alice",
					"flags": ["--", "--execution=wasm"]
				}
			]
		}
	],
	"hrmpChannels": [
		{
			"sender": 200,
			"recipient": 300,
			"maxCapacity": 8,
			"maxMessageSize": 512
		}
	],
	"types": {},
	"finalization": false
}

First log analyses :

The first collator node connect to the parachain and synchronize its first relay chain with blocks 31 on epoch 3 :

2022-03-14 00:13:05 [Relaychain] 👴 Applying authority set change scheduled at block #31
2022-03-14 00:13:05 [Relaychain] 👴 Applying GRANDPA set change to new set [(Public(88dc3417d5058ec4b4503e0c12ea1a0a89be200fe98922423d4334014fa6b0ee (5FA9nQDV...)), 1), (Public(d17c2d7823ebf260fd138f2d7e27d114c0145d968b5ff5006125f2414fadae69 (5GoNkf6W...)), 1), (P
ublic(439660b36c6c03afafca027b910b4fecf99801834c62a5e6006f27d978de234f (5DbKjhNL...)), 1), (Public(5e639b43e0052c47447dac87d6fd2b6ec50bdd4d0f614e4299c665249bbd09d9 (5ECTwv6c...)), 1)]
...
2022-03-14 00:13:48 [Relaychain] 👶 New epoch 4 launching at block 0x1f0c…efdd (block slot 274536138 >= start slot 274536138).

However I never see [Parachain] Starting collation. in my logs. I waited till block 152 and epoch 15 with no success...

2022-03-14 00:24:48 [Relaychain] 👶 New epoch 15 launching at block 0x0898…5404 (block slot 274536248 >= start slot 274536248).
2022-03-14 00:24:48 [Relaychain] 👶 Next epoch starts at slot 274536258
2022-03-14 00:24:48 [Relaychain] ✨ Imported #151 (0x0898…5404)
2022-03-14 00:24:48 [Relaychain] Advanced session window for approvals update=Advanced { prev_window_start: 9, prev_window_end: 14, new_window_start: 10, new_window_end: 15 }
2022-03-14 00:24:51 [Relaychain] 💤 Idle (5 peers), best: #151 (0x0898…5404), finalized #148 (0x8570…2a6e), ⬇ 4.2kiB/s ⬆ 2.9kiB/s
2022-03-14 00:24:51 [Parachain] 💤 Idle (1 peers), best: #0 (0x0a8a…28c5), finalized #0 (0x0a8a…28c5), ⬇ 49 B/s ⬆ 49 B/s
2022-03-14 00:24:54 [Relaychain] ✨ Imported #152 (0xce66…efb4)

The block count on the parachain remains to 0 :(. Is there something I missed ?

Thank you for your coming help :)

This happens to me. Parachain stays at 0 for 1 hour until it starts producing blocks.

Excuse me @mffrench , when you started the blockchain at that time, did polkadot-js show that the parachain registration was successful? Is it a parachain or a parathread?

I had the same issue recently and then manually called slots.frocelease to upgrade parathread to parachain for it to work.