尝试在OSX上部署bna文件时,Fabric Composer快速启动失败 [英] Fabric Composer quick-start failing when trying to deploy the bna file on OSX

查看:340
本文介绍了尝试在OSX上部署bna文件时,Fabric Composer快速启动失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我尝试使用面料编曲器部署bna文件时遇到一些问题。首先,我尝试使用我自己的HyperLedger 0.6实例,创建一个连接配置文件,然后使用composer-cli来部署一个bna,并且在composer network deploy命令中出现以下错误:TypeError:无法读取未定义的属性fail
然后我删除了所有的docker图像和容器,确保所有的更新,我尝试了起始脚本,我得到完全相同的错误。
我遵循的步骤如下:

I'm having some problems trying to deploy a bna file using the fabric composer. First I tried using my own HyperLedger 0.6 instance, creating a connection profile and then using the composer-cli to deploy a bna and I got the following error during the composer network deploy command: "TypeError: Cannot read property 'fail' of undefined" Then I removed all my docker images and containers, made sure everything was updated and I tried the getting-started script and I got the exact same error. The steps I followed are the following:


  • 我在OSX 10.12上使用Docker 17.03.1-ce-mac5 stable .4

  • 我克隆了示例应用程序rep:
    git clone https://github.com/fabric-composer/sample-applications.git

  • 被收录到入门文件夹

  • 我运行npm安装

  • 我收到以下错误,这是我创建自己的HyperLedger 0.6实例时遇到的错误,并尝试部署一个bna文件使用连接配置文件和composer-cli。鉴于我使用入门包我得到相同的错误,我认为这是一个更一般的错误。任何想法?

  • I'm using Docker 17.03.1-ce-mac5 stable on OSX 10.12.4
  • I cloned the sample applications rep: git clone https://github.com/fabric-composer/sample-applications.git
  • Cd'ed to the getting-started folder
  • I run npm install
  • I get the following error, which is the same error I get when I create my own HyperLedger 0.6 instance and try to deploy a bna file using a connection profile and the composer-cli. Given that I got the same error using the getting started package I assume it's a more general error. Any ideas?

从npm安装过程中生成的vp0的docker日志显示没有明显的连接错误,初始化后,它只会重复以下消息:

The docker log from the vp0 that is generated during the npm install shows no apparent connection error, after initialization it just repeats the following message:

    15:07:22.039 [peer] ensureConnected -> DEBU 31d Touch service indicates no dropped connections
    15:07:22.039 [peer] ensureConnected -> DEBU 31e Connected to: []
    15:07:22.039 [peer] ensureConnected -> DEBU 31f Discovery knows about: []

这是执行后得到的日志文件: p>

This is the log file I got after the execution:

    0 info it worked if it ends with ok
    1 verbose cli [ '/usr/local/bin/node',
    1 verbose cli   '/usr/local/bin/npm',
    1 verbose cli   'run',
    1 verbose cli   'deployNetwork' ]
    2 info using npm@4.4.4
    3 info using node@v6.10.0
    4 verbose run-script [ 'predeployNetwork', 'deployNetwork', 'postdeployNetwork' ]
    5 info lifecycle getting-started@1.0.0~predeployNetwork: getting-started@1.0.0
    6 silly lifecycle getting-started@1.0.0~predeployNetwork: no script for predeployNetwork, continuing
    7 info lifecycle getting-started@1.0.0~deployNetwork: getting-started@1.0.0
    8 verbose lifecycle getting-started@1.0.0~deployNetwork: unsafe-perm in lifecycle true
    9 verbose lifecycle getting-started@1.0.0~deployNetwork: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/raullaprida/newfabriccomposer/sample-applications/packages/getting-started/node_modules/.bin:/usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/raullaprida/newfabriccomposer/sample-applications/packages/getting-started/node_modules/.bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/go/bin:/usr/local/MacGPG2/bin:/Users/raullaprida/gospace/bin
    10 verbose lifecycle getting-started@1.0.0~deployNetwork: CWD: /Users/raullaprida/newfabriccomposer/sample-applications/packages/getting-started
    11 silly lifecycle getting-started@1.0.0~deployNetwork: Args: [ '-c',
    11 silly lifecycle   'composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna  --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d && composer network list -n digitalproperty-network --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d' ]
    12 silly lifecycle getting-started@1.0.0~deployNetwork: Returned: code: 1  signal: null
    13 info lifecycle getting-started@1.0.0~deployNetwork: Failed to exec deployNetwork script
    14 verbose stack Error: getting-started@1.0.0 deployNetwork: `composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna  --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d && composer network list -n digitalproperty-network --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d`
    14 verbose stack Exit status 1
    14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
    14 verbose stack     at emitTwo (events.js:106:13)
    14 verbose stack     at EventEmitter.emit (events.js:191:7)
    14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
    14 verbose stack     at emitTwo (events.js:106:13)
    14 verbose stack     at ChildProcess.emit (events.js:191:7)
    14 verbose stack     at maybeClose (internal/child_process.js:877:16)
    14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
    15 verbose pkgid getting-started@1.0.0
    16 verbose cwd /Users/raullaprida/newfabriccomposer/sample-applications/packages/getting-started
    17 verbose Darwin 16.5.0
    18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "deployNetwork"
    19 verbose node v6.10.0
    20 verbose npm  v4.4.4
    21 error code ELIFECYCLE
    22 error errno 1
    23 error getting-started@1.0.0 deployNetwork: `composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna  --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d && composer network list -n digitalproperty-network --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d`
    23 error Exit status 1
    24 error Failed at the getting-started@1.0.0 deployNetwork script 'composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna  --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d && composer network list -n digitalproperty-network --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d'.
    24 error Make sure you have the latest version of node.js and npm installed.
    24 error If you do, this is most likely a problem with the getting-started package,
    24 error not with npm itself.
    24 error Tell the author that this fails on your system:
    24 error     composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna  --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d && composer network list -n digitalproperty-network --enrollId WebAppAdmin --enrollSecret DJY27pEnl16d
    24 error You can get information on how to open an issue for this project with:
    24 error     npm bugs getting-started
    24 error Or if that isn't available, you can get their info via:
    24 error     npm owner ls getting-started
    24 error There is likely additional logging output above.
    25 verbose exit [ 1, true ]


推荐答案

我有同样的问题,但删除我的所有容器和图像后,起始的样品工作。我正在使用与Docker和OSX相同的版本,npm版本为4.4.4,节点版本为6.9.5。没有连接配置文件。我建议您这样做,删除所有容器,图像和连接配置文件,然后重试。

I had the same problem but after removing all my containers and images the getting-started sample worked. I am using the same version of Docker and OSX as you, npm version is 4.4.4 and node version is 6.9.5. without the connection profile. I suggest you to do the same, remove all containers, images and the connection profile and try again.

这篇关于尝试在OSX上部署bna文件时,Fabric Composer快速启动失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆