Installation

Why am I seeing "Pool Warning - Correct by midnight to avoid violation Learn more This pool contains slave(s) with 2 warnings"?

AaronMoorcroft
Communicator

Hi Guys

I have a question regarding a pool warning. I exceeded our license twice: once of the 13th and again on the 14th. Since then, all has been fine. We're now on the 18th, so it's been 4 days since we exceeded the license, however, I'm still seeing this error:

Pool Warning - Correct by midnight to avoid violation Learn more  This pool contains slave(s) with 2 warnings  

it has said this for the last few days and nothing so far has happened, I was hoping someone could advise if this is just a bug or explain what the issue is here. We're running Splunk 6.3.0

Thanks in advance for any help received

Labels (1)
0 Karma

renjith_nair
Legend

If you exceed your licensed daily volume on any one calendar day, you will get a violation warning. The message persists for 14 days. If you have 5 or more warnings on an Enterprise license or 3 warnings on a Free license in a rolling 30-day period, you are in violation of your license, and search will be disabled for the offending pool(s). Other pools will remain searchable and be unaffected, as long as the total license usage from all pools does not exceed the total license quota for the license master.

Reference : http://docs.splunk.com/Documentation/Splunk/6.2.0/Admin/Aboutlicenseviolations

---
What goes around comes around. If it helps, hit it with Karma 🙂
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...