Getting error while adding another org #184

Vishesh1702 · 2023-10-07T15:15:59Z

I followed the same steps but while creating the org 2 i am not able to see the container of org2 in docker the steps i followed was
1:I created and copied the content from org_env and created org_env_1
2:I changed only org name ,Api port, domain, CA port
3:i sourced the org_env_1
4:then i deployed by running ./deploy-2x.sh

after running the command this is what i am getting

Cleaning up

0e2467d14682
10965e35715d
1ade5cec65a9
efb118e2b7a6
72e324a814f3
78b4b9dcb745
162b25eea1d3
47eb36fd651c
d07d0af6c418
75b0b05fc12c
c92cbb7185e4
d1d8b1a7e812
dd3f52be45eb
6424bc71a531
9311bcfa92e4
55b5c8c962fe
9a9eaa11a160
0d0fddebf561
d4dc83d1c29a
Deleted Volumes:
e6745ce5547a4c8ff9f24d1befc8f8a03aad712ebc50d0035a5d490cacff4a53
ce894b7482a21f78f1b699053343a984e78b6a5dcfb2d1dec930ed40fc8e43a7
e0048634425d96514d915c0673385d08211ba36d864e5acf21d769a50afe25cf
f68f053e19efd149cda803f30bb424e98894c830327c99d890daf5c4c4f74308
6326ce6c6916a2400dad0df1ff82f5dfb75914c1582d864fd695df18b002841d
d3a474dedb7951916c075ba4782c3302c6fd94628c78f8e412391f05ba952cfc
27d6a120ebbc90988059d7b8a4a45c6944ebd2459e985b4e5f0286fc767d65f2
c2f933c6e5678358329ce4a66aa16c8e520b1886fd3ffecadf6b8e0053a39d6a
2049540eedded643692734016d1a3457276d3cae776799be4247c9b89079193e
34c64c09b0727edf36ac1c348fe8dbd8d2f5766185c775c22be13b536d5198a6
aa512cf075fe31c29c7a4d8a51579d8e04c97838ac7fb7aecc40a9f63d27159c
f90ac61163b143cef94fc7c29b1d093effe922477374d473cedf9f9225103e4e
a97ccc6cc5a52e0e8e3a6dc0381e56b5dd4d65d72dcd6d5d7300bd9380fc7141
d85fce12845b2a670d40369420ff8c61b1fae1d75d2d9a0490c36d32f4dd9853

Total reclaimed space: 3.224MB
"docker rmi" requires at least 1 argument.
See 'docker rmi --help'.

Usage: docker rmi [OPTIONS] IMAGE [IMAGE...]

Remove one or more images
stable: Pulling from olegabu/fabric-tools-extended
Digest: sha256:a6071c10e6818cec535f5d9de28c00bcd363acb237f96c64fe732b3b4226c208
Status: Image is up to date for olegabu/fabric-tools-extended:stable
docker.io/olegabu/fabric-tools-extended:stable
stable: Pulling from olegabu/fabric-starter-rest
Digest: sha256:603dd03dd3c6f700a54b3dc9cc3844f1ef27a341eaea9734a0d5cd312bdeeece
Status: Image is up to date for olegabu/fabric-starter-rest:stable
docker.io/olegabu/fabric-starter-rest:stable
stable: Pulling from olegabu/fabric-sdk-api
Digest: sha256:88f947775ef03f3013b7e7dc9fd1fa5ac25894d99cbf92037bea1136b419c04e
Status: Image is up to date for olegabu/fabric-sdk-api:stable
docker.io/olegabu/fabric-sdk-api:stable
ORDERER_NAMES=orderer:7052,raft1:7150,raft2:7250

Using ORDERER_NAMES: orderer:7052,raft1:7150,raft2:7250

Parsed orderer: ORDERER_NAME_0:orderer, RAFT0_PORT:7052

Creating orderer service for example2.com, of type RAFT1

WWW_PORT=79
DOCKER_COMPOSE_ORDERER_ARGS='-f docker-compose-orderer.yaml -f docker-compose-orderer-domain.yaml -f docker-compose-orderer-ports.yaml'
./raft/0_raft-start-1-node.sh
Start Raft node orderer.example2.com
WARNING: The USER_ID variable is not set. Defaulting to a blank string.
Creating pre-install.orderer.example2.com ... done
Creating orderer.example2.com ... done
Creating www.example2.com ... done
Creating post-install.orderer.example2.com ... done
Creating cli.orderer.example2.com ... done
returnCode=0
set +x

Create first organization org1

docker-compose -f docker-compose-preload-images.yaml up -d
Creating org1_jre8-preload_1 ... done
BOOTSTRAP_IP=
ENROLL_SECRET=adminpw
docker-compose -f docker-compose.yaml -f docker-compose-couchdb.yaml -f docker-compose-ldap.yaml -f https/docker-compose-https-ports.yaml up -d --force-recreate
WARNING: The PEER_ADDRESS_TEMPLATE variable is not set. Defaulting to a blank string.
Creating ca.org1.example2.com ...
Creating couchdb.peer1.org1.example2.com ... done
Creating tlsca.org1.example2.com ... done
Creating sdk.org1.example2.com ... done
Creating www.org1.example2.com ... done
Creating ca.org1.example2.com ... done
Creating api.org1.example2.com ... done
Creating ldapadmin.org1.example2.com ... done
Creating peer1.org1.example2.com ... done
Creating post-install.peer1.org1.example2.com ... done
Creating cli.peer1.org1.example2.com ... done
Creating www.peer.org1.example2.com ... done
docker exec -t ldap.org1.example2.com bash -c 'set -x; creatorsName=slapcat|grep "creatorsName:"; adminDN=${creatorsName:14}; ldapadd -x -D "${adminDN}" -w "${LDAP_ADMIN_PASSWORD}" -f /etc/hyperledger/crypto-config/ldap/admin.ldif'
++ slapcat
++ grep creatorsName:
creatorsName='creatorsName: cn=admin,dc=example2,dc=com'
adminDN=cn=admin,dc=example2,dc=com
ldapadd -x -D cn=admin,dc=example2,dc=com -w adminpw -f /etc/hyperledger/crypto-config/ldap/admin.ldif
adding new entry "cn=admin,dc=example2,dc=com"
set +x
++ : wget -P
++ export GENERATE_DIR=crypto-config
++ GENERATE_DIR=crypto-config
++ set +x
Waiting for peer1.org1.example2.com:7058
Result code: 143
Terminated
/etc/hyperledger/crypto-config/peerOrganizations/
├── org1.example.com
│ ├── ca
│ │ ├── ca.org1.example.com-cert.pem
│ │ └── sk.pem
│ ├── msp
│ │ ├── admincerts
│ │ │ ├── [email protected]
│ │ │ └── [email protected]
│ │ ├── cacerts
│ │ │ ├── ca.example.com-cert.pem
│ │ │ └── ca.org1.example.com-cert.pem
│ │ ├── orderer.example.com
│ │ │ └── tls
│ │ │ └── server.crt
│ │ ├── tlscacerts
│ │ │ ├── tlsca.example.com-cert.pem
│ │ │ └── tlsca.org1.example.com-cert.pem
│ │ └── well-known
│ │ ├── msp-admin.pem
│ │ └── tlsca-cert.pem
│ ├── peers
│ │ └── peer0.org1.example.com
│ │ ├── msp
│ │ │ ├── admincerts
│ │ │ │ └── [email protected]
│ │ │ ├── cacerts
│ │ │ │ └── ca.org1.example.com-cert.pem
│ │ │ ├── keystore
│ │ │ │ └── priv_sk
│ │ │ ├── signcerts
│ │ │ │ └── peer0.org1.example.com-cert.pem
│ │ │ └── tlscacerts
│ │ │ └── tlsca.org1.example.com-cert.pem
│ │ └── tls
│ │ ├── ca.crt
│ │ ├── server.crt
│ │ └── server.key
│ ├── tlsca
│ │ ├── sk.pem
│ │ └── tlsca.org1.example.com-cert.pem
│ └── users
│ ├── [email protected]
│ │ ├── msp
│ │ │ ├── admincerts
│ │ │ │ └── [email protected]
│ │ │ ├── cacerts
│ │ │ │ └── ca.org1.example.com-cert.pem
│ │ │ ├── keystore
│ │ │ │ └── sk.pem
│ │ │ ├── signcerts
│ │ │ │ └── [email protected]
│ │ │ └── tlscacerts
│ │ │ └── tlsca.org1.example.com-cert.pem
│ │ └── tls
│ │ ├── ca.crt
│ │ ├── client.crt
│ │ └── client.key
│ └── [email protected]
│ ├── msp
│ │ ├── admincerts
│ │ │ └── [email protected]
│ │ ├── cacerts
│ │ │ └── ca.org1.example.com-cert.pem
│ │ ├── keystore
│ │ │ └── sk.pem
│ │ ├── signcerts
│ │ │ └── [email protected]
│ │ └── tlscacerts
│ │ └── tlsca.org1.example.com-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── client.crt
│ └── client.key
└── org1.example2.com
├── ca
│ ├── ca.org1.example2.com-cert.pem
│ ├── priv_sk
│ └── sk.pem
├── msp
│ ├── admincerts
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ └── ca.org1.example2.com-cert.pem
│ ├── cacerts
│ │ ├── ca.example2.com-cert.pem
│ │ └── ca.org1.example2.com-cert.pem
│ ├── orderer.example2.com
│ │ └── tls
│ │ └── server.crt
│ ├── tlscacerts
│ │ ├── tlsca.example2.com-cert.pem
│ │ └── tlsca.org1.example2.com-cert.pem
│ └── well-known
│ ├── msp-admin.pem
│ └── tlsca-cert.pem
├── peers
│ ├── peer0.org1.example2.com
│ │ ├── msp
│ │ │ ├── admincerts
│ │ │ │ └── [email protected]
│ │ │ ├── cacerts
│ │ │ │ └── ca.org1.example2.com-cert.pem
│ │ │ ├── keystore
│ │ │ │ └── priv_sk
│ │ │ ├── signcerts
│ │ │ │ └── peer0.org1.example2.com-cert.pem
│ │ │ └── tlscacerts
│ │ │ └── tlsca.org1.example2.com-cert.pem
│ │ └── tls
│ │ ├── ca.crt
│ │ ├── server.crt
│ │ └── server.key
│ └── peer1.org1.example2.com
│ ├── msp
│ │ ├── admincerts
│ │ │ └── [email protected]
│ │ ├── cacerts
│ │ │ └── ca.org1.example2.com-cert.pem
│ │ ├── keystore
│ │ │ └── priv_sk
│ │ ├── signcerts
│ │ │ └── peer1.org1.example2.com-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.org1.example2.com-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── server.crt
│ └── server.key
├── tlsca
│ ├── priv_sk
│ ├── sk.pem
│ └── tlsca.org1.example2.com-cert.pem
└── users
├── [email protected]
│ ├── msp
│ │ ├── admincerts
│ │ │ └── [email protected]
│ │ ├── cacerts
│ │ │ └── ca.org1.example2.com-cert.pem
│ │ ├── keystore
│ │ │ └── sk.pem
│ │ ├── signcerts
│ │ │ └── [email protected]
│ │ └── tlscacerts
│ │ └── tlsca.org1.example2.com-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── client.crt
│ └── client.key
└── [email protected]
├── msp
│ ├── admincerts
│ │ └── [email protected]
│ ├── cacerts
│ │ └── ca.org1.example2.com-cert.pem
│ ├── keystore
│ │ └── sk.pem
│ ├── signcerts
│ │ └── [email protected]
│ └── tlscacerts
│ └── tlsca.org1.example2.com-cert.pem
└── tls
├── ca.crt
├── client.crt
└── client.key

80 directories, 85 files

Install DNS chaincode

Install chaincode package /opt/chaincode/2x/node/dns-chaincode.tgz
Error: failed to retrieve endorser client for install: endorser client failed to connect to peer1.org1.example2.com:7058: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup peer1.org1.example2.com: no such host"
Usage:
peer lifecycle chaincode install [flags]

Flags:
--connectionProfile string The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
-h, --help help for install
--peerAddresses stringArray The addresses of the peers to connect to
--targetPeer string When using a connection profile, the name of the peer to target for this action
--tlsRootCertFiles stringArray If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

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
--connTimeout duration Timeout for client to connect (default 3s)
--keyfile string Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
-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
--tlsHandshakeTimeShift duration The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint

++ : wget -P
++ export GENERATE_DIR=crypto-config
++ GENERATE_DIR=crypto-config
++ set +x

Init Open Net. Add myself to Consortium

API_PORT=4010
BASE64_UNWRAP_CODE=| tr -d '\n'
BASE64_WRAP_OPT=-w
BOOTSTRAP_EXTERNAL_PORT=4010
BOOTSTRAP_IP=
BOOTSTRAP_SERVICE_URL=https
CORE_PEER_ADDRESS=peer1.org1.example2.com:7058
CORE_PEER_LOCALMSPID=org1
CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/crypto-config/peerOrganizations/org1.example2.com/users/[email protected]/msp
CORE_PEER_TLS_ENABLED=true
CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/crypto-config/peerOrganizations/org1.example2.com/peers/peer1.org1.example2.com/tls/ca.crt
DOMAIN=example2.com
ENROLL_ID=admin
ENROLL_SECRET=adminpw
FABRIC_CFG_PATH=/etc/hyperledger/fabric
FABRIC_VERSION=2.3
GENERATE_DIR=crypto-config
GOLANG_VERSION=1.16.7
GOPATH=/go
HOME=/root
HOSTNAME=0f850a609188
MY_IP=
ORDERER_BATCH_TIMEOUT=2
ORDERER_DOMAIN=example2.com
ORDERER_GENERAL_LISTENPORT=7052
ORDERER_NAME=orderer
ORDERER_NAMES=orderer
ORDERER_WWW_PORT=79
ORG=org1
PATH=/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PEER0_PORT=7058
PEER_ADDRESS_PREFIX=peer1.
PEER_NAME=peer1
PWD=/etc/hyperledger
RAFT0_CONSENTER_PORT=7050
RAFT1_CONSENTER_PORT=7150
RAFT2_CONSENTER_PORT=7250
SHLVL=2
SIGNATURE_HASH_FAMILY=SHA2
SYSTEM_CHANNEL_ID=orderer-system-channel
VERSIONED_CHAINCODE_PATH=/opt/chaincode/2x
WGET_CMD=wget -P
WWW_PORT=80
_=/usr/bin/env
API_PORT=4010
BASE64_UNWRAP_CODE=| tr -d '\n'
BASE64_WRAP_OPT=-w
BOOTSTRAP_EXTERNAL_PORT=4010
BOOTSTRAP_IP=
BOOTSTRAP_SERVICE_URL=https
CORE_PEER_ADDRESS=peer1.org1.example2.com:7058
CORE_PEER_LOCALMSPID=org1
CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/crypto-config/peerOrganizations/org1.example2.com/users/[email protected]/msp
CORE_PEER_TLS_ENABLED=true
CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/crypto-config/peerOrganizations/org1.example2.com/peers/peer1.org1.example2.com/tls/ca.crt
DOMAIN=example2.com
ENROLL_ID=admin
ENROLL_SECRET=adminpw
FABRIC_CFG_PATH=/etc/hyperledger/fabric
FABRIC_VERSION=2.3
GENERATE_DIR=crypto-config
GOLANG_VERSION=1.16.7
GOPATH=/go
HOME=/root
HOSTNAME=0f850a609188
MY_IP=
ORDERER_BATCH_TIMEOUT=2
ORDERER_DOMAIN=example2.com
ORDERER_GENERAL_LISTENPORT=7052
ORDERER_NAME=orderer
ORDERER_NAMES=orderer
ORDERER_WWW_PORT=79
ORG=org1
PATH=/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PEER0_PORT=7058
PEER_ADDRESS_PREFIX=peer1.
PEER_NAME=peer1
PWD=/etc/hyperledger
RAFT0_CONSENTER_PORT=7050
RAFT1_CONSENTER_PORT=7150
RAFT2_CONSENTER_PORT=7250
SHLVL=2
SIGNATURE_HASH_FAMILY=SHA2
SYSTEM_CHANNEL_ID=orderer-system-channel
VERSIONED_CHAINCODE_PATH=/opt/chaincode/2x
WGET_CMD=wget -P
WWW_PORT=80
_=/usr/bin/env

wget -P crypto-config/ordererOrganizations/example2.com/msp/admincerts http://www.example2.com:80/node-certs/orderer.example2.com/msp/admincerts/[email protected]
Connecting to www.example2.com:80 (172.18.0.3:80)
wget: can't open 'crypto-config/ordererOrganizations/example2.com/msp/admincerts/[email protected]': File exists
wget -P crypto-config/ordererOrganizations/example2.com/msp/cacerts http://www.example2.com:80/node-certs/orderer.example2.com/msp/cacerts/ca.example2.com-cert.pem
Connecting to www.example2.com:80 (172.18.0.3:80)
wget: can't open 'crypto-config/ordererOrganizations/example2.com/msp/cacerts/ca.example2.com-cert.pem': File exists
wget -P crypto-config/ordererOrganizations/example2.com/msp/tlscacerts http://www.example2.com:80/node-certs/orderer.example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
Connecting to www.example2.com:80 (172.18.0.3:80)
wget: can't open 'crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem': File exists
set +x
Connecting to www.example2.com:80 (172.18.0.3:80)
wget: can't open 'crypto-config/ordererOrganizations/example2.com/msp/orderer.example2.com/tls/server.crt': File exists
mkdir -p crypto-config/configtx

Trying to create channel common

Create channel org1 common

envsubst
cat crypto-config/configtx.yaml

Organizations:

- &OrdererOrg
    Name: Orderer
    ID: orderer.example2.com
    MSPDir: /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp

- &firstOrg
    Name: org1
    ID: org1
    MSPDir: /etc/hyperledger/crypto-config/peerOrganizations/org1.example2.com/msp
    AnchorPeers:
    # AnchorPeers defines the location of peers which can be used
    # for cross org gossip communication.  Note, this value is only
    # encoded in the genesis block in the Application section context
    - Host: peer1.org1.example2.com
      Port: 7058
    Policies: &OrgPolicies
      Readers:
        Type: Signature
        Rule: "OR('org1.member')"
      Writers:
        Type: Signature
        Rule: "OR('org1.member')"
      Admins:
        Type: Signature
        Rule: "OR('org1.admin')"
      Endorsement:
        Type: Signature
        Rule: "OR('org1.member')"

Capabilities:

Global: &ChannelCapabilities

V1_1: true

Orderer: &OrdererCapabilities
# V1_1: true
V2_0: true
Application: &ApplicationCapabilities
# V1_2: true
V2_0: true
Channel: &ChannelCapabilities
# V1_3: true
V2_0: true

Application: &ApplicationDefaults
ACLs: &ACLsDefault
# This section provides defaults for policies for various resources
# in the system. These "resources" could be functions on system chaincodes
# (e.g., "GetBlockByNumber" on the "qscc" system chaincode) or other resources
# (e.g.,who can receive Block events). This section does NOT specify the resource's
# definition or API, but just the ACL policy for it.
#
# User's can override these defaults with their own policy mapping by defining the
# mapping under ACLs in their channel definition

#---New Lifecycle System Chaincode (_lifecycle) function to policy mapping for access control--#

# ACL policy for _lifecycle's "CheckCommitReadiness" function
_lifecycle/CheckCommitReadiness: /Channel/Application/Writers

# ACL policy for _lifecycle's "CommitChaincodeDefinition" function
_lifecycle/CommitChaincodeDefinition: /Channel/Application/Writers

# ACL policy for _lifecycle's "QueryChaincodeDefinition" function
_lifecycle/QueryChaincodeDefinition: /Channel/Application/Writers

# ACL policy for _lifecycle's "QueryChaincodeDefinitions" function
_lifecycle/QueryChaincodeDefinitions: /Channel/Application/Writers


# 2.x ACL policy for cscc's "GetChannelConfig" function
cscc/GetChannelConfig: /Channel/Application/Readers


#---Lifecycle System Chaincode (lscc) function to policy mapping for access control---#

# ACL policy for lscc's "getid" function
lscc/ChaincodeExists: /Channel/Application/Readers

# ACL policy for lscc's "getdepspec" function
lscc/GetDeploymentSpec: /Channel/Application/Readers

# ACL policy for lscc's "getccdata" function
lscc/GetChaincodeData: /Channel/Application/Readers

# ACL Policy for lscc's "getchaincodes" function
lscc/GetInstantiatedChaincodes: /Channel/Application/Readers

#---Query System Chaincode (qscc) function to policy mapping for access control---#

# ACL policy for qscc's "GetChainInfo" function
qscc/GetChainInfo: /Channel/Application/Readers

# ACL policy for qscc's "GetBlockByNumber" function
qscc/GetBlockByNumber: /Channel/Application/Readers

# ACL policy for qscc's  "GetBlockByHash" function
qscc/GetBlockByHash: /Channel/Application/Readers

# ACL policy for qscc's "GetTransactionByID" function
qscc/GetTransactionByID: /Channel/Application/Readers

# ACL policy for qscc's "GetBlockByTxID" function
qscc/GetBlockByTxID: /Channel/Application/Readers

#---Configuration System Chaincode (cscc) function to policy mapping for access control---#

# ACL policy for cscc's "GetConfigBlock" function
cscc/GetConfigBlock: /Channel/Application/Readers

# ACL policy for cscc's "GetConfigTree" function
cscc/GetConfigTree: /Channel/Application/Readers

# ACL policy for cscc's "SimulateConfigTreeUpdate" function
cscc/SimulateConfigTreeUpdate: /Channel/Application/Readers

#---Miscellanesous peer function to policy mapping for access control---#

# ACL policy for invoking chaincodes on peer
peer/Propose: /Channel/Application/Writers

# ACL policy for chaincode to chaincode invocation
peer/ChaincodeToChaincode: /Channel/Application/Readers

#---Events resource to policy mapping for access control###---#

# ACL policy for sending block events
event/Block: /Channel/Application/Readers

# ACL policy for sending filtered block events
event/FilteredBlock: /Channel/Application/Readers

Organizations lists the orgs participating on the application side of the

network.

Organizations:

Policies defines the set of policies at this level of the config tree

For Application policies, their canonical path is

/Channel/Application/

Policies: &ApplicationDefaultPolicies

LifecycleEndorsement:

Type: ImplicitMeta

Rule: "MAJORITY Endorsement"

Endorsement:

Type: ImplicitMeta

Rule: "MAJORITY Endorsement"

Readers:

Type: ImplicitMeta

Rule: "ANY Readers"

Writers:

Type: ImplicitMeta

Rule: "ANY Writers"

Admins:

Type: ImplicitMeta

Rule: "MAJORITY Admins"

Capabilities describes the application level capabilities, see the

dedicated Capabilities section elsewhere in this file for a full

description

Capabilities:
<<: *ApplicationCapabilities

Orderer: &OrdererDefaults

# Batch Timeout: The amount of time to wait before creating a batch
BatchTimeout: 2s

# Batch Size: Controls the number of messages batched into a block
BatchSize:

    # Max Message Count: The maximum number of messages to permit in a batch
    MaxMessageCount: 10

    # Absolute Max Bytes: The absolute maximum number of bytes allowed for
    # the serialized messages in a batch.
    AbsoluteMaxBytes: 98 MB

    # Preferred Max Bytes: The preferred maximum number of bytes allowed for
    # the serialized messages in a batch. A message larger than the preferred
    # max bytes will result in a batch larger than preferred max bytes.
    PreferredMaxBytes: 512 KB

Kafka:
    # Brokers: A list of Kafka brokers to which the orderer connects
    # NOTE: Use IP:port notation
    Brokers:
        - 127.0.0.1:9092

# Organizations is the list of orgs which are defined as participants on
# the orderer side of the network
Organizations:

Profiles:

CHANNEL:
    Orderer:
      Policies:
        Readers:
          Type: ImplicitMeta
          Rule: ANY Readers
        Writers:
          Type: ImplicitMeta
          Rule: ANY Writers
        Admins:
          Type: ImplicitMeta
          #          Rule: MAJORITY Admins
          Rule: ANY Admins
        BlockValidation:
          Type: ImplicitMeta
          Rule: ANY Writers
      Organizations:
      - <<: *OrdererOrg
        Policies:
          Readers:
            Type: ImplicitMeta
            Rule: ANY Readers
          Writers:
            Type: ImplicitMeta
            Rule: ANY Writers
          Admins:
            Type: ImplicitMeta
            #          Rule: MAJORITY Admins
            Rule: ANY Admins
          BlockValidation:
            Type: ImplicitMeta
            Rule: ANY Writers
    Consortium: SampleConsortium
    Policies:
      Readers:
        Type: ImplicitMeta
        Rule: "ANY Readers"
      Writers:
        Type: ImplicitMeta
        Rule: "ANY Writers"
      Admins:
        #                Type: ImplicitMeta
        #                Rule: "ANY Admins"
        Type: Signature
        Rule: "OutOf('1','org1.admin')"
    Application:
        <<: *ApplicationDefaults
        Organizations:
            - <<: *firstOrg
              Policies:
                <<: *OrgPolicies
        Capabilities:
            <<: *ApplicationCapabilities
        Policies:
          LifecycleEndorsement:

Type: ImplicitMeta

Rule: ANY MEMBER

            Type: Signature
            Rule: "OutOf('1','org1.member')"
          Endorsement:

Type: ImplicitMeta

Rule: "MAJORITY Writers"

Type: Signature

Rule: "OutOf('1','org1.member')"

             Type: ImplicitMeta
             Rule: "ANY Writers"
          Readers:

printYellow '\n configtxgen \n'
printInColor '1;33' '\n configtxgen \n'
color1='1;33'
message1='\n configtxgen \n'
color2=
message2=
echo -e '\033[1;33m\n configtxgen \n\033[m\033[m\033[m'
configtxgen -configPath crypto-config/ -outputCreateChannelTx crypto-config/configtx/channel_common.tx -profile CHANNEL -channelID common
Type: ImplicitMeta
Rule: "ANY Readers"
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
Admins:

Type: ImplicitMeta

Rule: "ANY Admins"

            Type: Signature
            Rule: "OutOf('1','org1.admin')"

Admins:

Type: ImplicitMeta

Rule: "MAJORITY Admins"

configtxgen

2023-10-07 15:12:32.948 UTC [common.tools.configtxgen] main -> INFO 001 Loading configuration
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 002 Orderer.OrdererType unset, setting to solo
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 Orderer.BatchTimeout unset, setting to 2s
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 004 Orderer.BatchSize.MaxMessageCount unset, setting to 500
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 005 Orderer.BatchSize.AbsoluteMaxBytes unset, setting to 10485760
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 006 Orderer.BatchSize.PreferredMaxBytes unset, setting to 2097152
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 007 orderer type: solo
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen.localconfig] Load -> INFO 008 Loaded configuration: crypto-config/configtx.yaml
2023-10-07 15:12:32.954 UTC [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 009 Generating new channel configtx
2023-10-07 15:12:32.962 UTC [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 00a Writing new channel tx

printYellow '\n peer channel create \n'
printInColor '1;33' '\n peer channel create \n'
color1='1;33'
message1='\n peer channel create \n'
color2=
message2=
echo -e '\033[1;33m\n peer channel create \n\033[m\033[m\033[m'

peer channel create

peer channel create -o orderer.example2.com:7052 -c common -f crypto-config/configtx/channel_common.tx --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
2023-10-07 15:12:33.098 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Error: got unexpected status: FORBIDDEN -- config update for existing channel did not pass initial checks: implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Writers' sub-policies to be satisfied: permission denied
set +x
Put certs to env for org1.example2.com
org1 is updating channel common config with ./templates/AnchorPeers.json, peer0Port: outputFile: crypto-config/configtx/updated_config.json adminOrg:
Execute: channel fetch config crypto-config/configtx/common.pb -o orderer.example2.com:7052 -c common --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
2023-10-07 15:12:33.248 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-10-07 15:12:33.252 UTC [cli.common] readBlock -> INFO 002 Expect block, but got status: &{SERVICE_UNAVAILABLE}
Error: can't read the block: &{SERVICE_UNAVAILABLE}
configtxlator: error: open crypto-config/configtx/common.pb: no such file or directory, try --help
jq: error: Could not open file crypto-config/configtx/common.json: No such file or directory
Prepare updated config crypto-config/configtx/new_config_org1.json

Prepare config update from org1 for channel common
configtxlator: error: Error decoding: error decoding input: error unmarshaling intermediate JSON: EOF
cat: can't open 'crypto-config/configtx/update.json': No such file or directory
parse error: Unmatched '}' at line 1, column 98
configtxlator: error: Error decoding: error decoding input: error unmarshaling intermediate JSON: EOF
org1 is sending channel update update_in_envelope.pb with by
Execute: peer channel update -f update_in_envelope.pb -c common -o orderer.example2.com:7052 --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
2023-10-07 15:12:34.812 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Error: Invalid channel create transaction : bad header

Channel 'common' cannot be created or already exists

Sat Oct 7 15:12:37 UTC 2023
Waiting for server is accessible: orderer.example2.com:7052

nc orderer.example2.com 7052 -z
RES=0
set +x
Probe of orderer.example2.com:7052 is successful
Sat Oct 7 15:12:37 UTC 2023
sleep 30
set +x

Joining channel 'common, try 1 '

Join org1 to channel common
Execute: channel fetch 0 crypto-config/configtx/common.pb -o orderer.example2.com:7052 -c common --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
Error: failed to create deliver client for orderer: orderer client failed to connect to orderer.example2.com:7052: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 172.18.0.2:7052: connect: connection refused"
Error: error getting endorser client for channel: endorser client failed to connect to peer1.org1.example2.com:7058: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup peer1.org1.example2.com: no such host"
Status: 1

Joining channel 'common, try 2 '

Join org1 to channel common
Execute: channel fetch 0 crypto-config/configtx/common.pb -o orderer.example2.com:7052 -c common --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
2023-10-07 15:13:22.826 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-10-07 15:13:22.829 UTC [cli.common] readBlock -> INFO 002 Expect block, but got status: &{SERVICE_UNAVAILABLE}
Error: can't read the block: &{SERVICE_UNAVAILABLE}
Error: error getting endorser client for channel: endorser client failed to connect to peer1.org1.example2.com:7058: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup peer1.org1.example2.com: no such host"
Status: 1

Joining channel 'common, try 3 '

Join org1 to channel common
Execute: channel fetch 0 crypto-config/configtx/common.pb -o orderer.example2.com:7052 -c common --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
2023-10-07 15:13:34.707 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-10-07 15:13:34.710 UTC [cli.common] readBlock -> INFO 002 Expect block, but got status: &{SERVICE_UNAVAILABLE}
Error: can't read the block: &{SERVICE_UNAVAILABLE}
Error: error getting endorser client for channel: endorser client failed to connect to peer1.org1.example2.com:7058: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 172.18.0.4:7058: connect: connection refused"
Status: 1

Not joined to 'common'

Error: failed to retrieve endorser client for queryinstalled: endorser client failed to connect to peer1.org1.example2.com:7058: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup peer1.org1.example2.com: no such host"
Usage:
peer lifecycle chaincode queryinstalled [flags]

Flags:
--connectionProfile string The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
-h, --help help for queryinstalled
-O, --output string The output format for query results. Default is human-readable plain-text. json is currently the only supported format.
--peerAddresses stringArray The addresses of the peers to connect to
--targetPeer string When using a connection profile, the name of the peer to target for this action
--tlsRootCertFiles stringArray If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

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
--connTimeout duration Timeout for client to connect (default 3s)
--keyfile string Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
-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
--tlsHandshakeTimeShift duration The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint

Approving chaincode:

++ peer lifecycle chaincode queryapproved --channelID common --name dns
++ grep ''

local SEQUENCE=
set +x
peer lifecycle chaincode approveformyorg -o orderer.example2.com:7052 --channelID common --name dns --version 1.0 --package-id --sequence 1 --tls --cafile /etc/hyperledger/crypto-config/ordererOrganizations/example2.com/msp/tlscacerts/tlsca.example2.com-cert.pem
Error: failed to retrieve endorser client for approveformyorg: endorser client failed to connect to peer1.org1.example2.com:7058: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup peer1.org1.example2.com: no such host"
Usage:
peer lifecycle chaincode approveformyorg [flags]

Flags:
--channel-config-policy string The endorsement policy associated to this chaincode specified as a channel config policy reference
-C, --channelID string The channel on which this command should be executed
--collections-config string The fully qualified path to the collection JSON file including the file name
--connectionProfile string The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
-E, --endorsement-plugin string The name of the endorsement plugin to be used for this chaincode
-h, --help help for approveformyorg
--init-required Whether the chaincode requires invoking 'init'
-n, --name string Name of the chaincode
--package-id string The identifier of the chaincode install package
--peerAddresses stringArray The addresses of the peers to connect to
--sequence int The sequence number of the chaincode definition for the channel
--signature-policy string The endorsement policy associated to this chaincode specified as a signature policy
--tlsRootCertFiles stringArray If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag
-V, --validation-plugin string The name of the validation plugin to be used for this chaincode
-v, --version string Version of the chaincode
--waitForEvent Whether to wait for the event from each peer's deliver filtered service signifying that the transaction has been committed successfully (default true)
--waitForEventTimeout duration Time to wait for the event from each peer's deliver filtered service signifying that the 'invoke' transaction has been committed successfully (default 30s)

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
--connTimeout duration Timeout for client to connect (default 3s)
--keyfile string Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
-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
--tlsHandshakeTimeShift duration The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint

set +x
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
35efcbf9d8a3 nginx "/docker-entrypoint.…" 3 minutes ago Up 3 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 0.0.0.0:4010->4000/tcp, :::4010->4000/tcp www.peer.org1.example2.com
4b7bcb7d570c olegabu/fabric-tools-extended:stable "/bin/sh" 3 minutes ago Up 3 minutes cli.peer1.org1.example2.com
189a18d781fc hyperledger/fabric-peer:2.3 "sh -c 'sed -i 's/\…" 3 minutes ago Restarting (1) 15 seconds ago peer1.org1.example2.com
c8e0a9ad16d6 olegabu/fabric-starter-rest:stable "sh -c '/etc/hyperle…" 3 minutes ago Up 3 minutes 3000/tcp api.org1.example2.com
8035c1267af6 osixia/phpldapadmin "/container/tool/run…" 3 minutes ago Up 3 minutes 80/tcp, 0.0.0.0:6443->443/tcp, :::6443->443/tcp ldapadmin.org1.example2.com
7a56294411b2 hyperledger/fabric-ca:1.5 "sh -c 'sleep 2; fab…" 3 minutes ago Restarting (1) 53 seconds ago ca.org1.example2.com
b20469f65d90 nginx "/docker-entrypoint.…" 3 minutes ago Up 3 minutes 80/tcp www.org1.example2.com
841ef7030ec1 olegabu/fabric-sdk-api:stable "java -jar ./fabric2…" 3 minutes ago Up 3 minutes 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp sdk.org1.example2.com
4e952f1a88db hyperledger/fabric-ca:1.5 "sh -c 'sleep 2; fab…" 3 minutes ago Restarting (1) 54 seconds ago tlsca.org1.example2.com
8be6b1ceb87a hyperledger/fabric-couchdb "tini -- /docker-ent…" 3 minutes ago Up 3 minutes 4369/tcp, 5984/tcp, 9100/tcp couchdb.peer1.org1.example2.com
41a1d234dc94 osixia/openldap "/container/tool/run…" 3 minutes ago Up 3 minutes 389/tcp, 636/tcp ldap.org1.example2.com
91088ab7bf5c olegabu/fabric-tools-extended:stable "/bin/sh" 3 minutes ago Up 3 minutes cli.orderer.example2.com
ddc3e372f1f7 nginx "/docker-entrypoint.…" 3 minutes ago Up 3 minutes 0.0.0.0:79->80/tcp, :::79->80/tcp www.example2.com
6602f4d6cd6a hyperledger/fabric-orderer:2.3 "sh -c 'sleep 3 && o…" 3 minutes ago Up 12 seconds 7050/tcp, 0.0.0.0:7052->7052/tcp, :::7052->7052/tcp orderer.example2.com
vishesh@ubuntu:~/fabric-starter$

If anyone have any way to solve this please do help me out.
thank you

The text was updated successfully, but these errors were encountered:

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Getting error while adding another org #184

Getting error while adding another org #184

Vishesh1702 commented Oct 7, 2023

Getting error while adding another org #184

Getting error while adding another org #184

Comments

Vishesh1702 commented Oct 7, 2023

Global: &ChannelCapabilities

V1_1: true

Organizations lists the orgs participating on the application side of the

network.

Policies defines the set of policies at this level of the config tree

For Application policies, their canonical path is

/Channel/Application/

Policies: &ApplicationDefaultPolicies

LifecycleEndorsement:

Type: ImplicitMeta

Rule: "MAJORITY Endorsement"

Endorsement:

Type: ImplicitMeta

Rule: "MAJORITY Endorsement"

Readers:

Type: ImplicitMeta

Rule: "ANY Readers"

Writers:

Type: ImplicitMeta

Rule: "ANY Writers"

Admins:

Type: ImplicitMeta

Rule: "MAJORITY Admins"

Capabilities describes the application level capabilities, see the

dedicated Capabilities section elsewhere in this file for a full

description

Type: ImplicitMeta

Rule: ANY MEMBER

Type: ImplicitMeta

Rule: "MAJORITY Writers"

Type: Signature

Rule: "OutOf('1','org1.member')"

Type: ImplicitMeta

Rule: "ANY Admins"

Admins:

Type: ImplicitMeta

Rule: "MAJORITY Admins"