代码之家 › 专栏 › 技术社区 › ulu

无法将BNA部署到现有的Hyperledger结构安装

hyperledger-composer grpc hyperledger hyperledger-fabric

ulu · 技术社区 · 6 年前

我正在尝试将我的bna(在我的dev机器上开发的)部署到现有的hyperledger结构安装中。结构是由另一个我无法联系的开发人员安装的。我可以启动操场并看到另一个已部署的网络,但无法部署自己的:

$ composer network install -a ./dist/noiz.bna -c PeerAdmin@composer-network-a â Installing business network. This may take a minute... Error: Error trying install business network. Error: No valid responses from any peers. Response from attempted peer comms was an error: Error: 14 UNAVAILABLE: Connect Failed Command failed

我尝试使用操场创建一个新的PeerAdmin卡,但使用该卡部署不会有帮助。结果不同(可能是因为我用admin/adminpw创建了卡):

â Installing business network. This may take a minute... Error: Error trying install business network. Error: No valid responses from any peers. Response from attempted peer comms was an error: Error: 2 UNKNOWN: chaincode error (status: 500, message: Authorization for INSTALL has been denied (error-Failed verifying that proposal's creator satisfies local MSP principal during channelless check policy with policy [Admins]: [This identity is not an admin])) Response from attempted peer comms was an error: Error: 14 UNAVAILABLE: Connect Failed Command failed

我用的是作曲家0.19.5。我相信TLS已开启。

这是我的 docker ps 以防万一:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES aa4d7a9d2ccd dev-peer0.a.example.com-export_import-0.0.1-5d8a845d4c4a29001b15ec77fa81c2b896564f083c5b2d55a9a5e5252cf98754 "/bin/sh -c 'cd /usrâ¦" 2 hours ago Up 2 hours dev-peer0.a.example.com-export_import-0.0.1 5f7a9b240371 hyperledger/fabric-peer:x86_64-1.1.0 "peer node start" 29 hours ago Up 4 hours 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peer0.a.example.com 32f274f31bd6 hyperledger/fabric-couchdb:x86_64-0.4.6 "tini -- /docker-entâ¦" 29 hours ago Up 4 hours 4369/tcp, 9100/tcp, 0.0.0.0:5984->5984/tcp couchdb.peer0.a.example.com 54b8b4e2816d hyperledger/fabric-ca:x86_64-1.1.0 "sh -c 'fabric-ca-seâ¦" 29 hours ago Up 4 hours 0.0.0.0:7054->7054/tcp ca.a.example.com ddb2594ddcfd hyperledger/fabric-orderer:x86_64-1.1.0 "orderer" 29 hours ago Up 4 hours 0.0.0.0:7050->7050/tcp orderer.example.com

这是的输出 channel list :

$ docker exec peer0.a.example.com peer channel list 2018-05-22 18:37:26.073 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP 2018-05-22 18:37:26.073 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity 2018-05-22 18:37:26.076 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2018-05-22 18:37:26.076 UTC [msp/identity] Sign -> DEBU 004 Sign: plaintext: 0A90070A5B08031A0B08E6C691D80510...631A0D0A0B4765744368616E6E656C73 2018-05-22 18:37:26.077 UTC [msp/identity] Sign -> DEBU 005 Sign: digest: 138FECCD301FA969418E2DE047CEA7B1E506880E726EC0F14E2542D33C7A0CCE 2018-05-22 18:37:26.080 UTC [main] main -> INFO 006 Exiting..... Channels peers has joined: mychannel

2 回复 | 直到 6 年前

R Thatcher 6 年前

这有点困难,因为你的同事已经建立了一个定制的织物。

这个错误 Error: 14 UNAVAILABLE: Connect Failed Command failed 通常会很快返回,这意味着CLI找不到在connection.json文件中为所用卡指定的结构。因此,您可以查看卡的connection.json并查看指定的结构和URL。文件将类似于 ~/.composer/cards/PeerAdmin@composer-network-a/connection.json 如果没有空白或换行符,则很难读取该文件,因此将其粘贴到JSON查看器中会有所帮助。

你试过了吗 composer card list 看看有没有其他的管理卡可用?

你说你可以在操场上开火-比在码头集装箱里还是在CLI上?

如果您有权访问同事生成加密材料的文件夹,您可以创建一个新的管理卡-作曲家 single org 和 multi-org 教程演示了如何基于现有加密材料构建卡。

Himani Mukne 6 年前

你的布料在运转吗?

如果没有,请在重新定向startfabric.sh文件所在的目录后启动它,然后将自己定向回.bna文件所在的文件夹。