2017-04-11 49 views
1

我在嘗試使用fabric composer部署bna文件時遇到了一些問題。首先,我嘗試使用自己的HyperLedger 0.6實例,創建連接配置文件,然後使用composer-cli部署bna,並且在作曲網絡部署命令期間出現以下錯誤:「TypeError:無法讀取未定義的」 然後,我刪除了所有的碼頭圖像和容器,確保所有內容都已更新,並嘗試啓動腳本,並得到完全相同的錯誤。 我遵循的步驟如下:嘗試在OSX上部署bna文件時Fabric Composer快速啓動失敗

  • 我使用的是OSX 10.12.4
  • 多克爾17.03.1-CE-MAC5穩定克隆我的樣本應用程序代表: 混帳克隆https://github.com/fabric-composer/sample-applications.git
  • Cd'ed到入門文件夾
  • 我運行npm install
  • 我得到以下錯誤,這與我創建自己的HyperLedger 0.6實例時遇到的錯誤相同,並嘗試使用連接部署bna文件個人資料和作曲家氣質。鑑於我使用入門包得到了相同的錯誤,我認爲這是一個更一般的錯誤。有任何想法嗎?

從在NPM過程中產生的安裝沒有顯示出明顯的連接錯誤的VP0泊塢窗日誌,初始化後,它只是重複了以下消息:

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: [] 

這是日誌文件I後得到執行:

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 [email protected] 
    3 info using [email protected] 
    4 verbose run-script [ 'predeployNetwork', 'deployNetwork', 'postdeployNetwork' ] 
    5 info lifecycle [email protected]~predeployNetwork: [email protected] 
    6 silly lifecycle [email protected]~predeployNetwork: no script for predeployNetwork, continuing 
    7 info lifecycle [email protected]~deployNetwork: [email protected] 
    8 verbose lifecycle [email protected]~deployNetwork: unsafe-perm in lifecycle true 
    9 verbose lifecycle [email protected]~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 [email protected]~deployNetwork: CWD: /Users/raullaprida/newfabriccomposer/sample-applications/packages/getting-started 
    11 silly lifecycle [email protected]~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 [email protected]~deployNetwork: Returned: code: 1 signal: null 
    13 info lifecycle [email protected]~deployNetwork: Failed to exec deployNetwork script 
    14 verbose stack Error: [email protected] 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 [email protected] 
    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 [email protected] 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 [email protected] 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 ] 

回答

1

我有同樣的問題,但刪除所有容器和圖像後,啓動示例工作。我使用與您相同版本的Docker和OSX,npm版本是4.4.4,節點版本是6.9.5。沒有連接配置文件。我建議你也這樣做,刪除所有容器,圖像和連接配置文件,然後重試。

+1

是的,刪除我現有的連接配置文件工作。該腳本再次生成了profiles文件夾並創建了一個默認連接,它與我所使用的連接非常相似,它只是在示例網絡的名稱和ID(快速入門演示在安裝期間創建並部署的那個)網絡「結構。 –

相關問題