Skip to content
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

Could not launch local network: Orchestrator error: Provider error #401

Open
Krayt78 opened this issue Jan 27, 2025 · 5 comments
Open

Could not launch local network: Orchestrator error: Provider error #401

Krayt78 opened this issue Jan 27, 2025 · 5 comments

Comments

@Krayt78
Copy link

Krayt78 commented Jan 27, 2025

I have been following the docs to run locally a parachain for development purposes.
After running these :

pop new parachain
cd my_parachain/
pop build --release
pop up parachain -f ./network.toml

I end up with this error

┌   Pop CLI : Launch a local network
│
◐  🚀 Launching local network...
└  🚫 Could not launch local network: Orchestrator error: Provider error

This is my network.toml

[relaychain]
chain = "paseo-local"

[[relaychain.nodes]]
name = "alice"
validator = true

[[relaychain.nodes]]
name = "bob"
validator = true

[[parachains]]
id = 2000
default_command = "./target/release/parachain-template-node"

[[parachains.collators]]
name = "collator-01"

Did i forget anything ?

@AlexD10S
Copy link
Collaborator

AlexD10S commented Feb 4, 2025

Thanks for reporting the issue.
I am trying to replicate it, but it seems to work fine on my end and I can't spot anything wrong with your steps. Could you provide more details?

  • What version of pop-cli are you using? You can check by running:
pop --version

If is not the last one pop-cli 0.6.0 you can try installing the last one with cargo install --force --locked pop-cli

  • Which template do you select when executing pop new parachain?
 Pop CLI : Generate a parachain
│
◆  Select a template provider: 
│  ● Pop (An all-in-one tool for Polkadot development. 4 available options)  
│  ○ OpenZeppelin  
│  ○ Parity

@Krayt78
Copy link
Author

Krayt78 commented Feb 4, 2025

  • What version of pop-cli are you using? You can check by running:

pop-cli 0.6.0

  • Which template do you select when executing pop new parachain?

Pop (An all-in-one tool for Polkadot development. 4 available options)

I tried to redo it again but still have the same issue
I am using wsl 2, in case that could cause an issue (shouldnt tho? )

@AlexD10S
Copy link
Collaborator

AlexD10S commented Feb 4, 2025

Apologies for the delayed response. I couldn't find the reason for your error.
I guess you picked the standard one after:

 Select the type of parachain:
│  ● Standard (A standard parachain)

Did the pop build --release go through successfully, or did you encounter any error messages?

I experienced a similar issue in the past (link), but it was due to a wrong network.toml file, which doesn't seem to be the case for you. Your network.toml file looks correct.

It might be a good idea to try removing this code:

[[parachains]]
id = 2000
default_command = "./target/release/parachain-template-node"

[[parachains.collators]]
name = "collator-01"

And run pop up -f ./network.toml again to see if it can launch the paseo-local network. This will help determine if the issue is with your generated binary.

@Krayt78
Copy link
Author

Krayt78 commented Feb 4, 2025

Apologies for the delayed response. I couldn't find the reason for your error. I guess you picked the standard one after:

 Select the type of parachain:
│  ● Standard (A standard parachain)

Did the pop build --release go through successfully, or did you encounter any error messages?

Yes i use the standard parachain
pop build --release goes through successfully

[[parachains]]
id = 2000
default_command = "./target/release/parachain-template-node"

[[parachains.collators]]
name = "collator-01"

even after removing this and Launching pop up parachain -f ./network.toml i still get the same error message 🚫 Could not launch local network: Orchestrator error: Provider error

@AlexD10S
Copy link
Collaborator

AlexD10S commented Feb 5, 2025

Thanks for your quick responses!
pop sources some binaries needed to launch a network and stores them in a cache file. You may have seen a message like:

➡️ Binaries will be cached at...

You can view the artifacts stored in the cache by running:

pop clean --help

This command will display the cache path and list the stored binaries.

ℹ️ The cache is located at: /Users/folder/Library/Caches/pop

Could you navigate to the cache path and check if there are any permission issues with the binaries? It’s possible that WSL2 is causing some issues there.

Under the hood, pop uses [zombienet-sdk](https://github.com/paritytech/zombienet), so if we can’t identify the issue, might be good to see if we can launch the network with Zombienet and open an issue there to see if they have any insights on how to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants