All Apps and Add-ons
Highlighted

Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

New Member

We have updated the splunk servers from 6.5 to 6.6 and are seeing the following errors

Search peer has the following message: Failed to register with cluster master reason: failed method=POST path=/services/cluster/master/peers/?outputmode=json master=:8089 rv=0 gotConnectionError=1 gotUnexpectedStatusCode=0 actualresponsecode=502 expectedresponsecode=2xx statusline="Error connecting: Connection refused" socketerror="Connection refused" remoteerror= [ event=addPeer status=retrying AddPeerRequest: { id= activebundleid=9884CA425F0224F22F37BE784337C463 addtype=Initial-Add basegenerationid=0 batchserialno=1 batchsize=4 forwarderdatarcvport=9997 forwarderdatausessl=0 lastcompletegenerationid=0 latestbundleid=9884CA425F0224F22F37BE784337C463 mgmtport=8089 name=6A1C1358-0C02-4D60-B58B-EA903E3D0991 registerforwarderaddress= registerreplicationaddress= registersearchaddress= replicationport=8080 replicationusessl=0 replications= servername= site=default splunkversion=6.6.0 splunkdbuild_number=1c4f3bbe1aea status=Up } ].

Are there any more steps required for the search peers to register again?

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

New Member

I'm also getting

Failed to register with cluster master reason: failed method=POST path=/services/cluster/master/peers/?outputmode=json master=splunkdeployer:8089 rv=0 gotConnectionError=1 gotUnexpectedStatusCode=0 actualresponsecode=502 expectedresponsecode=2xx statusline="Error connecting: Connection refused" socketerror="Connection refused" remoteerror= [ event=addPeer status=retrying AddPeerRequest: { id= activebundleid=4B4EFCBBAA14C9AD694D9BE6FAB82C22 addtype=Initial-Add basegenerationid=0 batchserialno=1 batchsize=1 forwarderdatarcvport=9997 forwarderdatausessl=0 lastcompletegenerationid=0 latestbundleid=4B4EFCBBAA14C9AD694D9BE6FAB82C22 mgmtport=8089 name=F645968A-05ED-411F-8F5E-C467EED3B184 registerforwarderaddress= registerreplicationaddress= registersearchaddress= replicationport=9887 replicationusessl=0 replications= servername=site1indexer1 site=site1 splunkversion=6.6.0 splunkdbuild_number=1c4f3bbe1aea status=Up } ].

nmap shows ports open on all relevant machines,I'm also getting

Failed to register with cluster master reason: failed method=POST path=/services/cluster/master/peers/?outputmode=json master=splunkdeployer:8089 rv=0 gotConnectionError=1 gotUnexpectedStatusCode=0 actualresponsecode=502 expectedresponsecode=2xx statusline="Error connecting: Connection refused" socketerror="Connection refused" remoteerror= [ event=addPeer status=retrying AddPeerRequest: { id= activebundleid=4B4EFCBBAA14C9AD694D9BE6FAB82C22 addtype=Initial-Add basegenerationid=0 batchserialno=1 batchsize=1 forwarderdatarcvport=9997 forwarderdatausessl=0 lastcompletegenerationid=0 latestbundleid=4B4EFCBBAA14C9AD694D9BE6FAB82C22 mgmtport=8089 name=F645968A-05ED-411F-8F5E-C467EED3B184 registerforwarderaddress= registerreplicationaddress= registersearchaddress= replicationport=9887 replicationusessl=0 replications= servername=site1indexer1 site=site1 splunkversion=6.6.0 splunkdbuild_number=1c4f3bbe1aea status=Up } ].

This is on a new install, so assumed it was a configuration issue, however testing using nmap shows the ports are open on relevant boxes.

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

New Member

this issue appears to be resolved in 6.6.3

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Engager

I am having the same issue and we are on version 6.6.3.2.

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Path Finder

Any solution to this issue? We upgraded to v6.6.1 over a month ago but the message just started showing up on all Indexers today.

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Path Finder

any solution ?

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Path Finder

hi .. any solution ?

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Engager

I had to open a case with Splunk support, and they had to patch. I suggest contacting Splunk if you have this issue. I suspect this has been fixed with newer versions of Splunk.

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Path Finder

we are already on latest version 7.0.3

and thanks .. we have opened the case as well with splunk

0 Karma
Highlighted

Re: Update to 6.6 resulted in the error "Failed to register with cluster master" reason "Error connecting: Connection refused"

Explorer

issue resolved?
Why because, now i am facing same issue in 7.0 version

0 Karma