Hi,
We created a new Search Head Cluster that includes one Deployer and 2 Cluster members with one being the captain. Deployment went well and the cluster members can recognize each other.
Captain:
dynamic_captain : 1
elected_captain : Thu May 12 15:37:23 2016
id : *******************************
initialized_flag : 1
label : splunk03.x.y.z
maintenance_mode : 0
mgmt_uri : https://splunk03.x.y.z:8089
min_peers_joined_flag : 1
rolling_restart_flag : 0
service_ready_flag : 1
Members:
splunk03.x.y.z
label : splunk03.x.y.z
mgmt_uri : https://splunk03.x.y.z:8089
mgmt_uri_alias : https://X.X.X.56:8089
status : Up
splunk04.x.y.z
label : splunk04.x.y.z
mgmt_uri : https://splunk04.x.y.z:8089
mgmt_uri_alias : https://X.X.X.57:8089
status : Up
But now when we are trying to add another member, it is giving errors. We tried both options. From an existing member using `splunk add shcluster-member -new_member_uri :` and from the new member, using `splunk add shcluster-member -current_member_uri :`
While trying from the new member, packet capture shows communication between splunk05 (New member) and splunk04 (existing member). In splunkd.log on splunk05, following messages are repeated.
05-20-2016 16:04:59.958 -0400 WARN SHClusterHandler - Failed to proxy call to member. https://splunk04.x.y.z:8089 WARN: call not properly authenticated
05-20-2016 16:05:00.081 -0400 WARN SHClusterHandler - Failed to proxy call to member. https://splunk04.x.y.z:8089 WARN: call not properly authenticated
- Verified server.conf for all members and made sure mgmt_uri is correct.
- All members have same value for replication_factor, replication_port, shcluster_lable and pass4SymmKey.
- Firewall rules allow communication on management port.
- Admin credential being used to authenticate are correct.
I could not find any articles referring to this proxy error. Are we missing anything obvious? Are these only warnings which can be ignored?
Thanks in advance..
~ Abhi
↧