Getting Data In

1 orphaned indexer reported by 1 indexer

sathiyamoorthy
Explorer

What made this warning appear ?

1 orphaned indexer reported by 1 indexer

How to Correct by midnight to avoid violation.

Tried finding out the issue, but can't get any clue yet. Any help is much appreciated.

There is only one indexer in the same splunk server, so assuming it can't go Orphaned, then what else?

Tags (2)
0 Karma

Masa
Splunk Employee
Splunk Employee

This happens when a license slave is not assigned to any license pool.

  1. License slave is connected to a license master
  2. License pool requires manual allocation of license slaves
  3. The license slave is not assigne to a pool manually.

So, please go edit a pool and add the slave to the pool manually

Please see the following answer, too.
http://splunk-base.splunk.com/answers/41467/why-did-a-license-slave-indexer-receive-a-license-violat...

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...