我正在尝试扩展this代码,以在组织org1中再添加1个支持对等体。我更新了/basic-network/crypto-config.yaml
如下:
PeerOrgs:
- Name: Org1
Domain: org1.example.com
Template:
Count: 2
Users:
Count: 1
然后我再次运行generate.sh
重新生成所有加密材料。我更新了basic-network/docker-compose.yaml
文件中的FABRIC_CA_SERVER_CA_KEYFILE。我在docker-compose.yaml中添加了peer1.org1.example.com:
peer1.org1.example.com:
container_name: peer1.org1.example.com
image: hyperledger/fabric-peer
environment:
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
- CORE_PEER_ID=peer1.org1.example.com
- CORE_LOGGING_PEER=debug
- CORE_CHAINCODE_LOGGING_LEVEL=DEBUG
- CORE_PEER_LOCALMSPID=Org1MSP
- CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
- CORE_PEER_ADDRESS=peer1.org1.example.com:7056
# # the following setting starts chaincode containers on the same
# # bridge network as the peers
# # https://docs.docker.com/compose/networking/
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_basic
- CORE_LEDGER_STATE_STATEDATABASE=CouchDB
- CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
# The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
# provide the credentials for ledger to connect to CouchDB. The username and password must
# match the username and password set for the associated CouchDB.
- CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
- CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
working_dir: /opt/gopath/src/github.com/hyperledger/fabric
command: peer node start
# command: peer node start --peer-chaincodedev=true
ports:
- 7056:7056
- 7058:7058
volumes:
- /var/run/:/host/var/run/
- ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/msp:/etc/hyperledger/msp/peer
- ./crypto-config/peerOrganizations/org1.example.com/users:/etc/hyperledger/msp/users
- ./config:/etc/hyperledger/configtx
depends_on:
- orderer.example.com
- couchdb
- peer0.org1.example.com
networks:
- basic
然后我运行了以下命令:
set -ev
export MSYS_NO_PATHCONV=1
docker-compose -f docker-compose.yml down
docker-compose -f docker-compose.yml up -d ca.example.com orderer.example.com peer0.org1.example.com peer1.org1.example.com couchdb
所有容器都启动并运行,没有任何错误。
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3393fc796417 dev-peer0.org1.example.com-tuna-app-1.0-b58eb592ed6ced10f52cc063bda0c303a4272089a3f9a99000d921f94b9bae9b "chaincode -peer.add…" 2 minutes ago Up 2 minutes dev-peer0.org1.example.com-tuna-app-1.0
a45d7e943068 hyperledger/fabric-tools "/bin/bash" 2 minutes ago Up 2 minutes cli
d3698fc6d3d3 hyperledger/fabric-peer "peer node start" 2 minutes ago Up 2 minutes 0.0.0.0:7056->7056/tcp, 0.0.0.0:7058->7058/tcp peer1.org1.example.com
b7c92a70fc89 hyperledger/fabric-peer "peer node start" 2 minutes ago Up 2 minutes 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peer0.org1.example.com
21fabe33e3e5 hyperledger/fabric-ca "sh -c 'fabric-ca-se…" 2 minutes ago Up 2 minutes 0.0.0.0:7054->7054/tcp ca.example.com
ddaf8390c0ee hyperledger/fabric-couchdb "tini -- /docker-ent…" 2 minutes ago Up 2 minutes 4369/tcp, 9100/tcp, 0.0.0.0:5984->5984/tcp couchdb
38bdb92c6de0 hyperledger/fabric-orderer "orderer" 2 minutes ago Up 2 minutes 0.0.0.0:7050->7050/tcp orderer.example.com
接下来,我需要创建两个对等的通道。如何修改以下命令以将peer1添加到org1?
# Create the channel
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/[email protected]/msp" peer0.org1.example.com peer channel create -o orderer.example.com:7050 -c mychannel -f /etc/hyperledger/configtx/channel.tx
# Join peer0.org1.example.com to the channel.
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/[email protected]/msp" peer0.org1.example.com peer channel join -b mychannel.block
以上两个命令成功运行,但是当我尝试运行以下命令时
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/[email protected]/msp" peer1.org1.example.com peer channel join -b mychannel.block
我收到以下错误:
Error: Error getting endorser client channel: endorser client failed to connect to peer1.org1.example.com:7056: failed to create new connection: context deadline exceeded
继续使用7051
和7053
作为同行的内部端口,只有暴露的端口必须更改:
ports:
- 7056:7051
- 7058:7053
我找不到任何关于此的官方文档,但似乎默认情况下它始终使用组织的主要对等方的地址。用于处理组织中对等方的传入请求的端口应与该组织的锚对等端口相同。
#Peer将侦听的本地网络接口的地址。 #默认情况下,它将侦听所有网络接口 listenAddress:0.0.0.0:7051
[...]
#用作对等配置时,表示其他对等体的端点 #在同一个组织中。对于其他组织的同行,请参阅 #gossip.externalEndpoint了解更多信息。 #用作CLI配置时,这意味着要与之交互的对等端点 地址:0.0.0.0:7051
[...]
八卦: #bootstrap设置为初始化八卦。 #这是此对等体在启动时伸出的其他对等体的列表。 #重要提示:此处的端点必须是同级端点 #organization,因为对等方拒绝连接到这些端点 #除非他们与同伴在同一个组织中。 bootstrap:127.0.0.1:7051
如果你真的想使用另一个内部端口(比如7056
),尝试在你的新对等体的docker-compose文件中定义CORE_PEER_LISTENADDRESS
(定义GRPC服务器的监听端口):
CORE_PEER_LISTENADDRESS=0.0.0.0:7056
另外,我建议你不要为所有同行使用相同的CouchDb作为分类帐数据库。每个对等方使用couchDB(建议设置用户名/密码)。
编辑:因为你没有从你的peer channel join
容器运行cli
命令,我认为你必须通过你的新同行的订货人fetch通道才能加入它(这将返回目标通道的最新配置块):
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/[email protected]/msp" peer1.org1.example.com peer channel fetch config -o orderer.example.com:7050 -c mychannel
然后,您应该能够使用新创建的块(<channelID>_config.block
)将您的对等方加入到通道中。