Hyperledger fabric Can';t连接AWS上不同机器上的订购者和对等节点
我正在尝试用一个订购者和3个组织构建一个网络,每个组织在Hyperledger结构版本2的AWS上都有一个对等节点。我可以通过以下命令使用configtxgen成功生成订购方和渠道配置事务的genesis块:Hyperledger fabric Can';t连接AWS上不同机器上的订购者和对等节点,hyperledger-fabric,hyperledger,Hyperledger Fabric,Hyperledger,我正在尝试用一个订购者和3个组织构建一个网络,每个组织在Hyperledger结构版本2的AWS上都有一个对等节点。我可以通过以下命令使用configtxgen成功生成订购方和渠道配置事务的genesis块: configtxgen-profile threeorgansorderergenesis-channelID orderchannel-outputBlock./config/genesis.block configtxgen-profile ChannelAll-outputCreat
configtxgen-profile threeorgansorderergenesis-channelID orderchannel-outputBlock./config/genesis.block
configtxgen-profile ChannelAll-outputCreateChannelTx./config/channel.tx-channelID ChannelAll
这是我的configtx.yaml文件:(这里的策略不是一个好的实践,只是试验)
---
组织:
-&orderorg
姓名:OrderOrg
ID:ordermsp
MSPDir:./crypto-config/orderOrganizations/example.com/msp
政策:
读者:
类型:签名
规则:“或('ordermsp.member')”
作者:
类型:签名
规则:“或('ordermsp.member')”
管理员:
类型:签名
规则:“或('ordermsp.member')”
-&Org1
名称:Org1MSP
ID:Org1MSP
MSPDir:./crypto-config/peerOrganizations/org1.example.com/msp
政策:
读者:
类型:签名
规则:“或('Org1MSP.member')”
作者:
类型:签名
规则:“或('Org1MSP.member')”
管理员:
类型:签名
规则:“或('Org1MSP.member')”
背书:
类型:签名
规则:“或('Org1MSP.member')”
-&Org2
名称:Org2MSP
ID:Org2MSP
MSPDir:./crypto-config/peerOrganizations/org2.example.com/msp
政策:
读者:
类型:签名
规则:“或('Org2MSP.member')”
作者:
类型:签名
规则:“或('Org2MSP.member')”
管理员:
类型:签名
规则:“或('Org2MSP.member')”
背书:
类型:签名
规则:“或('Org2MSP.member')”
-&Org3
名称:Org3MSP
ID:Org3MSP
MSPDir:./crypto-config/peerOrganizations/org3.example.com/msp
政策:
读者:
类型:签名
规则:“或('Org3MSP.member')”
作者:
类型:签名
规则:“或('Org3MSP.member')”
管理员:
类型:签名
规则:“或('Org3MSP.member')”
背书:
类型:签名
规则:“或('Org3MSP.member')”
能力:
通道:&通道功能
V1_3:正确
订购者:&订购者能力
V1_1:正确
应用程序:&应用程序容量
V2_0:正确
V1_3:错误
V1_2:错误
V1_1:错误
应用程序:&ApplicationDefaults
组织:
政策:
读者:
类型:ImplicitMeta
规则:“任何读者”
作者:
类型:ImplicitMeta
规则:“任何作家”
管理员:
类型:ImplicitMeta
规则:“多数管理员”
生命周期声明:
类型:ImplicitMeta
规则:“多数赞成”
背书:
类型:ImplicitMeta
规则:“多数赞成”
能力:
我注意到你用了
configtxgen-profile oneorgordergenesis
而在配置文件部分的configtx.yaml
中是threeorganises
也许您应该尝试使用以下命令生成加密文件:
configtxgen-profile threeorgansorderergenesis-channelID orderchannel-outputBlock./config/genesis.block
configtxgen-profile ChannelAll-outputCreateChannelTx./config/channel.tx-channelID ChannelAll
您在was上使用docker swarm吗?我没有,我在docker compose文件中使用额外的\u主机。例如:peer0.org1.example.com:extra_hosts:-“order.example.com:172.31.95.122”-“peer0.org2.example.com:172.31.20.132”-“peer0.org3.example.com:172.31.22.56”试图ping您的容器,是否可以访问?是的,我用nmap检查了特定端口,它说您从本地或aws实例使用了opennmap?抱歉,这是一个复制粘贴错误。我正在运行正确的命令。尽管收到了警告,我还是成功地运行了我的网络。这可能是因为我的其他同龄人当时还没有加入网络,所以说闲话是不正常的。
---
Organizations:
- &OrdererOrg
Name: OrdererOrg
ID: OrdererMSP
MSPDir: ./crypto-config/ordererOrganizations/example.com/msp
Policies:
Readers:
Type: Signature
Rule: "OR('OrdererMSP.member')"
Writers:
Type: Signature
Rule: "OR('OrdererMSP.member')"
Admins:
Type: Signature
Rule: "OR('OrdererMSP.member')"
- &Org1
Name: Org1MSP
ID: Org1MSP
MSPDir: ./crypto-config/peerOrganizations/org1.example.com/msp
Policies:
Readers:
Type: Signature
Rule: "OR('Org1MSP.member')"
Writers:
Type: Signature
Rule: "OR('Org1MSP.member')"
Admins:
Type: Signature
Rule: "OR('Org1MSP.member')"
Endorsement:
Type: Signature
Rule: "OR('Org1MSP.member')"
- &Org2
Name: Org2MSP
ID: Org2MSP
MSPDir: ./crypto-config/peerOrganizations/org2.example.com/msp
Policies:
Readers:
Type: Signature
Rule: "OR('Org2MSP.member')"
Writers:
Type: Signature
Rule: "OR('Org2MSP.member')"
Admins:
Type: Signature
Rule: "OR('Org2MSP.member')"
Endorsement:
Type: Signature
Rule: "OR('Org2MSP.member')"
- &Org3
Name: Org3MSP
ID: Org3MSP
MSPDir: ./crypto-config/peerOrganizations/org3.example.com/msp
Policies:
Readers:
Type: Signature
Rule: "OR('Org3MSP.member')"
Writers:
Type: Signature
Rule: "OR('Org3MSP.member')"
Admins:
Type: Signature
Rule: "OR('Org3MSP.member')"
Endorsement:
Type: Signature
Rule: "OR('Org3MSP.member')"
Capabilities:
Channel: &ChannelCapabilities
V1_3: true
Orderer: &OrdererCapabilities
V1_1: true
Application: &ApplicationCapabilities
V2_0: true
V1_3: false
V1_2: false
V1_1: false
Application: &ApplicationDefaults
Organizations:
Policies:
Readers:
Type: ImplicitMeta
Rule: "ANY Readers"
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
Admins:
Type: ImplicitMeta
Rule: "MAJORITY Admins"
LifecycleEndorsement:
Type: ImplicitMeta
Rule: "MAJORITY Endorsement"
Endorsement:
Type: ImplicitMeta
Rule: "MAJORITY Endorsement"
Capabilities:
<<: *ApplicationCapabilities
Orderer: &OrdererDefaults
OrdererType: solo
Addresses:
- orderer.example.com:7050
BatchTimeout: 2s
BatchSize:
MaxMessageCount: 300
AbsoluteMaxBytes: 99 MB
PreferredMaxBytes: 512 KB
Kafka:
Brokers:
- 127.0.0.1:9092
Organizations:
Policies:
Readers:
Type: ImplicitMeta
Rule: "ANY Readers"
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
Admins:
Type: ImplicitMeta
Rule: "MAJORITY Admins"
BlockValidation:
Type: ImplicitMeta
Rule: "ANY Writers"
Channel: &ChannelDefaults
Policies:
Readers:
Type: ImplicitMeta
Rule: "ANY Readers"
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
Admins:
Type: ImplicitMeta
Rule: "MAJORITY Admins"
Capabilities:
<<: *ChannelCapabilities
Profiles:
ThreeOrgsOrdererGenesis:
<<: *ChannelDefaults
Orderer:
<<: *OrdererDefaults
Organizations:
- *OrdererOrg
Capabilities:
<<: *OrdererCapabilities
Consortiums:
SampleConsortium:
Organizations:
- *Org1
- *Org2
- *Org3
ChannelAll:
Consortium: SampleConsortium
<<: *ChannelDefaults
Application:
<<: *ApplicationDefaults
Organizations:
- *Org1
- *Org2
- *Org3
Capabilities:
<<: *ApplicationCapabilities