Hyperledger Fabric 订购者抛出故障节点错误状态:NOT_FOUND

发布于 2025-01-17 05:17:26 字数 2270 浏览 1 评论 0原文

我的集群上运行着 5 个排序节点(版本 2.4)。我尝试轮换他们的 tls 证书并犯了一些错误。该网络是一个开发网络,现在所有排序节点都会抛出下面提到的错误:

2022-03-25 10:18:13.947 UTC 014c WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer1.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.947 UTC 014d WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer1.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.948 UTC 014e WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer4.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.948 UTC 014f WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer4.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.948 UTC 0150 WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer2.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.949 UTC 0151 WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer2.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.949 UTC 0152 WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer0.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.949 UTC 0153 WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer0.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.953 UTC 0154 WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer3.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.953 UTC 0155 WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer3.org1.com:7050 channel=assetschannel

由于它是一个开发网络,我可以重置整个网络,但我想将这种情况视为发生在生产网络上,因为我们可以不重置生产网络,我想获得一些关于如何从该错误中恢复排序节点的建议。

任何建议将不胜感激

I have 5 ordering nodes (version 2.4) running on my cluster. I tried to rotate their tls certs and made some mistake. The network is a dev network and now all the ordering nodes are throwing below mentioned error:

2022-03-25 10:18:13.947 UTC 014c WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer1.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.947 UTC 014d WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer1.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.948 UTC 014e WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer4.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.948 UTC 014f WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer4.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.948 UTC 0150 WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer2.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.949 UTC 0151 WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer2.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.949 UTC 0152 WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer0.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.949 UTC 0153 WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer0.org1.com:7050 channel=assetschannel
2022-03-25 10:18:13.953 UTC 0154 WARN [orderer.common.cluster.puller] fetchLastBlockSeq -> Received status:NOT_FOUND  from orderer3.org1.com:7050: faulty node, received: status:NOT_FOUND  channel=assetschannel
2022-03-25 10:18:13.953 UTC 0155 WARN [orderer.common.cluster.puller] func1 -> Received error of type 'faulty node, received: status:NOT_FOUND ' from orderer3.org1.com:7050 channel=assetschannel

Since it is a dev network, I can reset the entire network but I want to consider this scenario as if it occurred on a production network and because we can not reset a production network, I would like to get some suggestions on how we can recover the ordering nodes from this error.

Any suggestions would be appreciated

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

短叹 2025-01-24 05:17:26

据我所知,如果我们有账本和 WAL 的备份,我们可以恢复它们并恢复它们。打开网络。否则,我们需要重置网络。

As per my knowledge, If we have backup of the ledger and WAL, we can restore them & bring up the network. Otherwise, we need to reset the network.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文