首页 文章

Chaincode for Developers Cli error terminal 3

提问于
浏览
1

我正在尝试使用链代码为终端3的开发人员教程“http://hyperledger-fabric.readthedocs.io/en/latest/chaincode4ade.html ". I was able to complete the steps till Terminal 2 but get an Error in the command " docker exec -it cli bash”部署链代码 .

1号航站楼的输出:

[]从shim peer |收到消息REGISTER 2017-08-22 23:29:26.025 UTC [chaincode] HandleMessage - > DEBU 1a9 [] Fabric端处理类型的ChaincodeMessage:注册状态创建的peer 2017-08-22 23:29:26.025 UTC [chaincode] beforeRegisterEvent - > DEBU 1aa在状态创建的同伴中收到REGISTER | 2017-08-22 23:29:26.025 UTC [chaincode] registerHandler - > DEBU 1ab注册处理程序完成链代码mycc:0 peer | 2017-08-22 23:29:26.025 UTC [chaincode] beforeRegisterEvent - > DEBU 1ac获得了chaincodeID = name:“mycc:0”的寄存器,发回寄存器对等端| 2017-08-22 23:29:26.025 UTC [chaincode] notifyDuringStartup - > DEBU 1ad什么都没有通知(开发模式?)peer | 2017-08-22 23:29:26.025 UTC [chaincode] notifyDuringStartup - > DEBU 1ae发送READY peer | 2017-08-22 23:29:26.025 UTC [chaincode] processStream - > DEBU 1af []移动状态消息READY peer | 2017-08-22 23:29:26.025 UTC [chaincode] HandleMessage - > DEBU 1b0 [] Fabric端处理ChaincodeMessage类型:READY in state established peer | 2017-08-22 23:29:26.026 UTC [chaincode] enterReadyState - > DEBU 1b1 []进入状态就绪的同行2017-08-22 23:29:26.026 UTC [chaincode]通知 - > DEBU 1b2通知程序Txid:不存在同行2017-08-22 23:29:26.026 UTC [chaincode] processStream - > DEBU 1b3 []发送状态信息READY

2号航站楼的输出:

CORE_PEER_ADDRESS = peer:7051 CORE_CHAINCODE_ID_NAME = mycc:0 ./sacc 2017-08-22 23:29:26.020 UTC [shim] SetupChaincodeLogging - > INFO 001未提供Chaincode日志级别;默认为:INFO 2017-08-22 23:29:26.020 UTC [shim] SetupChaincodeLogging - > INFO 002 Chaincode(构建级别:)启动...

3号航站楼的输出:

docker exec -it cli bash来自守护程序的错误响应:容器37efeab8d4930060c9de46d3bab9ab1ab034781be26b4a5176b80b54d6c1180b未运行

我找不到任何解决方案 . 谁能帮我?我正在使用MacOS X.

我在yaml文件中取消注释了“command:/ bin / bash -c'./ script.sh'”行 .

终端1后docker ps的输出:

docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES befcf58f4b59 hyperledger / fabric-ccenv“/ bin / bash -c'well ...”21秒前20秒chaincode 3129dac3e13b hyperledger / fabric-peer“peer node start - .. . “21秒前20秒0.0.0.0:7051->7051/tcp,.0.0.0:7053->7053/tcp peer 56a92979e7cb hyperledger / fabric-orderer”orderer“22秒前21秒0.0.0.0:7050 - > 7050 / tcp orderer

终端2后docker ps的输出:

docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES befcf58f4b59 hyperledger / fabric-ccenv“/ bin / bash -c'well ...”2分钟前最多2分钟链码3129dac3e13b hyperledger / fabric-peer“对等节点启动 - .. . “2分钟前上升2分0.0.0.0:7051->7051/tcp,0.0.0.0:7053->7053/tcp peer 56a92979e7cb hyperledger / fabric-orderer”orderer“2分钟前上涨2分钟0.0.0.0:7050 - > 7050 / tcp orderer

运行.yaml文件时出现Cli错误:

返回虚拟拒绝所有策略,因为在/ Application / Admins orderer |中找不到管理员2017-08-23 23:09:50.644 UTC [政策] GetPolicy - > DEBU 154返回政策读者评价订购者| 2017-08-23 23:09:50.644 UTC [policies] GetPolicy - > DEBU 155返回虚拟拒绝所有策略,因为在/ Application / Readers orderer中找不到读者2017-08-23 23:09:50.644 UTC [政策] GetPolicy - > DEBU 156返回政策作者评价orderer | 2017-08-23 23:09:50.645 UTC [policies] GetPolicy - > DEBU 157返回虚拟拒绝所有策略,因为在/ Application / Writers orderer中找不到编写器2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 158添加到配置 Map :[Groups] / Channel orderer | 2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 159添加到配置图:[Groups] / Channel / Application orderer | 2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 15a添加到配置图:[Groups] / Channel / Application / SampleOrg cli |错误:出现意外状态:BAD_REQUEST orderer | 2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 15b添加到配置图:[Values] / Channel / Consortium orderer | 2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 15c添加到配置图:[Groups] / Channel cli |用法:cli |窥视channel create [flags] cli | cli |标志:orderer | 2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 15d添加到配置图:[Groups] / Channel / Application cli | -c,--channelID string如果是newChain命令,则创建通道ID . orderer | 2017-08-23 23:09:50.645 UTC [common / configtx] addToMap - > DEBU 15e添加到配置图:[Groups] / Channel / Application / SampleOrg cli | -f, - file string由configtxgen等工具生成的配置事务文件,用于提交给orderer orderer . 2017-08-23 23:09:50.646 UTC [common / configtx] addToMap - > DEBU 15f添加到配置图:[Policy] / Channel / Application / Admins cli | -t, - timeoutout int通道创建超时(默认为5)cli | cli |全局标志:cli | --cafile string包含用于排序 endpoints cli |的PEM编码的可信证书的文件的路径--logging-level string默认日志记录级别和覆盖,请参阅core.yaml以获取完整语法cli | -o, - orderer string订购服务 endpoints orderer | 2017-08-23 23:09:50.646 UTC [common / configtx] addToMap - > DEBU 160添加到配置 Map :[Policy] / Channel / Application / Writers cli | --test.coverprofile string Done(默认为“coverage.cov”)cli | --tls与orderer endpoints cli |进行通信时使用TLS -v, - version显示结构对等服务器cli的当前版本orderer | 2017-08-23 23:09:50.646 UTC [common / configtx] addToMap - > DEBU 161添加到配置图:[Policy] / Channel / Application / Readers orderer | 2017-08-23 23:09:50.646 UTC [common / configtx] addToMap - > DEBU 162添加到配置 Map :[Values] / Channel / Consortium orderer | 2017-08-23 23:09:50.646 UTC [orderer / common / broadcast]句柄 - > WARN 163拒绝CONFIG_UPDATE因为:错误授权更新:验证DeltaSet时出错:元素[Policy] / Channel / Application / Writers:mod_policy的mod_policy无效没有设定订货人| 2017-08-23 23:09:50.646 UTC [orderer / main] func1 - > DEBU 164 Closing Broadcast stream orderer | 2017-08-23 23:09:50.648 UTC [orderer / common / deliver]句柄 - > WARN 165从流中读取错误:rpc错误:代码=取消desc =上下文取消orderer | 2017-08-23 23:09:50.649 UTC [orderer / main] func1 - > DEBU 166 Closing Deliver stream

2 回答

  • 0

    我能够通过在“fabric-samples / chaincode-docker-devmode / docker-compose-simple.yaml”文件中注释掉“command:/ bin / bash -c'./script.sh'”这一行来解决这个问题 . .

  • 1

    我已经阅读了这个https://jira.hyperledger.org/browse/FAB-5309如何解决,看起来问题出在chaincode-docker-devmode的工件上

    附:只需将面料更新到1.0.2并拉出新的面料样品仓库,启动新容器,瞧!

    最好的鼻子

相关问题