Deployment Architecture

How to fix sourcetype(s) without a corresponding license pool

liang_psc
New Member

Dear supports,
I use the OEM license, which means you can only usr the specific fixed prefix sourcetype "psc_".
I uploaded a csv file with default sourcetype, which I should use the sourcetype with prefix psc_.
After I uploaded this file, I got the Orphaned indexer alerts (1), the Message TEXT:
This slave indexed data/sourcetype(s) without a corresponding license pool
The Category is "orphan_slave".
I have delete all the csv data upload with default sourcetype. and delete sourcetype csv. But the alert still here.
How can I fix this alert?
Thanks!
Bright

Tags (1)
0 Karma

koshyk
Super Champion

I believe you got multiple issues
1. I assume you got a indexer cluster? if yes, then your indexer slaves are NOT connected to your license master via Cluster Master. This setup requires bit of reading if you are new to Splunk (or request PS support)
2. Did you write index-time settings for your new psc_ sourcetype?

0 Karma

liang_psc
New Member

Thanks for your reply!
1.I am just install a single Splunk instance. No cluster.
2.I could use the right sourcetype(with prefix psc_) successfully. In this problem, I just select the wrong sourcetype, and it generated an alert.
I think the alert is about the sourcetype, "sourcetype(s) without a corresponding license pool"

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...