Hyperledger: byfn.sh up: ERROR !!! FAILED to execute End-2-End Scenario.

0 votes

On running the command: ./byfn.sh up, I get this error:

 Starting with channel 'mychannel' and CLI timeout of '10' seconds and CLI delay of '3' seconds
    Continue? [Y/n] y
    proceeding ...
    2018-06-05 12:01:27.340 UTC [main] main -> INFO 001 Exiting.....
    peer0.org2.example.com is up-to-date
    peer1.org2.example.com is up-to-date
    orderer000.example.com is up-to-date
    peer1.org1.example.com is up-to-date
    peer000.org001.example.com is up-to-date
    cli is up-to-date

     ____    _____      _      ____    _____ 
    / ___|  |_   _|    / \    |  _ \  |_   _|
    \___ \    | |     / _ \   | |_) |   | |  
     ___) |   | |    / ___ \  |  _ <    | |  
    |____/    |_|   /_/   \_\ |_| \_\   |_|  

    Build your first network (BYFN) end-to-end test

    Channel name : mychannel
    Creating channel...
    + peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
    + res=1
    + set +x
    2018-06-05 12:01:30.704 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group]  /Channel/Application at version 0, but got version 1
      peer channel create [flags]

      -c, --channelID string   In case of a newChain command, the channel ID to create.
      -f, --file string        Configuration transaction file generated by a tool such as configtxgen for submitting to orderer
      -t, --timeout int        Channel creation timeout (default 5)

    Global Flags:
          --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
          --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
          --clientauth                          Use mutual TLS when communicating with the orderer endpoint
          --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
          --logging-level string                Default logging level and overrides, see core.yaml for full syntax
      -o, --orderer string                      Ordering service endpoint
          --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer.
          --tls                                 Use TLS when communicating with the orderer endpoint
      -v, --version                             Display current version of fabric peer server

    !!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
    ========= ERROR !!! FAILED to execute End-2-End Scenario ===========

    ERROR !!!! Test failed
Nov 6, 2018 in Blockchain by digger
• 27,620 points

4 answers to this question.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
+1 vote
Best answer

Try these commands

$ docker rm -f $(docker ps -aq)

This will remove all your containers

$ docker rmi -f $(docker image list -aq)

This will remove all your images

$ docker volume prune

This will remove all unused local volumes. Unused local volumes are those which are not referenced by any containers.

answered Nov 28, 2018 by kartik chauhan

selected Apr 26 by Omkar
Yup force removing the containers and images will work. But thats unhealthy. Like Omkar said, better stopping the container and then removing it is better right?
Hello Sir. Is removing all the images really necessary when just removing the container works?
Hey @Charan.

No, removing all the images is not really necessary
0 votes

First, stop all the containers:

docker stop $(docker ps -q)

then remove all containers:

docker rm $(docker ps -aq)

then change the names of the yaml files to their original names. Then try starting it all up again.

It should work

answered Nov 6, 2018 by Omkar
• 65,850 points
+1 vote

Try restarting the network

$ ./bfyn.sh down
$ ./bfyn.sh up
answered Apr 26 by Rajesh
0 votes

A network restart worked for me:

$ ./byfn.sh -m restart -c <channelName>
answered Apr 26 by Rishi
how to do this
Just run the above mentioned command...

Related Questions In Blockchain

0 votes
2 answers
0 votes
1 answer

Getting error when i execute ./byfn.sh -m up command.

The error is caused because you're trying ...READ MORE

answered Jul 12, 2018 in Blockchain by slayer
• 29,040 points
0 votes
1 answer

Hyperledger: ./byfn.sh -m up gives error

Open .env file in fabric-samples/first-network/  ...READ MORE

answered Oct 26, 2018 in Blockchain by Omkar
• 65,850 points
0 votes
1 answer

Hyperledger Fabric: ./byfn.sh -m up failed

Try adding GODEBUG=netdns=go to the environment variables ...READ MORE

answered Oct 26, 2018 in Blockchain by Omkar
• 65,850 points
0 votes
1 answer

How to fix "failed to execute script docker compose" error on windows 7?

It seems like the container is not ...READ MORE

answered Jun 27, 2018 in Blockchain by Omkar
• 65,850 points
0 votes
1 answer
0 votes
1 answer

Invalid Batch or signature in Savtooth

This will solve your problem import org.apache.commons.codec.binary.Hex; Transaction txn ...READ MORE

answered Aug 1, 2018 in Blockchain by digger
• 27,620 points
+1 vote
1 answer

© 2018 Brain4ce Education Solutions Pvt. Ltd. All rights Reserved.
"PMP®","PMI®", "PMI-ACP®" and "PMBOK®" are registered marks of the Project Management Institute, Inc. MongoDB®, Mongo and the leaf logo are the registered trademarks of MongoDB, Inc.