我们使用基于 fabric 1.2 的 IBM Managed Blockchain，并使用 Go SDK @5e291d3a34f59beb9a8ae2bcbba388515648dc73。当我们尝试调用已安装在节点上的链代码时，我们会收到“没有要连接的节点”错误:

[fabsdk/fab] 2019/01/25 12:25:57 UTC - dispatcher.(*Dispatcher).Start.func1 -> DEBU Listening for events...
[fabsdk/fab] 2019/01/25 12:25:57 UTC - client.(*Client).connect -> DEBU ... got error in connection response: no peers to connect to
[fabsdk/common] 2019/01/25 12:25:57 UTC - retry.(*RetryableInvoker).Invoke -> DEBU Failed with err [error registering for TxStatus event: no peers to connect to] on attempt #1. Checking if retry is warranted...
[fabsdk/util] 2019/01/25 12:25:57 UTC - lazyref.(*Reference).setTimerRunning -> DEBU Timer started
[fabsdk/common] 2019/01/25 12:25:57 UTC - retry.(*RetryableInvoker).Invoke -> DEBU ... retry for err [error registering for TxStatus event: no peers to connect to] is NOT warranted after 1 attempt(s).
[fabsdk/util] 2019/01/25 12:25:57 UTC - lazyref.checkTimeStarted -> DEBU Starting timer

在放置了一些我们自己的额外日志记录后，似乎发生了故障，因为对等发现服务 (https://github.com/hyperledger/fabric-sdk-go/blob/master/pkg/client/common/discovery/dynamicdiscovery/chservice.go#L72) 没有在其响应中返回任何对等点。目标似乎设置正确。

转储 GRPC 响应后，我们得到

(*discovery.Response)(0xc4205cd600)(
results: <
    members: <
        peers_by_org: <
            key: "org1" 
            value: <> 
        > 
    >
> 
)

我们还使用相同的链代码自行设置了一个不同的结构网络，它工作正常并且相同的转储显示了这一点(一些部分已被编辑):

(*discovery.Response)(0xc42045ed20)(
results: <
    members: <
        peers_by_org: <
            key: "Org1MSP" 
            value: <
                peers: <
                    state_info: <
                        payload:"<redacted>"
                    >
                    membership_info: <payload:"<redacted>" > 
                    identity:"<redacted>" 
                >
                peers: <
                    state_info: <
                        payload:"<redacted>" 
                        signature:"<redacted>" 
                    > 
                    membership_info: <
                        payload:"<redacted>" 
                        signature:"<redacted>" 
                    > 
                    identity:"<redacted>"
                >
            >
        > 
        peers_by_org: <
            key:"Org2MSP"
            value: <
                peers: <
                    state_info:<
                        payload:"<redacted>" 
                        signature:"<redacted>" 
                    > 
                    membership_info: <
                        payload:"<redacted>" 
                    > 
                    identity:"<redacted>" 
                > 
                peers: <
                    state_info: <
                        payload:"<redacted>" 
                        signature:"<redacted>" 
                    > 
                    membership_info: < 
                        payload:"<redacted>" 
                        signature:"<redacted>" 
                    > 
                    identity:"<redacted>" 
                > 
            > 
        > 
    > 
>
)

我不确定问题是否出在 SDK 或 IBM Managed fabric 网络的配置中。如果是 IBM 网络，那么同行似乎不知何故不知道他们是组织的成员。

有没有人见过这种行为？ 我在hyperledger官方rocket chat中搜索了“no peers to connect to”的错误，也出现了一些结果，但好像是其他原因造成的，比如peer被SDK排除了，而不是响应发现请求。

最佳答案

1. 确保您在 channel 中配置了 anchor 。

2. 确保对等节点配置了外部端点，即 - (CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051)

关于go - fabric-sdk-go 错误 : No peers to connect to，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/54370764/