<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NSO generate error when ha-raft create-cluster in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896114#M7969</link>
    <description>&lt;P&gt;Hello BasharAziz,&lt;BR /&gt;&lt;BR /&gt;Thanks for sharing. The 'ncsd@' part is implicitly added as it forms the internal representation for node names together with hostname.&amp;nbsp;&lt;BR /&gt;Create cluster issue needs to be investigated further. Could you share the raft.log and devel.log?&lt;BR /&gt;From what you shared, it looks like the cluster was formed but later 'nso02.example.com' got stalled for some reason.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Erdem&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jul 2023 13:55:50 GMT</pubDate>
    <dc:creator>eaksu</dc:creator>
    <dc:date>2023-07-31T13:55:50Z</dc:date>
    <item>
      <title>NSO generate error when ha-raft create-cluster</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4870887#M7933</link>
      <description>&lt;P&gt;NSO generate error when&amp;nbsp;&lt;SPAN&gt;ha-raft create-cluster, I don't&amp;nbsp;know from where&amp;nbsp;&lt;STRONG&gt;ncsd@&lt;/STRONG&gt; is coming! and is added in the front of the hostname&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;admin@ncs# show ha-raft
ha-raft status role leader
ha-raft status leader nso01.example.com
ha-raft status member [ nso01.example.com nso02.example.com nso03.example.com ]
ha-raft status connected-node [ nso02.example.com nso03.example.com ]
ha-raft status local-node nso01.example.com
SERIAL NUMBER                             EXPIRATION DATE            FILE PATH
--------------------------------------------------------------------------------------------------
xxxx                                              2033-07-07T10:27:52+00:00  /etc/ncs/ssl/cert/nso01.crt

SERIAL NUMBER                             EXPIRATION DATE            FILE PATH
-----------------------------------------------------------------------------------------------
xxxx                                             2033-07-07T08:09:57+00:00  /etc/ncs/ssl/cert/ca.crt

ha-raft status log current-index 0
ha-raft status log applied-index 0
ha-raft status log num-entries 11
NODE                STATE              INDEX  LAG
---------------------------------------------------
ncsd@nso02.example.com  requires-snapshot  0      0
ncsd@nso03.example.com  requires-snapshot  0      0



on the seed node:
admin@ncs# show ha-raft
ha-raft status role stalled
ha-raft status leader nso01.example.com
ha-raft status connected-node [ nso01.example.com nso03.example.com ]
ha-raft status local-node nso02.example.com
SERIAL NUMBER                             EXPIRATION DATE            FILE PATH
--------------------------------------------------------------------------------------------------
xxxx                                               2033-07-07T10:27:39+00:00  /etc/ncs/ssl/cert/nso02.crt

SERIAL NUMBER                             EXPIRATION DATE            FILE PATH
-----------------------------------------------------------------------------------------------
xxxx                                                2033-07-07T08:09:57+00:00  /etc/ncs/ssl/cert/ca.crt

ha-raft status log current-index 0
ha-raft status log applied-index 0
ha-raft status log num-entries 0
admin@ncs#&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;info message:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;&amp;lt;INFO&amp;gt; 10-Jul-2023::10:31:45.441 9ccc7c1bdb1d ncs[152]: Leader[raft_server_ha_raft_1, term 26] append failure for follower {raft_identity,raft_server_ha_raft_1,'ncsd@nso02.example.com'}. Follower reports local log ends at 0. &amp;lt;INFO&amp;gt; 10-Jul-2023::10:31:45.442 9ccc7c1bdb1d ncs[152]: Leader[raft_server_ha_raft_1, term 26] append failure for follower {raft_identity,raft_server_ha_raft_1,'ncsd@nso03.example.com'}. Follower reports local log ends at 0.

&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;NSO01 leader node:&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV&gt;&lt;LI-CODE lang="markup"&gt;    &amp;lt;ha-raft&amp;gt;
    &amp;lt;enabled&amp;gt;true&amp;lt;/enabled&amp;gt;
    &amp;lt;cluster-name&amp;gt;amsterdam&amp;lt;/cluster-name&amp;gt;
    &amp;lt;listen&amp;gt;
      &amp;lt;node-address&amp;gt;nso01.example.com&amp;lt;/node-address&amp;gt;
    &amp;lt;/listen&amp;gt;
    &amp;lt;seed-nodes&amp;gt;
      &amp;lt;seed-node&amp;gt;nso02.example.com&amp;lt;/seed-node&amp;gt;
    &amp;lt;/seed-nodes&amp;gt;
    &amp;lt;ssl&amp;gt;
      &amp;lt;ca-cert-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/ca.crt&amp;lt;/ca-cert-file&amp;gt;
      &amp;lt;cert-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/nso01.crt&amp;lt;/cert-file&amp;gt;
      &amp;lt;key-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/nso01.key&amp;lt;/key-file&amp;gt;
    &amp;lt;/ssl&amp;gt;
  &amp;lt;/ha-raft&amp;gt;

&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;NSO02 seed node:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;&amp;lt;ha-raft&amp;gt;
    &amp;lt;enabled&amp;gt;true&amp;lt;/enabled&amp;gt;
    &amp;lt;cluster-name&amp;gt;amsterdam&amp;lt;/cluster-name&amp;gt;
    &amp;lt;listen&amp;gt;
      &amp;lt;node-address&amp;gt;nso02.example.com&amp;lt;/node-address&amp;gt;
    &amp;lt;/listen&amp;gt;
    &amp;lt;seed-nodes&amp;gt;
      &amp;lt;seed-node&amp;gt;nso02.example.com&amp;lt;/seed-node&amp;gt;
    &amp;lt;/seed-nodes&amp;gt;
    &amp;lt;ssl&amp;gt;
      &amp;lt;ca-cert-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/ca.crt&amp;lt;/ca-cert-file&amp;gt;
      &amp;lt;cert-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/nso02.crt&amp;lt;/cert-file&amp;gt;
      &amp;lt;key-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/nso02.key&amp;lt;/key-file&amp;gt;
    &amp;lt;/ssl&amp;gt;
  &amp;lt;/ha-raft&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;NOS03:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;&amp;lt;ha-raft&amp;gt;
    &amp;lt;enabled&amp;gt;true&amp;lt;/enabled&amp;gt;
    &amp;lt;cluster-name&amp;gt;amsterdam&amp;lt;/cluster-name&amp;gt;
    &amp;lt;listen&amp;gt;
      &amp;lt;node-address&amp;gt;nso03.example.com&amp;lt;/node-address&amp;gt;
    &amp;lt;/listen&amp;gt;
    &amp;lt;seed-nodes&amp;gt;
      &amp;lt;seed-node&amp;gt;nso02.example.com&amp;lt;/seed-node&amp;gt;
    &amp;lt;/seed-nodes&amp;gt;
    &amp;lt;ssl&amp;gt;
      &amp;lt;ca-cert-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/ca.crt&amp;lt;/ca-cert-file&amp;gt;
      &amp;lt;cert-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/nso03.crt&amp;lt;/cert-file&amp;gt;
      &amp;lt;key-file&amp;gt;${NCS_CONFIG_DIR}/ssl/cert/nso03.key&amp;lt;/key-file&amp;gt;
    &amp;lt;/ssl&amp;gt;
  &amp;lt;/ha-raft&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 10 Jul 2023 11:26:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4870887#M7933</guid>
      <dc:creator>BasharAziz</dc:creator>
      <dc:date>2023-07-10T11:26:41Z</dc:date>
    </item>
    <item>
      <title>Re: NSO generate error when ha-raft create-cluster</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896114#M7969</link>
      <description>&lt;P&gt;Hello BasharAziz,&lt;BR /&gt;&lt;BR /&gt;Thanks for sharing. The 'ncsd@' part is implicitly added as it forms the internal representation for node names together with hostname.&amp;nbsp;&lt;BR /&gt;Create cluster issue needs to be investigated further. Could you share the raft.log and devel.log?&lt;BR /&gt;From what you shared, it looks like the cluster was formed but later 'nso02.example.com' got stalled for some reason.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Erdem&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 13:55:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896114#M7969</guid>
      <dc:creator>eaksu</dc:creator>
      <dc:date>2023-07-31T13:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: NSO generate error when ha-raft create-cluster</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896133#M7970</link>
      <description>&lt;P&gt;Hi Erdem,&lt;/P&gt;
&lt;P&gt;The problem is been solved with Cisco TAC.&lt;/P&gt;
&lt;P&gt;we simply deleted the snapshot:&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;rm -rf /nso/run/state/raft/ha_raft.1/snapshot.0.0&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;and now it works again.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 14:23:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896133#M7970</guid>
      <dc:creator>BasharAziz</dc:creator>
      <dc:date>2023-07-31T14:23:18Z</dc:date>
    </item>
    <item>
      <title>Re: NSO generate error when ha-raft create-cluster</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896604#M7974</link>
      <description>&lt;P&gt;I am glad that your issue was resolved.&lt;BR /&gt;Cheers!&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 08:31:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-generate-error-when-ha-raft-create-cluster/m-p/4896604#M7974</guid>
      <dc:creator>eaksu</dc:creator>
      <dc:date>2023-08-01T08:31:49Z</dc:date>
    </item>
  </channel>
</rss>

