当我尝试批准链码时，Hyperledger Fabric Orderer 收到权限被拒绝

Question

当我尝试批准链码时，Hyperledger Fabric Orderer 收到权限被拒绝

我正在尝试通过遵循本教程来使系统正常运行 -

https://hyperledger-fabric.readthedocs.io/en/release-2.0/build_network.html

在我的情况下，Hyperledger Fabric 组件在 Kubernetes 上运行，而我正在从包含 fabric-tool:2.0 的 pod 中运行所有命令。

据我了解，我成功地正确运行了所有 pod 和服务。我成功地创建了genesis.block，创建了网络，将节点加入网络，在每个节点上打包并安装了链码，并mycc像教程中一样收到了密钥。

当我尝试批准链码时，问题就开始了 -

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

Run Code Online (Sandbox Code Playgroud)

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

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

Run Code Online (Sandbox Code Playgroud)

订购者日志中还有一些错误 - ( implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Readers' sub-policies to be satisfied: permission denied)

2020-04-15 18:41:24.595 IDT [comm.grpc.server] 1 -> INFO 2bd 流媒体调用完成 grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.17.0.14:36484 grpc =OK grpc.call_duration=2.180654ms 2020-04-15 18:41:34.574 IDT [common.deliver] deliveryBlocks -> WARN 2be [channel: orderer-system-channel] 客户授权被撤销，因为来自 172.17.0.105:42 的交付请求：隐式策略评估失败 - 满足 0 个子策略，但此策略需要满足“读者”子策略中的 1 个：权限被拒绝 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.call_duration=1.918542ms 2020-04-15:45.18. IDT [常见。交付]deliverBlocks -> WARN 2c0 [channel: orderer-system-channel] 客户授权因来自 172.17.0.16:36710 的交付请求而被撤销：隐式策略评估失败 - 满足 0 个子策略，但此策略需要 1 个“读者” ' 要满足的子策略：permission denied 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 grpc.call_duration=3.452952ms 2020-04-15 18:41:55.196 IDT [common.deliver] deliveryBlocks -> WARN 2c2 [channel] orderer authorization-system撤销来自 172.17.0.17:53220 的交付请求：隐式策略评估失败 - 满足 0 个子策略，但此策略需要 '读者要满足的子策略：permission denied 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.call_duration=1.084932ms 2020-04-15 18:42:08.194 IDT [orderer.common.broadcast] 处理 -> WARN 2.170216 读取错误：rpc 错误：代码 = Canceled desc = 上下文取消 2020-04-15 18:42:08.194 IDT [comm.grpc.server] 1 -> INFO 2c5 流调用完成 grpc.service=orderer.AtomicBroadcast grpc.method=Broadcast grpc .peer_address=172.17.0.11:50106 error="rpc error: code = Canceled desc = context cancelled" grpc.code=Canceled grpc.call_duration=30.451678366s 2020-04-15 18:42:22.760 IDT交付[common.deliver] ->WARN 2c6 [channel: orderer-system-channel] 客户授权因来自 172.17.0.18:43404 的交付请求而被撤销：隐式策略评估失败 - 满足 0 个子策略，但此策略需要“读者”子策略中的 1 个才能满足：permission denied 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.call_duration=962.109µs 2020-04-15 18:42:33.165 IDT [common.deliver] deliveryBlocks -> WARN 2c8 [channel: orderer-system-channel] 客户授权被撤销，因为来自172.17.0.19:56570：隐式策略评估失败 - 满足 0 个子策略，但此策略需要 1 个“读者”要满足的子策略：许可被拒绝

Org1Peer1 日志 -

478 IDT [leveldbhelper] openDBAndCheckFormat -> INFO 009 DB is empty Setting db format as 2.0 2020-04-18 14:01:45.503 IDT [fsblkstorage] NewProvider -> INFO 00a 在 /var/production/hyperledger/ 创建新的文件分类帐目录ledgersData/chains/chains 2020-04-18 14:01:45.647 IDT [leveldbhelper] openDBAndCheckFormat -> INFO 00b DB is empty 将 db 格式设置为 2.0 2020-04-18 14:01:45.888 IDT [couchDBRequest] 00c 在 125 毫秒内重试 couchdb 请求。尝试：1 错误：获取 INFO 00b DB is empty Setting db format as 2.0 2020-04-18 14:01:45.888 IDT [couchdb] handleRequest -> WARN 00c Retrying couchdb request in 125ms. 尝试：1 错误：获取 INFO 00b DB is empty Setting db format as 2.0 2020-04-18 14:01:45.888 IDT [couchdb] handleRequest -> WARN 00c Retrying couchdb request in 125ms. 尝试：1 错误：获取http://localhost:5984/ : dial tcp [::1]:5984: connect: 无法分配请求的地址 2020-04-18 14:01:46.017 IDT [couchdb] handleRequest -> WARN 00d 在 250 毫秒内重试 couchdb 请求。尝试：2 错误：获取http://localhost:5984/：拨号 tcp [::1]:5984：连接：无法分配请求的地址 2020-04-18 14:01:46.329 IDT [couchdb] handleRequest -> WARN 00e在 500 毫秒内重试 couchdb 请求。尝试：3 错误：获取http://localhost:5984/：拨号 tcp 127.0.0.1:5984：连接：连接被拒绝 2020-04-18 14:01:46.830 IDT [couchdb] handleRequest -> WARN 00f Retrying couchdb request in 1 秒。尝试：4 错误：获取http://localhost:5984/: dial tcp [::1]:5984: connect: 无法分配请求的地址 2020-04-18 14:01:47.952 IDT [couchdb] handleRequest -> WARN 010 在 2 秒内重试 couchdb 请求。尝试：5 错误：获取http://localhost:5984/：拨号 tcp 127.0.0.1:5984：连接：连接被拒绝 2020-04-18 14:01:49.954 IDT [couchdb] handleRequest -> WARN 011 Retrying couchdb request in 4 秒。尝试：6 错误：获取http://localhost:5984/：拨号 tcp 127.0.0.1:5984：连接：连接被拒绝 2020-04-18 14:01:53.955 IDT [couchdb] handleRequest -> WARN 012 Retrying couchdb request in 8 秒。尝试：7 错误：获取 http://localhost:5984/：拨号 tcp 127.0.0.1:5984：连接：连接被拒绝 2020-04-18 14:02:01.956 IDT [couchdb] handleRequest -> WARN 013 在 16 秒内重试 couchdb 请求。尝试：8 错误：获取 http://localhost:5984/：拨号 tcp 127.0.0.1:5984：连接：连接被拒绝 2020-04-18 14:02:23.678 IDT [couchdb] CreateDatabaseIfNotExist -> INFO 014 创建状态数据库 _users 2020-04-18:24.613.678 IDTbouch] CreateDatabaseIfNotExist -> INFO 015 创建状态数据库 _replicator 2020-04-18 14:02:26.355 IDT [couchdb] CreateDatabaseIfNotExist -> INFO 016 创建状态数据库 fabric__internal 2020-04-18 14.939-18 14:02:26.355 IDT [couchdb] 017 初始化 LedgerMgr 2020-04-18 14:02:26.940 IDT [lifecycle] InitializeLocalChaincodes -> INFO 018 初始化生命周期缓存，已经安装了 0 个链码 2020-04-18 14:02:26.940 IDT100D INFO-INFO-INFO具有 peerHostname 的 computeChaincodeEndpoint: 172.17.0.14 2020-04-18 14:02:26.940 IDT [nodeCmd] computeChaincodeEndpoint ->INFO 01a Exit with ccEndpoint: 172.17.0.14:7052 2020-04-18 14:02:26.940 IDT [nodeCmd] createChaincodeServer -> WARN 01b peer.chaincodeListenAddress 未设置，使用 172.17.0.14:7052 2020-04-18 14:02:26.940 02:26.944 IDT [sccapi] DeploySysCC -> INFO 01c 部署系统链码 'lscc' 2020-04-18 14:02:26.944 IDT [sccapi] DeploySysCC -> INFO 01d 部署系统链码 'cscc'-04-4020 02:26.945 IDT [sccapi] DeploySysCC -> INFO 01e 部署系统链码 'qscc' 2020-04-18 14:02:26.945 IDT [sccapi] DeploySysCC -> INFO 01f 部署系统链码'944 IDT [sccapi] DeploySysCC -> INFO 01c 部署系统链代码 'lscc' 2020-04-18 14:02:26.944 IDT [sccapi] DeploySysCC -> INFO 01d 部署系统链代码 'cscc' 2020-04-18:14:028 26.945 IDT [sccapi] DeploySysCC -> INFO 01e 部署系统链码 'qscc' 2020-04-18 14:02:26.945 IDT [sccapi] DeploySysCC -> INFO 01f 部署系统链码'944 IDT [sccapi] DeploySysCC -> INFO 01c 部署系统链代码 'lscc' 2020-04-18 14:02:26.944 IDT [sccapi] DeploySysCC -> INFO 01d 部署系统链代码 'cscc' 2020-04-18:14:028 26.945 IDT [sccapi] DeploySysCC -> INFO 01e 部署系统链码 'qscc' 2020-04-18 14:02:26.945 IDT [sccapi] DeploySysCC -> INFO 01f 部署系统链码'生命周期' 2020-04-18 14:02:26.945 IDT [nodeCmd] serve -> INFO 020 已部署的系统链码 2020-04-18 14:02:26.945 IDT [discovery] NewService -> INFO 021：使用配置 TLS 创建authCacheMaxSize: 1000, authCachePurgeRatio: 0.750000 2020-04-18 14:02:26.945 IDT [nodeCmd] registerDiscoveryService -> INFO 022 发现服务已激活 2020-04-18: 124.394 INFO 2020-04-18: 124.394-18: 124.394-18] with ID=[org1peer1-svc], network ID=[nid1], address=[172.17.0.14:30110] 2020-04-18 14:02:26.945 IDT [nodeCmd] serve -> INFO 024 Started peer with ID=[ org1peer1-svc]，网络 ID=[nid1]，地址=[172.17.0.14:30110] 2020-04-18 14:02:26.945 IDT [nodeCmd] func6 -> INFO 025 使用 listenAddress0.0:0 启动分析服务器。 6060 2020-04-18 14:02:26.945 IDT [kvledger] LoadPreResetHeight ->INFO 026 从路径加载预设高度 [/var/hyperledger/production/ledgersData/chains] 2020-04-18 14:02:26.945 IDT [fsblkstorage] preResetHtFiles -> INFO 027 没有活动通道通过 2020-04-16 :23.402 IDT [ledgermgmt] CreateLedger -> INFO 028 使用创世区块创建账本 [orderer-system-channel] 2020-04-18 14:06:23.450 IDT [fsblkstorage] newBlockfileMgr -> INFO 029 从区块存储中获取区块信息04-18 14:06:24.348 IDT [couchdb] CreateDatabaseIfNotExist -> INFO 02a 创建状态数据库 orderer-system-channelINFO 028 使用创世区块创建账本 [orderer-system-channel] 2020-04-18 14:06:23.450 IDT [fsblkstorage] newBlockfileMgr -> INFO 029 从区块存储中获取区块信息 2020-04-18 14:06:24.34.34. [couchdb] CreateDatabaseIfNotExist -> INFO 02a 创建状态数据库 orderer-system-channelINFO 028 使用创世区块创建账本 [orderer-system-channel] 2020-04-18 14:06:23.450 IDT [fsblkstorage] newBlockfileMgr -> INFO 029 从区块存储中获取区块信息 2020-04-18 14:06:24.34.34. [couchdb] CreateDatabaseIfNotExist -> INFO 02a 创建状态数据库 orderer-system-channel2020-04-18 14:06:25.986 IDT [couchdb] CreateDatabaseIfNotExist -> INFO 02b 创建状态数据库 orderer-system-channel__lifecycle 2020-04-18 14:06:27.177 IDT [kvledger] INorderFOLegacy-> CommitLegacy-> -channel] 在 1153 毫秒内提交了 1 个事务的块 [0]（state_validation=0ms block_and_pvtdata_commit=100ms state_commit=1026ms）commitHash=[] 2020-04-18 14:06:27.210 IDT [ledgermgmt> -FOL]使用创世区块创建账本 [orderer-system-channel] 2020-04-18 14:06:27.587 IDT [gossip.gossip] JoinChan -> INFO 02e 加入 3 个组织的通道 orderer-system-channel 的八卦网络 2020-04- 18 14:06:27.587 IDT [gossip.gossip] learnAnchorPeers -> INFO 02f 没有为通道 orderer-system-channel 配置 Org2MSP 的锚点节点以了解 2020-04-18 14:06:27。587 IDT [gossip.gossip] learnAnchorPeers -> INFO 030 没有为通道 orderer-system-channel 配置 Org3MSP 的锚点节点来了解 2020-04-18 14:06:27.587 IDT [gossip.gossip] learnAnchorPeers -> No INFO031为通道 orderer-system-channel 配置 Org1MSP 的锚点节点以了解 2020-04-18 14:06:27.590 IDT [gossip.state] NewGossipStateProvider -> INFO 032 更新通道 orderer-system-channel 的元数据信息，当前分类帐序列在 = 0，下一个预期块是 = 1 2020-04-18 14:06:27.590 IDT [endorser] callChaincode -> INFO 033 完成链码：cscc 持续时间：4192ms channel= txID=22d5a6a6 2020-14:06 :27.590 IDT [comm.grpc.server] 1 -> INFO 034 一元调用完成 grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.17.0.11:60502 grpc。代码= OK grpc.call_duration = 4.200507752s 2020年4月18日14：06：33.591 IDT [gossip.election] beLeader - > INFO 035 51b25e96fadae28a11006feffffc06ff47d1cb25bef7c82a04c36c4ddb20e9f9：成为领导者2020年4月18日14：06：33.591 IDT [gossip.service ] func1 -> INFO 036 Elected as a leader, starting delivery service for channel orderer-system-channel 2020-04-18 14:06:33.591 IDT [deliveryClient] StartDeliverForChannel -> INFO 037 This peer will retrieve blocks from ordering service and disseminate到组织中的其他对等方以获取通道 orderer-system-channel 2020-04-18 14:06:33.596 IDT [peer.blocksprovider] func1 -> WARN 038 从交付流中读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:33.596 IDT [peer.blocksprovider] DeliverBlocks ->WARN 039 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 收到错误状态 FORBIDDEN:31010 2020-04-18 14:06:34.915 IDT [peer.blocksprovider] DeliverBlocks -> WARN 047 尝试接收块时出错：从 orderer 通道收到错误状态 FORBIDDEN=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:35.276 IDT [peer.blocksprovider] func1 -> WARN 048从交付流中读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:35.276 IDT [peer.blocksprovider] DeliverBlocks -> WARN 049 尝试接收时出错块：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:35 收到错误状态 FORBIDDEN。708 IDT [peer.blocksprovider] func1 -> WARN 04a 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:35.708 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 04b 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:36.228 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 04c 遇到从交付流读取错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:36.228 IDT [peer.blocksprovider] DeliverBlocks -> WARN 04d Got尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:36 接收到错误状态 FORBIDDEN。881 IDT [peer.blocksprovider] func1 -> WARN 04e 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:36.882 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 04f 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:37.627 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 050 遇到从交付流读取错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:37.627 IDT [peer.blocksprovider] DeliverBlocks -> WARN 051 Got尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:44 接收到错误状态 FORBIDDEN。281 IDT [peer.blocksprovider] func1 -> WARN 05a 从传送流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:44.281 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 05b 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:46.501 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 05c 遇到从交付流读取错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:46.501 IDT [peer.blocksprovider] DeliverBlocks -> WARN 05d Got尝试接收块时出错：从 orderer 通道收到错误状态 FORBIDDEN=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:56。200 IDT [peer.blocksprovider] func1 -> WARN 062 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:06:56.200 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 063 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:00.802 IDT [peer.blocksprovider] 收到错误状态禁止DeliverBlocks -> WARN 065 在尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:00.802 IDT [peer.blocksprovider] func1 接收到错误状态 FORBIDDEN -> WARN 064 从传送流中读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:06。324 IDT [peer.blocksprovider] func1 -> WARN 066 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:06.324 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 067 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:12.954 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 068 从传送流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:12.954 IDT [peer.blocksprovider] DeliverBlocks -> WARN 069 Got尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:20 接收到错误状态 FORBIDDEN。906 IDT [peer.blocksprovider] func1 -> WARN 06a 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:20.906 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 06b 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:30.449 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 06c 遇到从交付流读取错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:30.449 IDT [peer.blocksprovider] DeliverBlocks -> WARN 06d Got尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:41 接收到错误状态 FORBIDDEN。899 IDT [peer.blocksprovider] func1 -> WARN 06e 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:41.899 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 06f 在尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:55.641 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 070 从交付流中读取错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:07:55.641 IDT [peer.blocksprovider] DeliverBlocks -> WARN 071 Got尝试接收块时出错：从 orderer 通道收到错误状态 FORBIDDEN=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:08:12。129 IDT [peer.blocksprovider] func1 -> WARN 072 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:08:12.129 IDT [peer.blocksprovider ] DeliverBlocks -> WARN 073 尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:08:31.916 IDT [peer.blocksprovider] 收到错误状态禁止func1 -> WARN 074 遇到从交付流读取错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:08:31.916 IDT [peer.blocksprovider] DeliverBlocks -> WARN 075 Got尝试接收块时出错：从 orderer channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:08:55 接收到错误状态 FORBIDDEN。657 IDT [peer.blocksprovider] func1 -> WARN 076 从交付流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:09:28.078 IDT [lifecycle] InstallChaincode - > INFO 07A成功安装包ID 'mycc_1：265208bde42d32cc07779c963ccfa379439f1ac64a813bf701e5309ff08bae13' chaincode 2020年4月18日14：09：28.078 IDT [背书] callChaincode - > INFO 07B成品chaincode：_lifecycle持续时间：702ms信道= TxID添加= 6cf67d2f 2020-04- 18 14:09:28.078 IDT [comm.grpc.server] 1 -> INFO 07c 一元调用完成 grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.17.0.11:34596 grpc.code=OK grpc. call_duration=724.175701ms 2020-04-18 14:09:28.551 IDT [endorser] callChaincode -> INFO 07d 完成链码：_lifecycle 持续时间：0ms channel= txID=f5998634 2020-04-18 14:09:28.551 IDT [comm.grpc.server] 1 -> INFO 07e 一元调用完成 grpc.service=protos.Endorser grpc.method=ProcessProposal grpc. =172.17.0.11:34628 grpc.code=OK grpc.call_duration=1.714696ms 2020-04-18 14:09:58.337 IDT [peer.blocksprovider] func1 -> WARN 07f 遇到：从传送流读取的错误通道= Eorder -system-channel orderer-address=orderer:31010 2020-04-18 14:09:58.337 IDT [peer.blocksprovider] DeliverBlocks -> WARN 080 在尝试接收块时出错：从 orderer channel=orderer 收到错误状态 FORBIDDEN system-channel orderer-address=orderer:31010 2020-04-18 14:10:39.363 IDT [peer.blocksprovider] func1 -> WARN 081 从传送流读取时遇到错误：EOF channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:10:39.363 IDT [peer.blocksprovider] DeliverBlocks -> WARN 082 尝试接收块时出错：收到来自 orderer 的错误状态 FORBIDDEN channel=orderer-system-channel orderer-address=orderer:31010 2020-04-18 14:10:49.169 IDT [endorser] callChaincode -> INFO 083 完成链码：cscc 持续时间：0ms channel= txID=e48c516f 20180- 14:10:49.169 IDT [comm.grpc.server] 1 -> INFO 084 一元调用完成 grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.17.0.11:35566 grpc.code=OK grpc.call_d =1.250385ms 2020-04-18 14:10:51.147 IDT [couchdb] CreateDatabaseIfNotExist -> INFO 085 创建状态数据库 orderer-system-channel_lscc 2020-04-18 14:10:52。347 IDT [couchdb] CreateDatabaseIfNotExist -> INFO 086 创建状态数据库 orderer-system-channel__lifecycle$$p_implicit_org_$org1$m$s$p 2020-04-18 14:10:53.267 IDT [couchdb] CreateDatabaseIf StatedFO087数据库 orderer-system-channel__lifecycle$$h_implicit_org_$org1$m$s$p 2020-04-18 14:10:53.453 IDT [lifecycle] ApproveChaincodeDefinitionForOrg -> INFO 088 已成功通过名称为“mycc”的链码批准，包 ID 为 cc_1my :265208bde42d32cc07779c963ccfa379439f1ac64a813bf701e5309ff08bae13', 在频道'orderer-system-channel' 上定义{sequence: 1, 背书信息: (version: '1.0,validation:', cc 插件) '，政策： '12202f4368616e6e656c2f4170706c69636174696f6e2f456e646f7273656d656e74' ），集合：（）} 2020年4月18日14：10：53.453 IDT [背书] callChaincode - > INFO 089成品chaincode：_lifecycle持续时间：4204ms通道=订货者系统用信道TxID添加= d913be80 2020年4月18日14:10:53.485 IDT [comm.grpc.server] 1 -> INFO 08a 一元调用完成 grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.17.0.11:35566

Answer 1

rak*_*aht 0

对我来说，这个问题是由于权限问题造成的。检查您的同行和订购者日志，您似乎遇到了一些沟通问题，我认为您的情况可能与我通过此问题解决的情况类似。请注意，这个问题也可能包含有用的指针。

无论如何，我的建议是按如下方式设置您的策略并重新生成初始工件。这应该可以解决您的通信问题和链代码生命周期错误：

在 configtx.yaml 中，您应该按如下方式设置组织权限：

- &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

Run Code Online (Sandbox Code Playgroud)

在那之后：

重新生成创世块
重新生成channel.tx
重新启动你的网络

归档时间：	5 年，6 月前
查看次数：	1116 次
最近记录：	5 年，3 月前