Git 登录到对等网络hyperledger fabric（eca.user）有什么问题？

有人能帮我解决这个问题吗？我不确定对等网络HyperLedger结构的登录有什么问题

我跟着他们的脚步走了进去 http://hyperledger-fabric.readthedocs.io/en/latest/Setup/Chaincode-setup/ ，在有关安全功能的说明下。我试过了。我做了流浪的宋承宪， cd$GOPATH/src/github.com/hyperledger/fabric/peer，后跟

peer network login admin 

membersrvc.yaml的默认文件

我确实尝试了其他用户名和密码，但都没有工作，因为它显示了错误。据我所知，当它显示错误时，意味着用户和密码不正确。然而，我复制并粘贴了用户和密码，但它不起作用。我可以知道使用git bash登录对等网络hyperledger fabric的用户和密码有什么问题吗

用户和密码seca.user-显示用户和密码将显示在以下成员srvc.yaml中：

    eca:


              # This hierarchy is used to create the Pre-key tree, affiliations is the top of this hierarchy, 'banks_and_institutions' is used to create the key associated to auditors of both banks and
                # institu

tions, 'banks' is used to create a key associated to auditors of banks, 'bank_a' is used to create a key associated to auditors of bank_a, etc.
            affiliations:
               banks_and_institutions:
                  banks:
                      - bank_a
                      - bank_b
                      - bank_c
                  institutions:
                      - institution_a
            users:
                    #
                    # The fields of each user are as follows:
                    #    <EnrollmentID>: <system_role (1:client, 2: peer, 4: validator, 8: auditor)> <EnrollmentPWD> <Affiliation> <Affiliation_Role> <JSON_Metadata>
                    #
                    # The optional JSON_Metadata field is of the following format:
                    #   { "registrar": { "roles": <array-of-role-names>, "delegateRoles": <array-of-role-names> } }
                    # The 'registrar' section is used to control access to registration of new users directly via the ECAA.RegisterUser GRPC call.
                    # (See the 'fabric/membersrvc/protos/ca.proto' file for the definition of ECAA.RegisterUser.)
                    # Note that this also controls who can register users via the client SDK.
                    #
                    # Only users with a 'registrar' section may be a registrar to register other users.  In particular,
                    # 1) the "roles" field specifies which member roles may be registered by this user, and
                    # 2) the "delegateRoles" field specifies which member roles may become the "roles" field of registered users.
                    # The valid role names are "client", "peer", "validator", and "auditor".
                    #
                    # Example1:
                    #    The 'admin' user below can register clients, peers, validators, or auditors; furthermore, the 'admin' user can register other
                    #    users who can then register clients only.
                    #
                    # Example2:
                    #    The 'WebAppAdmin' user below can register clients only, but none of the users registered by this user can register other users.
                    #
                    admin: 1 Xurw3yU9zI0l institution_a '{"registrar":{"roles":["client","peer","validator","auditor"],"delegateRoles":["client"]}}'
                    WebAppAdmin: 1 DJY27pEnl16d institution_a '{"registrar":{"roles":["client"]}}'
                    lukas: 1 NPKYL39uKbkj bank_a
                    system_chaincode_invoker: 1 DRJ20pEql15a institution_a
                    diego: 1 DRJ23pEQl16a institution_a
                    jim: 1 6avZQLwcUe9b bank_a
                    binhn: 1 7avZQLwcUe9q institution_a
                    testing: 1 test123 institution_a

                    # Users for asset transfer with roles test located at
                    # sdk/node/test/unit/asset-mgmt-with-roles.js
                    alice: 1 CMS10pEQlB16 bank_a
                    bob: 1 NOE63pEQbL25 bank_a
                    assigner: 1 Tc43PeqBl11 bank_a

                    vp: 4 f3489fy98ghfAD

                    test_vp0: 4 MwYpmSRjupbT
                    test_vp1: 4 5wgHK9qqYaPy
                    test_vp2: 4 vQelbRvja7cJ
                    test_vp3: 4 9LKqKH5peurL
                    test_vp4: 4 Pqh90CEW5juZ
                    test_vp5: 4 FfdvDkAdY81P
                    test_vp6: 4 QiXJgHyV4t7A
                    test_vp7: 4 twoKZouEyLyB
                    test_vp8: 4 BxP7QNh778gI
                    test_vp9: 4 wu3F1EwJWHvQ

    # Uncomment this section to activate devnet setup as specficied in
    # devnet-setup.md
    #
    #               vp0: 4 vp0_secret
    #               vp1: 4 vp1_secret

                    test_user0: 1 MS9qrN8hFjlE bank_a
                    test_user1: 1 jGlNl6ImkuDo institution_a
                    test_user2: 1 zMflqOKezFiA bank_c
                    test_user3: 1 vWdLCE00vJy0 bank_a
                    test_user4: 1 4nXSrfoYGFCP institution_a
                    test_user5: 1 yg5DVhm0er1z bank_b
                    test_user6: 1 b7pmSxzKNFiw bank_a
                    test_user7: 1 YsWZD4qQmYxo institution_a
                    test_user8: 1 W8G0usrU7jRk bank_a
                    test_user9: 1 H80SiB5ODKKQ institution_a

                    test_nvp0: 2 iywrPBDEPl0K bank_a
                    test_nvp1: 2 DcYXuRSocuqd institution_a
                    test_nvp2: 2 flpChShlY7xt bank_c
                    test_nvp3: 2 jeruawMomclo bank_a
                    test_nvp4: 2 RMYVxSZCk370 institution_a
                    test_nvp5: 2 XHYVCIJGZGK7 bank_b
                    test_nvp6: 2 4cIn63j8ahYp bank_a
                    test_nvp7: 2 E7FAJUtWVn2h institution_a
                    test_nvp8: 2 LJu8DkUilBEH bank_a
                    test_nvp9: 2 VlEsBsiyXSjw institution_a

输入密码后会出现以下错误：

2016/09/14 07:05:33 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 0.0.0.0:7051: getsockopt: connection refused"; Reconnecting to {"0.0.0.0:7051" <nil>}
2016/09/14 07:05:35 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 0.0.0.0:7051: getsockopt: connection refused"; Reconnecting to {"0.0.0.0:7051" <nil>}
2016/09/14 07:05:35 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 0.0.0.0:7051: getsockopt: connection refused"; Reconnecting to {"0.0.0.0:7051" <nil>}
Error: Error trying to connect to local peer: grpc: timed out when dialing
Usage:
  peer network login <username> [flags]

Flags:
  -p, --password string   The password for user. You will be requested to enter the password if this flag is not specified.

Global Flags:
      --logging-level string       Default logging level and overrides, see core.yaml for full syntax
      --test.coverprofile string   Done (default "coverage.cov")
  -v, --version                    Display current version of fabric peer server

vagrant@hyperledger-devenv:v0.0.11-c6e56d6:/opt/gopath/src/github.com/hyperledger/fabric/peer$

但是，我可以知道为什么我只能登录一次吗？例如，如果我想再次登录到admin，它不会提示输入密码，并且会有类似的内容

vagrant@hyperledger-devenv:v0.0.11-087d2ea:/opt/gopath/src/github.com/hyperledger/fabric/peer$ peer network login admin
vagrant@hyperledger-devenv:v0.0.11-087d2ea:/opt/gopath/src/github.com/hyperledger/fabric/peer$

---

你犯错误的原因

2016/09/14 07:05:33 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 0.0.0.0:7051: getsockopt: connection refused"; Reconnecting to {"0.0.0.0:7051" <nil>}

请注意，我正在开发模式下运行它

打开另一个终端并运行以下操作：

peer network login lukas

提示时输入或粘贴密码

在启动对等机的第二个窗口中，您将看到以下输出：

08:48:18.978 [crypto] RegisterClient -> INFO 01b Registering client [lukas] with name [lukas]...
08:48:19.179 [crypto] Info -> INFO 01c [client.lukas]  Register crypto engine...
08:48:19.181 [crypto] Info -> INFO 01d [client.lukas]  Register crypto engine...done.
08:48:19.183 [crypto] RegisterClient -> INFO 01e Registering client [lukas] with name [lukas]...done!

---

如果有帮助，请告诉我。

错误原因

2016/09/14 07:05:33 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 0.0.0.0:7051: getsockopt: connection refused"; Reconnecting to {"0.0.0.0:7051" <nil>}

请注意，我正在开发模式下运行它

打开另一个终端并运行以下操作：

peer network login lukas

提示时输入或粘贴密码

在启动对等机的第二个窗口中，您将看到以下输出：

08:48:18.978 [crypto] RegisterClient -> INFO 01b Registering client [lukas] with name [lukas]...
08:48:19.179 [crypto] Info -> INFO 01c [client.lukas]  Register crypto engine...
08:48:19.181 [crypto] Info -> INFO 01d [client.lukas]  Register crypto engine...done.
08:48:19.183 [crypto] RegisterClient -> INFO 01e Registering client [lukas] with name [lukas]...done!

---

如果有帮助，请告诉我。

问题“为什么我只能登录一次？”第二部分的答案如下：

用户只能有一个注册证书。会员服务将在第一个用户登录网络时生成唯一的注册证书。 一旦注册证书颁发，会员服务将通过覆盖注册密码“禁用”用户帐户

在您的示例中，当您向同一对等方发送“login”命令时，该对等方将检查用户是否已注册，并且不会向会员服务发送任何请求

在配置多个对等点时，用户只能登录其中一个。第二次尝试通过其他对等方登录将导致：

Error: Error on client login: roc error: code = 2 desc = Identity or token does not match.

---

问题“为什么我只能登录一次？”第二部分的答案如下：

用户只能有一个注册证书。会员服务将在第一个用户登录网络时生成唯一的注册证书。 一旦注册证书颁发，会员服务将通过覆盖注册密码“禁用”用户帐户

在您的示例中，当您向同一对等方发送“login”命令时，该对等方将检查用户是否已注册，并且不会向会员服务发送任何请求

在配置多个对等点时，用户只能登录其中一个。第二次尝试通过其他对等方登录将导致：

Error: Error on client login: roc error: code = 2 desc = Identity or token does not match.

---

您是否通过在单独的终端窗口中首先启动对等节点启动对等进程？对不起。我不明白你的意思。是否有任何例子或网站，我可以参考？链接，你已经张贴在上面，请仔细阅读运行验证对等部分。它应该在一个单独的终端ID中运行。您首先在一个单独的终端窗口中通过对等节点启动对等进程？对不起。我不明白你的意思。是否有任何例子或网站，我可以参考？链接，你已经张贴在上面，请仔细阅读运行验证对等部分。它应该在一个单独的终端运行感谢您的帮助！我可以得到类似你的东西，但我只能登录到管理员一次。例如，如果我登录lukas，我就不能再次登录lukas。我能知道为什么会这样吗？我已经显示了上面的更新版本@苏菲亚·戈里谢谢你的帮助！我可以得到类似你的东西，但我只能登录到管理员一次。例如，如果我登录lukas，我就不能再次登录lukas。我能知道为什么会这样吗？我已经显示了上面的更新版本@苏菲扬·古里