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

Error: proposal failed (err: bad proposal response 500: cannot create ledger from genesis block: ledger [mychannel] already exists with state [ACTIVE]) After 5 attempts, peer0.1 has failed to join channel 'mychannel' #1097

Open
Piyushmethi09 opened this issue Oct 18, 2023 · 5 comments

Comments

@Piyushmethi09
Copy link

Error: proposal failed (err: bad proposal response 500: cannot create ledger from genesis block: ledger [mychannel] already exists with state [ACTIVE])
After 5 attempts, peer0.1 has failed to join channel 'mychannel'

@eveporras23
Copy link

eveporras23 commented Jan 6, 2024

@Piyushmethi09 Did you find a fix for this issue? I have the same.

@bestbeforetoday
Copy link
Member

I hit this error recently and the problem - for me at least - seemed to be Docker volumes hanging around from a previous time the Fabric network was created. This was resolved by running:

  1. ./network.sh down
  2. docker system prune --volumes

@ConstantRohmer
Copy link

I have the same error as you, but only while trying to add a second peer to the channel :
image

I don't understand why it attempts to recreate a channel, when I only want to add another peer to it.

If someone has a clue...

@lvxinnian
Copy link

I have the same error as you, but only while trying to add a second peer to the channel : image

I don't understand why it attempts to recreate a channel, when I only want to add another peer to it.

If someone has a clue...

Hello, have you solved this problem? I'm running into this issue now as well

@dave1725
Copy link

I hit this error recently and the problem - for me at least - seemed to be Docker volumes hanging around from a previous time the Fabric network was created. This was resolved by running:

  1. ./network.sh down
  2. docker system prune --volumes

this solved the issue for me! thank youu!

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

6 participants