Error: Service(Client(Execution(Other("Exported method GrandpaApi_grandpa_authorities is not found")))) #4838
Labels
I2-bug
The node fails to follow expected behavior.
I10-unconfirmed
Issue might be valid, but it's not yet known.
Comments
letsbangout
added
I10-unconfirmed
|
It's worthy of note, I have an existing node running on the 'polkadot' binary provided by the project's apt repo, also on Ubuntu 20.04 LTS. When I copy the .json file above to that node and launch with the polkadot binary, the error output identical to above. |
|
If you want to start a parachain, use |
|
I wouldn't say I'm trying to "start" a parachain. I'm trying to run a node on asset-hub-polkadot. It doesn't work with the 'polkadot' binary as aforementioned. And I believe i've already tried with 'polkadot-parachain' with exactly the same result. Perhaps you could point to a guide showing how to get this going, because I don't think one exists and there is a gaping hole in the documentation in this regard. |
|
https://github.com/paritytech/polkadot-sdk/tree/master/cumulus#asset-hub- @kianenigma we need to make the more prominent. |
Thanks for the reply. Now it seems we're getting somewhere :) Note that I quoted this exact URL in my bug report. I hope you'll forgive my ignorance, mostly not knowing how things are done in the "polkadot world". But I am directed by your URL that I should build a binary called I've tried building As per above I have already tried the Finally, for the sake of completeness, I did build the Is there anything else I should try, or shall we reopen and call this one a bug? Thanks again. :) |
|
|
|
Fascinating. After running the above command, cargo decided to build me a binary called |
|
Okay perfect! |
|
Whereas this issue is still marked "open", and I'd like to point out that there is another glaring error in the docs: I see no indication as to what kind of system resources I have Kusama and Polkadot nodes running (on the Ubuntu 20.04 repo binary) for a few days now, both seem to only actually need about 1.6GB of RAM: and I am currently seeing an out-of-memory condition on Thanks. |
|
Edit: I have the The invocation is as follows: |
Which version are you using? |
This is the entire output, including version number. Note that it is quite slow to initialize the database, perhaps 5 minutes, which is much slower than my full archives of Polkadot and Kusama btw. Specifically I mean that the stage that says |
|
Please run with |
|
See below for the last 100 lines of the console log. If you need the whole thing I suppose I can pastebin it. |
|
Out of curiosity I re-launched this VM with 25GB of RAM, all other specs remaining equal to before. I no longer get an out-of-memory condition when launching. However, I see that despite having plenty of peers, the Parachain is no longer being updated. I'm mentioning this in case it is somehow connected to the out-of-memory problem. Unless we need more Relaychain blocks in order to advance the Parachain? See below. |
|
Scratch that, I did get another out-of-memory condition, running on 25GB RAM. All other parameters being equal. It's being invoked with: Here are the last 200 lines of the trace: |
|
Failed again with 25GB in the VM and a 10GB swap file activated. The common thread seems to be that the counters on these chains do not increment (Relaychain/best, Parachain/finalized): LMK what I can do to provide more useful info @bkchr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
Polkadot substrate-node fails to launch with asset-hub-[polkadot(-genesis)] or [westend]. Throws the following output:
Steps to reproduce
apt -y update
apt -y install build-essential
apt install --assume-yes git clang curl libssl-dev llvm libudev-dev make protobuf-compiler
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
git clone https://github.com/paritytech/polkadot-sdk
cd polkadot-sdk
cargo build --release --locked --bin substrate-node
The text was updated successfully, but these errors were encountered: