Search code examples
hyperledger-fabricblockchainhyperledger

Minifabric custom network

I am setting up a hyperledger fabric environment using the Minifabric tool. I am specifying the structure of my custom network in the spec.yaml file in the working directory:

fabric:
cas:
- "ca1.university.com"
- "ca2.university1.com"
- "ca3.university2.com"
- "ca4.org.com"
- "ca5.org.com"
peers: 
- "peer1.university1.com"
- "peer2.university1.com"
- "peer3.university1.com"
- "peer4.university1.com"
- "peer5.university1.com"
- "peer6.university1.com"
- "peer7.university1.com"
- "peer8.university1.com"
- "peer9.university1.com"
- "peer1.university2.com"
- "peer2.university2.com"
- "peer3.university2.com"
- "peer4.university2.com"
- "peer5.university2.com"
- "peer6.university2.com"
- "peer7.university2.com"
- "peer8.university2.com"
- "peer1.organization_x.com"
- "peer2.organization_x.com"
- "peer3.organization_x.com"
- "peer1.organization_y.com"
- "peer2.organization_y.com"
- "peer3.organization_y.com"
- "peer1.organization_z.com"
- "peer2.organization_z.com"
- "peer3.organization_z.com"
orderers:
- "orderer1.university1.com"
- "orderer2.university1.com"
- "orderer3.university1.com"
- "orderer1.university2.com"
- "orderer2.university2.com"
- "orderer3.university2.com"
- "orderer1.organization_x.com"
- "orderer1.organization_y.com"
- "orderer1.organization_z.com"
settings:
  ca:
    FABRIC_LOGGING_SPEC: DEBUG
  peer:
    FABRIC_LOGGING_SPEC: DEBUG
  orderer:
    FABRIC_LOGGING_SPEC: DEBUG

I gave the "./minifab up" command and got the following error: enter image description here Am I specifying the spec.yaml file in a wrong way? What could be the problem? TIA.

Solution

  • The organization that you've specified in spec.yaml is *.university.com. The default organization is org0.example.com and you can see that in the error as well Default option org is org0.example.com which does not exist in your spec, use -o to specify one.

    minifab is a bash file which in turn executes main.sh(/home/main.sh "$@"). main.sh accepts many arguments such as -c channel-name, -s database-type, and among them, one is -o organization as you can see here. If you're not using default organization and also not specifying one using the flag -o or --organization, then you'll get this error.

    You can see the CURRENT_ORG value in the image you attached and the value is org0.example.com.

    So, I suggest you to either use the default organization name or pass a new organization name by using the flag -o.