Getting Data In

replicationStatus Failed failure info: failed_because_HTTP_REPLY_ERROR_CODE

pbalbasm
Path Finder

Hi guys,

I'm getting the following message in one of the indexers from the cluster.

"DistributedPeerManager - Unable to distribute to peer named XXXXXXXXXXXX.com at uri https://xxx.xxx.xxx.xxx:8089 because replication was unsuccessful. replicationStatus Failed failure info: failed_because_HTTP_REPLY_ERROR_CODE"

I was searching through the documentation and couldn't find anything.

Does someone know what could be the possible reason of this failure?

Thanks in advance.

Regards.

0 Karma

effem
Communicator

This can happen, when both systems have diverting License-Master/Licenses.

You should set the licensemaster to the same master_uri/same license pool.

On the License-Slave:

splunk edit licenser-localslave -master_uri https://<license-master>:8089

Or via server.conf:

[license]
master_uri = https://<licensemaster>:8089

However HTTP 400 Response is a very ambiguous message. Splunk should implement a proper Error-Message for this case.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.    Watch On-Demand   In this Tech Talk, Splunk platform specialists ...

How to Break a Kubernetes Pod on Purpose and Let the AI Troubleshooting Agent Find ...

Let's say I've just rolled out a Kubernetes Deployment with a typo in the image tag. Nothing explodes. The pod ...

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...