Hyperledger fabric Hyperledger结构订购者在我尝试批准链码时收到的权限被拒绝

在本教程之后，我试图通过以下方式使系统正常运行-

在我的例子中，Hyperledger结构组件在Kubernetes上运行，而我正在运行 pod中包含fabric tool:2.0的所有命令

据我所知，我成功地正确运行了所有的播客和服务。我成功了 要创建

genesis.block

，请创建网络，将对等方加入网络，在每个对等方上打包并安装链码，然后接收教程中的

mycc

键

当我尝试批准链码时，问题开始出现-

peer lifecycle chaincode approveformyorg --channelID $CHANNEL_NAME --name mycc --version 1.0 --init-required --package-id $CC_PACKAGE_ID --sequence 1

当我运行它时，我得到以下消息-

2020-04-15 18:39:04.743 IDT [cli.lifecycle.chaincode] setOrdererClient -> INFO 001 Retrieved channel (orderer-system-channel) orderer endpoint: orderer:31010
Error: timed out waiting for txid on all peers

以及订购者日志中的一些错误-（

隐式策略评估失败-满足了0个子策略，但此策略要求满足“读者”子策略中的1个子策略：权限被拒绝

）

2020-04-15 18:41:24.595 IDT[comm.grpc.server]1->INFO 2bd流媒体 调用已完成的grpc.service=order.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.17.0.14:36484 grpc.code=OK grpc.呼叫持续时间=2.180654ms 2020-04-15 18:41:34.574 IDT [common.deliver]传送块->警告2be[频道： 订购方系统通道]已撤销交付的客户端授权 来自172.17.0.15:42520的请求：隐式策略评估失败-0 满足子策略，但此策略需要 需满足的“读者”子政策：许可被拒绝2020-04-15 18:41:34.574 IDT[comm.grpc.server]1->INFO 2bf流式呼叫 已完成的grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.17.0.15:42520 grpc.code=OK grpc.呼叫持续时间=1.918542ms 2020-04-15 18:41:45.865 IDT [common.deliver]传送块->警告2c0[频道： 订购方系统通道]已撤销交付的客户端授权 来自172.17.0.16:36710的请求：隐式策略评估失败-0 满足子策略，但此策略需要 需满足的“读者”子政策：许可被拒绝2020-04-15 18:41:45.865 IDT[comm.grpc.server]1->INFO 2c1流式呼叫 已完成的grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.17.0.16:36710 grpc.code=OK 总通话时长=3.452952ms 2020-04-15 18:41:55.196 IDT [common.deliver]传送块->警告2c2[频道： 订购方系统通道]已撤销交付的客户端授权 来自172.17.0.17:53220的请求：隐式策略评估失败-0 满足子策略，但此策略需要 需满足的“读者”子政策：许可被拒绝2020-04-15 18:41:55.196 IDT[comm.grpc.server]1->INFO 2c3流式呼叫 已完成的grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.17.0.17:53220 grpc.code=OK grpc.呼叫持续时间=1.084932ms 2020-04-15 18:42:08.194 IDT [orderer.common.broadcast]句柄->警告2c4读取时出错 172.17.0.11:50106:rpc错误：代码=取消描述=上下文取消2020-04-15 18:42:08.194 IDT[comm.grpc.server]1->INFO 2c5流媒体 调用已完成的grpc.service=order.AtomicBroadcast grpc.method=广播grpc.peer_address=172.17.0.11:50106 error=“rpc 错误：code=cancelled desc=context cancelled“grpc.code=cancelled 总通话时长=30.451678366S2020-04-1518:42:22.760IDT [common.deliver]传送块->警告2c6[频道： 订购方系统通道]已撤销交付的客户端授权 来自172.17.0.18:43404的请求：隐式策略评估失败-0 满足子策略，但此策略需要 需满足的“读者”子政策：许可被拒绝2020-04-15 18:42:22.760 IDT[comm.grpc.server]1->INFO 2c7流式呼叫 已完成的grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.17.0.18:43404 grpc.code=OK grpc.呼叫持续时间=962.109µs 2020-04-15 18:42:33.165 IDT [common.deliver]传送块->警告2c8[频道： 订购方系统通道]已撤销交付的客户端授权 来自172.17.0.19:56570的请求：隐式策略评估失败-0 满足子策略，但此策略需要 要满足的“读者”子策略：权限被拒绝

Org1Peer1日志-

kubectl exec -it fabric-tools -- /bin/bash
cryptogen generate --config /fabric/config/crypto-config.yaml &&
cp -r crypto-config /fabric/ &&
for file in $(find /fabric/ -iname *_sk); do echo $file; dir=$(dirname $file); mv ${dir}/*_sk ${dir}/key.pem; done &&
cp /fabric/config/configtx.yaml /fabric/ &&
cd /fabric &&
configtxgen -profile FourOrgsOrdererGenesis -outputBlock genesis.block -channelID kafka-orderer-channel &&
configtxgen -profile FourOrgsChannel -outputCreateChannelTx orderer-system-channel.tx -channelID orderer-system-channel &&
configtxgen -profile FourOrgsChannel -outputAnchorPeersUpdate ./Org1MSPanchors.tx -channelID orderer-system-channel -asOrg Org1MSP &&
configtxgen -profile FourOrgsChannel -outputAnchorPeersUpdate ./Org2MSPanchors.tx -channelID orderer-system-channel -asOrg Org2MSP &&
configtxgen -profile FourOrgsChannel -outputAnchorPeersUpdate ./Org3MSPanchors.tx -channelID orderer-system-channel -asOrg Org3MSP &&
cd .. &&
chmod a+rx /fabric/* -R 

2020-04-18 14:01:44.999 IDT[peer]getLocalAddress->INFO 003 自动检测到的对等地址：172.17.0.14:30110 2020-04-18 14:01:44.999 设置IDT[peer]getLocalAddress->INFO 004自动检测标志， 返回172.17.0.14:30110 2020-04-18 14:01:45.194 IDT [gossip.service]新建->信息005使用端点初始化gossip org1peer1 svc:30110 2020-04-18 14:01:45.194 IDT[gossip.gossip]新-> 信息006正在创建具有端点自身成员身份的八卦服务： org1peer1 svc:30110，内部端点：org1peer1 svc:30110，PKI-ID: 51b25e96fadae28a11006feffffc06ff47d1cb25bef7c82a04c36c4ddb20e9f9， 元数据：2020-04-1814:01:45.195IDT[gossip.gossip]开始->信息 007八卦实例org1peer1 svc:30110于2020年4月18日启动 14:01:45.196 IDT[ledgermgmt]NewLedgerMgr->INFO 008正在初始化 LedgerMgr 2020-04-18 14:01:45.478 IDT[leveldbhelper] openDBAndCheckFormat->INFO 009 DB为空，将DB格式设置为2.0 2020-04-18 14:01:45.503 IDT[fsblkstorage]新提供者->信息00a 正在创建新的文件分类帐目录 /var/超级分类账/生产/分类账数据/链/链2020-04-18 14:01:45.647 IDT[leveldbhelper]openDBAndCheckFormat->INFO 00b DB 设置db格式为2.0 2020-04-18 14:01:45.888 IDT时为空 [couchdb]HandlerRequest->WARN 00c在125ms内重试couchdb请求。 尝试：1错误：获取：拨号tcp[：：1]：5984: 连接：无法分配请求的地址2020-04-18 14:01:46.017 IDT [couchdb]HandlerRequest->WARN 00d在250ms内重试couchdb请求。 尝试：2错误：获取：拨号tcp[：：1]：5984: 连接：无法分配请求的地址2020-04

cd /fabric &&
export CHANNEL_NAME="orderer-system-channel" &&
export ORDERER_URL="orderer:31010" &&
export CORE_PEER_ADDRESSAUTODETECT="false" &&
export CORE_PEER_NETWORKID="nid1" &&
export CORE_PEER_LOCALMSPID="Org1MSP" &&
export CORE_PEER_ADDRESS="org1peer1-svc:30110" &&
export CORE_PEER_MSPCONFIGPATH="/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" &&
export FABRIC_CFG_PATH="/etc/hyperledger/fabric" &&
peer channel create -o ${ORDERER_URL} -c ${CHANNEL_NAME} -f /fabric/${CHANNEL_NAME}.tx &&
chmod a+rx /fabric/* -R 

export CHANNEL_NAME="orderer-system-channel" &&
export CORE_PEER_NETWORKID="nid1" &&
export ORDERER_URL="orderer:31010" &&
export FABRIC_CFG_PATH="/etc/hyperledger/fabric" &&
export CORE_PEER_LOCALMSPID="Org1MSP" &&
export CORE_PEER_MSPID="Org1MSP" &&
export CORE_PEER_MSPCONFIGPATH="/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" &&
export CORE_PEER_ADDRESS="org1peer1-svc:30110" &&
peer channel fetch newest -o ${ORDERER_URL} -c ${CHANNEL_NAME} &&
chmod a+rx /fabric/* -R &&
peer channel join -b ${CHANNEL_NAME}_newest.block &&
sleep 5 &&
export CORE_PEER_ADDRESS="org1peer2-svc:30110" &&
peer channel fetch newest -o ${ORDERER_URL} -c ${CHANNEL_NAME} &&
peer channel join -b ${CHANNEL_NAME}_newest.block 

cp -r /fabric/config/chaincode $GOPATH/src/ &&
cd /go/src/chaincode &&
GO111MODULE=on go mod vendor &&
cd /fabric &&
chmod a+rx /go/* -R &&
peer lifecycle chaincode package mycc.tar.gz --path /go/src/chaincode/ --lang golang --label mycc_1 &&
chmod a+rx /fabric/* -R 

export CHAINCODE_VERSION="1.0" &&
export FABRIC_CFG_PATH="/etc/hyperledger/fabric" &&
export CORE_PEER_MSPCONFIGPATH="/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" &&
export CORE_PEER_LOCALMSPID="Org1MSP" &&
export CORE_PEER_ADDRESS="org1peer1-svc:30110" &&
peer lifecycle chaincode install mycc.tar.gz &&
peer lifecycle chaincode queryinstalled &&
export CORE_PEER_ADDRESS="org1peer2-svc:30110" &&
peer lifecycle chaincode install mycc.tar.gz &&
peer lifecycle chaincode queryinstalled 

export CHANNEL_NAME="orderer-system-channel" &&
export CORE_PEER_NETWORKID="nid1" &&
export ORDERER_URL="orderer:31010" &&
export FABRIC_CFG_PATH="/etc/hyperledger/fabric"

export CC_PACKAGE_ID=mycc_1:265208bde42d32cc07779c963ccfa379439f1ac64a813bf701e5309ff08bae13 &&
export CORE_PEER_LOCALMSPID="Org1MSP" &&
export CORE_PEER_MSPID="Org1MSP" &&
export CORE_PEER_MSPCONFIGPATH="/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" &&
export CORE_PEER_ADDRESS="org1peer1-svc:30110"

peer lifecycle chaincode approveformyorg --channelID $CHANNEL_NAME --name mycc --version 1.0 --init-required --package-id $CC_PACKAGE_ID --sequence 1

- &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.admin')"
        Endorsement:
            Type: Signature
            Rule: "OR('Org1MSP.member')"

    AnchorPeers:
        - Host: peer0.org1.example.com
          Port: 7051

- &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.admin')"
        Endorsement:
            Type: Signature
            Rule: "OR('Org2MSP.member')"

    AnchorPeers:
        - Host: peer0.org2.example.com
          Port: 9051

2020-04-18 14:06:34.915 IDT [peer.blocksprovider] DeliverBlocks -> WARN 047 Got error while attempting to receive blocks: received bad status FORBIDDEN from orderer channel=orderer-system-channel orderer-address=orderer:31010 

2020-04-18 14:06:35.276 IDT [peer.blocksprovider] func1 -> WARN 048 Encountered an error reading from deliver stream: EOF channel=orderer-system-channel orderer-address=orderer:31010 

2020-04-18 14:06:35.276 IDT [peer.blocksprovider] DeliverBlocks -> WARN 049 Got error while attempting to receive blocks: received bad status FORBIDDEN from orderer channel=orderer-system-channel orderer-address=orderer:31010 

2020-04-18 14:06:35.708 IDT [peer.blocksprovider] func1 -> WARN 04a Encountered an error reading from deliver stream: EOF channel=orderer-system-channel orderer-address=orderer:31010 

2020-04-18 14:06:35.708 IDT [peer.blocksprovider] DeliverBlocks -> WARN 04b Got error while attempting to receive blocks: received bad status FORBIDDEN from orderer channel=orderer-system-channel orderer-address=orderer:31010 

2020-04-18 14:06:36.228 IDT [peer.blocksprovider] func1 -> WARN 04c Encountered an error reading from deliver stream: EOF channel=orderer-system-channel orderer-address=orderer:31010

2020-04-18 14:06:36.228 IDT [peer.blocksprovider] DeliverBlocks -> WARN 04d Got error while attempting to receive blocks: received bad status FORBIDDEN from orderer channel=orderer-system-channel orderer-address=orderer:31010 

2020-04-18 14:06:36.881 IDT [peer.blocksprovider] func1 -> WARN 04e Encountered an error reading from deliver stream: EOF channel=orderer-system-channel orderer-address=orderer:31010