Reporting

Cluster has only 0 peers (waiting for 2 peers to join the cluster)

hrithiktej
Communicator

Receiving as we had to redistribute the configuration to peers and took restart i think both peers took restart when cluster master was down and now we are getting this error Cluster has only 0 peers (waiting for 2 peers to join the cluster)

Please help

0 Karma
1 Solution

hrithiktej
Communicator

Support worked with me to resolve this. The first step always check splunkd.log

Here's our WebEx recap with support team:

From the cluster master the logs made it looks like a network issue but in fact, the indexers were not starting up correctly after a cluster bundle push. After a bundle is deployed, indexers will restart. The indexers were not able to delete the $SPLUNK_HOME/slave-apps.old folder since the contents were owned by another owner.

Resolution: Manually removed the $SPLUNK_HOME/slave-apps.old folder and restarted Splunk.

View solution in original post

0 Karma

hrithiktej
Communicator

Support worked with me to resolve this. The first step always check splunkd.log

Here's our WebEx recap with support team:

From the cluster master the logs made it looks like a network issue but in fact, the indexers were not starting up correctly after a cluster bundle push. After a bundle is deployed, indexers will restart. The indexers were not able to delete the $SPLUNK_HOME/slave-apps.old folder since the contents were owned by another owner.

Resolution: Manually removed the $SPLUNK_HOME/slave-apps.old folder and restarted Splunk.

0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...