Shulou(Shulou.com)06/02 Report--

This article will explain in detail how to solve the problems caused by consul restart. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

13:35:42 on 2019-07-12 [ERR] consul: "Catalog.Register" RPC failed to server 172.16.0.234 RPC failed to server 8300: rpc error making call: rpc error making call: failed inserting node: Error while renaming Node ID: "183f4599-bebb-f6ac-1269-d88d70b187eb": Node name C1 is reserved by node b2eab251-544d-7ecf-a5a0-2efa3b40da94 with name C1

2019-07-12 13:35:42 [WARN] agent: Syncing node info failed. Rpc error making call: rpc error making call: failed inserting node: Error while renaming Node ID: "183f4588-bebb-f6ac-1269-d88d70b187eb": Node name C1 is reserved by node b2eab232-544d-7ecf-a5a0-2efa3b40da94 with name C1

Each restart will generate a new nodeid, but the original nodeid has not been deleted in other nodes in the cluster, and the above exception will be thrown

The solution is to manually replace the id in node-id with the original id and restart.

On how to solve the problems caused by consul restart to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.