Multiple warning which lead to License Violation for a Slave

[Dark_Ichigo]

Im getting this warning only one one of my Slave license servers which has its own License pool:

slave had no matching license for data it indexed

I dont know what its telling me here?

[linu1988]

Hello Ichigo,
Use the Deployment monitor app to see the error and remove the source/ source type as soon as possible. This will lead to violation of the error for the whole license. Pool license means all the servers included on the pool not any individual. I am sure that is some bad definition/some data is there which Splunk doesn't like ;). Thanks.

[linu1988]

No, you can see for yourself the pool would be having the license available still. Splunk does show up violation error with incompatible sourcetype/source. Kindly contact support team if you are not sure about this. But Deployment monitor app will help you resolving this error as it shows from where it's coming..

[Dark_Ichigo]

So technically it's not related to insufficient Volume license to that specific pool where the warning issue currently lyes?

[lukejadamec]

The master license server has not allocated sufficent volume to the slave.
http://docs.splunk.com/Documentation/Splunk/5.0.4/Admin/Groups,stacks,pools,andotherterminology#Lice...

[Dark_Ichigo]

I reset the license and increased the Pool size....I'll see if this is indeed the issue