Timeline for Parachain keeps trying to start collation over and over again, without success. But no Error or Panic occurred
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2022 at 9:02 | comment | added | Ramsey - Decentration | whenever i get that warning i am usually on the wrong branch. So i need to make sure i have checkout and compiled the correct branch. | |
| Oct 17, 2022 at 17:28 | comment | added | Alexandre Ribeiro | Yes, indeed it works. But what happens after I insert the key is. 2022-10-17 14:25:47.587 WARN tokio-runtime-worker parachain::collator-protocol: Collation wasn't advertised to any validator. candidate_hash=0xe5c94d1cada5991c78b2ba39adf80aa90c96e085897beede55ac0f3241745075 pov_hash=0x0c8955bdc0f991fc543f8dcec038ecdb8ef445842a795ff5205265b95f0299c9 traceID=305438426720980369332937585534051027625 | |
| Oct 15, 2022 at 7:54 | comment | added | Ramsey - Decentration | The result null means there’s no error when inserting the key. You can check the keystore file in your directory where ever you added the —base-path (e.g. /home/…/parachain/keystore) and you will see the key in there. | |
| Oct 15, 2022 at 7:46 | comment | added | Ramsey - Decentration | That means success. I know that’s a confusing result, but that is expected. There is docs on this somewhere. | |
| Oct 15, 2022 at 0:18 | comment | added | Alexandre Ribeiro |
When I tried the curl, the output I got was {"jsonrpc":"2.0","result":null,"id":1} I must be missing something on the keystore. I'm going crazy with this D:
|
|
| Oct 15, 2022 at 0:10 | comment | added | Alexandre Ribeiro |
Still don't working. When I'm going to check the node's keystore by ls /tmp/parachain/mycol it shows two chain options instead of just one. Can you please check if that is correct? terminal outputs
|
|
| Oct 14, 2022 at 20:52 | history | edited | Ramsey - Decentration | CC BY-SA 4.0 |
added 321 characters in body
|
| Oct 14, 2022 at 20:51 | comment | added | Ramsey - Decentration | Then you can curl it in something like this: curl -vH 'Content-Type: application/json' --data '{ "jsonrpc":"2.0", "method":"author_insertKey", "params":["aura", "0x153d8db5f7ef35f18a456c049d6f6e2c723d6c18d1f9f6c9fbee880c2a171c73", "0x408f99b525d90cce76288245cb975771282c2cefa89d693b9da2cdbed6cd9152"],"id":1 }' localhost:9933 | |
| Oct 14, 2022 at 16:45 | comment | added | Alexandre Ribeiro | Yes, as I thought the error when trying to insert the keys into the parachain keystore returns me this: ./target/release/polkadot key insert --base-path /tmp/parachain/mld --chain rococo-para-2000-raw.json --scheme sr25519 --suri "<key>" --key-type aura Error: 0: Invalid input: Error parsing spec file: unknown field relay_chain at line 64 column 1 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. Run with RUST_BACKTRACE=full to include source snippets. | |
| Oct 14, 2022 at 15:31 | comment | added | Alexandre Ribeiro |
Yes, I'm using specific keys for both. In the Relay and in the Parachain. The thing is, how can I add those keys to the parachain keystore? The parachain build doesn't have the key subcommand. When I tried using the Relay binary to use it's key-insert I got a panic error. (rethinking now, it might work! ) Can I add the key subcommand in the cli.rs and commands.rs on my para node? And thanks for the help!! <3 I'll try to add it to the para's keystore.
|
|
| Oct 14, 2022 at 13:26 | history | answered | Ramsey - Decentration | CC BY-SA 4.0 |