我正在尝试与3个组织（每个组织有3个对等方），两个订购者建立网络结构1.4.3中有Kafka和zookeeper的节点
然后，当我与...建立频道时>
docker exec cli peer channel create -o orderer0.example.com:7050 -c $CHANNEL_NAME -f $ARTIFACTS_DIR/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
以下错误发生在CLI中
Error: got unexpected status: FORBIDDEN -- implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Writers' sub-policies to be satisfied: permission denied
这是orderer0的docker日志
2019-10-12 09:01:16.513 UTC [orderer.consensus.kafka] setupChannelConsumerForChannel -> INFO 011 [channel: channel.first] Setting up the channel consumer for this channel (start offset: -2)...
2019-10-12 09:01:16.524 UTC [orderer.consensus.kafka] startThread -> INFO 012 [channel: channel.first] Channel consumer set up successfully
2019-10-12 09:01:16.543 UTC [orderer.consensus.kafka] startThread -> INFO 013 [channel: channel.first] Start phase completed successfully
2019-10-12 09:01:18.537 UTC [orderer.common.broadcast] ProcessMessage -> WARN 014 [channel: channel.first] Rejecting broadcast of config message from 172.18.0.29:35290 because of error: implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Writers' sub-policies to be satisfied: permission denied
2019-10-12 09:01:18.537 UTC [comm.grpc.server] 1 -> INFO 015 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Broadcast grpc.peer_address=172.18.0.29:35290 grpc.code=OK grpc.call_duration=1.888934ms
2019-10-12 09:01:18.541 UTC [common.deliver] Handle -> WARN 016 Error reading from 172.18.0.29:35288: rpc error: code = Canceled desc = context canceled
2019-10-12 09:01:18.542 UTC [comm.grpc.server] 1 -> INFO 017 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.18.0.29:35288 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=10.552989ms
部门
|──目录| └──────文物| | └──────channel.tx| | └──────genesis.block| || └──────bin| | └──────crypto-config| | | └──────...| | └──────...| || └──────网络| docker──────docker-compose-mq.yaml| docker──────docker-compose-orderer.yaml| └──────...
我在here中阅读了一些像我一样的解决方案，但我还没有解决。
这是我的configtx.yaml部分
机构：-＆OrdererOrg名称：OrdererOrgID：订购者MSPMSPDir：./ crypto-config / ordererOrganizations / example.com / msp政策：读者：类型：签名规则：“ OR（'OrdererMSP.member'）”作家：类型：签名规则：“ OR（'OrdererMSP.member'）”管理员：类型：签名规则：“ OR（'OrdererMSP.admin'）”-＆Org1名称：Org1MSP编号：Org1MSPMSPDir：./ crypto-config / peerOrganizations / org1.example.com / msp政策：读者：类型：签名规则：“ OR（'Org1MSP.admin'，'Org1MSP.peer'，'Org1MSP.client'）”作家：类型：签名规则：“ OR（'Org1MSP.admin'，'Org1MSP.client'）”管理员：类型：签名规则：“ OR（'Org1MSP.admin'）”锚点：-主持人：peer0.org1.example.com端口：7051这是docker-compose-cli.yaml
cli：container_name：cli图片：hyperledger / fabric-tools：1.4.3tty：是stdin_open：是环境：-SYS_CHANNEL = $ SYS_CHANNEL-GOPATH = / opt / gopath-CORE_VM_ENDPOINT = unix：///host/var/run/docker.sock＃-FABRIC_LOGGING_SPEC =调试-FABRIC_LOGGING_SPEC = INFO-CORE_PEER_ID = cli-CORE_PEER_ADDRESS = peer0.org1.example.com-CORE_PEER_LOCALMSPID = Org1MSP-CORE_PEER_TLS_ENABLED = true-CORE_PEER_TLS_CERT_FILE = / opt / gopath / src / github.com / hyperledger / fabric / peer / crypto / peerOrganizations / org1.example.com / peers / peer0.org1.example.com / tls / server.crt-CORE_PEER_TLS_KEY_FILE = / opt / gopath / src / github.com / hyperledger / fabric / peer / crypto / peerOrganizations / org1.example.com / peers / peer0.org1.example.com / tls / server.key-CORE_PEER_TLS_ROOTCERT_FILE = / opt / gopath / src / github.com / hyperledger / fabric / peer / crypto / peerOrganizations / org1.example.com / peers / peer0.org1.example.com / tls / ca.crt-CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/mspworking_dir：/opt/gopath/src/github.com/hyperledger/fabric/peer命令：/ bin / bash数量：-/ var / run /：/ host / var / run /-../chaincode/:/opt/gopath/src/github.com/chaincode-./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/-../artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts-../chaincode:/opt/gopath/src/github.com/hyperledger/fabric/chaincode＃-./:/etc/hyperledger/fabriccrypto-config.yaml
订购者单位：-名称：订购者域：example.comEnableNodeOUs：是眼镜：-主机名：订购者模板：数：2同行组织：-名称：Org1域：org1.example.comEnableNodeOUs：是模板：数：3使用者：数：1docker-compose-orderer.yaml
版本：“ 2”网络：区块链网络服务：orderer0.example.com：container_name：orderer0.example.com图片：超级账本/织物订购者：1.4.3环境：-ORDERER_GENERAL_LOGLEVEL =调试-ORDERER_GENERAL_LISTENADDRESS = 0.0.0.0-ORDERER_GENERAL_GENESISMETHOD =文件-ORDERER_GENERAL_GENESISFILE = / var / hyperledger / orderer / orderer.genesis.block-ORDERER_GENERAL_LOCALMSPID = OrdererMSP-ORDERER_GENERAL_LOCALMSPDIR = / var / hyperledger / orderer / msp-ORDERER_GENERAL_TLS_ENABLED = true-ORDERER_GENERAL_TLS_PRIVATEKEY = / var / hyperledger / orderer / tls / server.key-ORDERER_GENERAL_TLS_CERTIFICATE = / var / hyperledger / orderer / tls / server.crt-ORDERER_GENERAL_TLS_ROOTCAS = [/ var / hyperledger / orderer / tls / ca.crt]-ORDERER_KAFKA_RETRY_SHORTINTERVAL = 1s-ORDERER_KAFKA_RETRY_SHORTTOTAL = 30秒-ORDERER_KAFKA_VERBOSE = trueworking_dir：/opt/gopath/src/github.com/hyperledger/fabric命令：订购者数量：-../artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block-./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp:/var/hyperledger/orderer/msp-./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls:/var/hyperledger/orderer/tls端口：-7050：7050网络：-区块链网络＃orderer1的上行空间相同我想知道为什么会发生此错误以及如何解决它们。
我正在尝试在结构1.4.3中与3个org（每个都有3个对等方），两个带有Kafka的订购者节点和zookeeper建立网络。然后，当我与docker exec cli对等创建通道时对等创建通道-o ...
您在configtx.yaml中的频道配置是什么？
您是否尝试过在客户端bash中运行peer命令（我不确定与MSP相关的环境变量是否以使用“ docker exec”的方式处于活动状态？]