我们有一个带有2个组织（org1和community-koinearth）的超级账本设置（让我们说N1）。每个组织都有2个对等方（peer1。作为锚点对等方，peer2。作为工作方对等方）。在此设置中，我们还为3个带有kafka的订购者提供订购服务。所有锚点对等点和订购者都附加到其各自的NLB。此设置完全正常。
现在，我们已经建立了另一个具有1个组织和1个对等方的超级账本基础（假设N2），并且基本上试图加入早期的网络。最初，加入者对等方成功加入N1。所有块均已同步，没有任何问题。在一段时间之后，当我们开始安装chaincode时，突然之间，我们开始在joiner peer上看到peer在线/离线消息。我们还注意到N1的锚点对等方工作正常，并且没有引发任何错误，但是网络N1的工作对等方正尝试与网络N2的细木工组织对等方联系（这很奇怪。据我所知，只有锚点对等方互相交谈） 。
以下是来自细木工组织对等方的错误日志：
2019-12-23 12:42:28.572 UTC [gossip.channel] reportMembershipChanges -> INFO ad30d Membership view has changed. peers went online: [[peer2-community-koinearth.community-koinearth:7051 ]] , current view: [[peer2-community-koinearth.community-koinearth:7051 ] [xxx-xxx.elb.ap-south-1.amazonaws.com:7051 ] [xxx-xxx.elb.ap-south-1.amazonaws.com:7051 ]]
2019-12-23 12:42:30.503 UTC [gossip.comm] sendToEndpoint -> WARN ad30e Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:30.503 UTC [gossip.discovery] expireDeadMembers -> WARN ad30f Entering [d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81]
2019-12-23 12:42:30.503 UTC [gossip.discovery] expireDeadMembers -> WARN ad310 Closing connection to Endpoint: peer2-community-koinearth.community-koinearth:7051, InternalEndpoint: , PKI-ID: d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81, Metadata:
2019-12-23 12:42:30.503 UTC [gossip.discovery] expireDeadMembers -> WARN ad311 Exiting
2019-12-23 12:42:30.511 UTC [gossip.comm] sendToEndpoint -> WARN ad312 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:32.474 UTC [gossip.comm] sendToEndpoint -> WARN ad313 Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:32.474 UTC [gossip.discovery] expireDeadMembers -> WARN ad314 Entering [d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81]
2019-12-23 12:42:32.474 UTC [gossip.discovery] expireDeadMembers -> WARN ad315 Closing connection to Endpoint: peer2-community-koinearth.community-koinearth:7051, InternalEndpoint: , PKI-ID: d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81, Metadata:
2019-12-23 12:42:32.474 UTC [gossip.discovery] expireDeadMembers -> WARN ad316 Exiting
2019-12-23 12:42:33.512 UTC [gossip.comm] sendToEndpoint -> WARN ad317 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:33.512 UTC [gossip.discovery] expireDeadMembers -> WARN ad318 Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:33.512 UTC [gossip.discovery] expireDeadMembers -> WARN ad319 Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:33.512 UTC [gossip.discovery] expireDeadMembers -> WARN ad31a Exiting
2019-12-23 12:42:33.572 UTC [gossip.channel] reportMembershipChanges -> INFO ad31b Membership view has changed. peers went offline: [[peer2-community-koinearth.community-koinearth:7051 ]] , current view: [[xxx-xxx.elb.ap-south-1.amazonaws.com:7051 ] [xxx-xxx.elb.ap-south-1.amazonaws.com:7051 ]]
2019-12-23 12:42:35.474 UTC [gossip.comm] sendToEndpoint -> WARN ad31c Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:35.474 UTC [gossip.discovery] expireDeadMembers -> WARN ad31d Entering [d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81]
2019-12-23 12:42:35.474 UTC [gossip.discovery] expireDeadMembers -> WARN ad31e Closing connection to Endpoint: peer2-community-koinearth.community-koinearth:7051, InternalEndpoint: , PKI-ID: d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81, Metadata:
2019-12-23 12:42:35.474 UTC [gossip.discovery] expireDeadMembers -> WARN ad31f Exiting
2019-12-23 12:42:35.474 UTC [gossip.comm] sendToEndpoint -> WARN ad320 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:35.475 UTC [gossip.comm] sendToEndpoint -> WARN ad321 Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:37.513 UTC [gossip.comm] sendToEndpoint -> WARN ad322 Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:38.475 UTC [gossip.comm] sendToEndpoint -> WARN ad323 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:38.475 UTC [gossip.discovery] expireDeadMembers -> WARN ad324 Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:38.475 UTC [gossip.discovery] expireDeadMembers -> WARN ad325 Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:38.475 UTC [gossip.discovery] expireDeadMembers -> WARN ad326 Exiting
2019-12-23 12:42:40.469 UTC [gossip.comm] sendToEndpoint -> WARN ad327 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:40.469 UTC [gossip.discovery] expireDeadMembers -> WARN ad328 Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:40.469 UTC [gossip.discovery] expireDeadMembers -> WARN ad329 Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:40.469 UTC [gossip.discovery] expireDeadMembers -> WARN ad32a Exiting
2019-12-23 12:42:40.514 UTC [gossip.comm] sendToEndpoint -> WARN ad32b Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:40.514 UTC [gossip.discovery] expireDeadMembers -> WARN ad32c Entering [d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81]
2019-12-23 12:42:40.514 UTC [gossip.discovery] expireDeadMembers -> WARN ad32d Closing connection to Endpoint: peer2-community-koinearth.community-koinearth:7051, InternalEndpoint: , PKI-ID: d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81, Metadata:
2019-12-23 12:42:40.514 UTC [gossip.discovery] expireDeadMembers -> WARN ad32e Exiting
2019-12-23 12:42:41.476 UTC [gossip.comm] sendToEndpoint -> WARN ad32f Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:42.499 UTC [gossip.comm] sendToEndpoint -> WARN ad330 Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:43.470 UTC [gossip.comm] sendToEndpoint -> WARN ad331 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:43.470 UTC [gossip.discovery] expireDeadMembers -> WARN ad332 Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:43.470 UTC [gossip.discovery] expireDeadMembers -> WARN ad333 Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:43.470 UTC [gossip.discovery] expireDeadMembers -> WARN ad334 Exiting
2019-12-23 12:42:45.501 UTC [gossip.comm] sendToEndpoint -> WARN ad335 Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:45.501 UTC [gossip.discovery] expireDeadMembers -> WARN ad336 Entering [d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81]
2019-12-23 12:42:45.501 UTC [gossip.discovery] expireDeadMembers -> WARN ad337 Closing connection to Endpoint: peer2-community-koinearth.community-koinearth:7051, InternalEndpoint: , PKI-ID: d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81, Metadata:
2019-12-23 12:42:45.501 UTC [gossip.discovery] expireDeadMembers -> WARN ad338 Exiting
2019-12-23 12:42:45.516 UTC [gossip.comm] sendToEndpoint -> WARN ad339 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:45.516 UTC [gossip.discovery] expireDeadMembers -> WARN ad33a Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:45.516 UTC [gossip.discovery] expireDeadMembers -> WARN ad33b Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:45.516 UTC [gossip.discovery] expireDeadMembers -> WARN ad33c Exiting
2019-12-23 12:42:46.471 UTC [gossip.comm] sendToEndpoint -> WARN ad33d Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:47.503 UTC [gossip.comm] sendToEndpoint -> WARN ad33e Failed obtaining connection for peer2-community-koinearth.community-koinearth:7051, PKIid:d668cdb388896d68e8092fe38b6588c7e71d7c8d99e3c9de7ae7e63d58e39e81 reason: context deadline exceeded
2019-12-23 12:42:48.129 UTC [gossip.comm] sendToEndpoint -> WARN ad33f Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:48.129 UTC [gossip.discovery] expireDeadMembers -> WARN ad340 Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:48.129 UTC [gossip.discovery] expireDeadMembers -> WARN ad341 Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:48.129 UTC [gossip.discovery] expireDeadMembers -> WARN ad342 Exiting
2019-12-23 12:42:48.517 UTC [gossip.comm] sendToEndpoint -> WARN ad343 Failed obtaining connection for peer2-org1.org1:7051, PKIid:81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b reason: context deadline exceeded
2019-12-23 12:42:48.517 UTC [gossip.discovery] expireDeadMembers -> WARN ad344 Entering [81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b]
2019-12-23 12:42:48.517 UTC [gossip.discovery] expireDeadMembers -> WARN ad345 Closing connection to Endpoint: peer2-org1.org1:7051, InternalEndpoint: , PKI-ID: 81f6fac2aa059963f5dd5d11d71dfa2269f047c8796deff268f312a68c16c60b, Metadata:
2019-12-23 12:42:48.517 UTC [gossip.discovery] expireDeadMembers -> WARN ad346 Exiting
我们正在使用超级账本结构1.4。
任何人都可以帮助我们解决此问题吗？让我知道是否需要更多信息？ 在此先感谢！
答案 0 :(得分：0)
如果您有不想与其他组织中的对等方进行交流的对等方，则不要在这些对等方中放置external endpoint。
换句话说，如果一个对等体定义了一个外部端点，那么它应该可以从整个网络路由。
我猜发生的是您的锚点对等点散布了无法从整个网络路由的对等点的成员资格信息，因此-其他对等点尝试连接到它们并失败。
据我所知，只有锚点同伴互相交谈。
否，所有对等方都可以与所有其他对等方进行通话。