<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Getting a pool warning for a pool that has 100 meg allocated in a 2 gig license but LM shows only 23 MB indexed today! in Security</title>
    <link>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45786#M13854</link>
    <description>&lt;P&gt;We are sharing 100 megabytes of our 2 gigabytes daily license with another system that monitors an Apache web log. The volume of log data is typically around 25 MB a day. URL/manager/system/licensing page shows only 23 MB used by this pool so far today, but the warning we are getting on the yellow warning bar is:&lt;/P&gt;

&lt;P&gt;Daily indexing volume limit exceeded for 1 slaves. See License Manager for details.&lt;/P&gt;

&lt;P&gt;Clicking on that the message is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2 pool warnings reported by 1 indexer   Correct by midnight to avoid violation
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Drilling down, we see&lt;/P&gt;

&lt;P&gt;indexing quota exceeded for this pool, poolsz=104857600 bytes&lt;/P&gt;

&lt;P&gt;Why is that being generated? Had this four times last week. At midnight this will make a fifth violation. Previously the log file was many gigabytes, and based on splunkd.log was getting re-read, so those four I understand. But yesterday I rolled-out that log, and hup'd the Apache server creating the logs, so started with new log file at 0 bytes, now ~23 megs. followtail = 0 in inputs.conf. Any ideas what the heck is going on?&lt;/P&gt;</description>
    <pubDate>Tue, 28 Aug 2012 18:11:28 GMT</pubDate>
    <dc:creator>wrangler2x</dc:creator>
    <dc:date>2012-08-28T18:11:28Z</dc:date>
    <item>
      <title>Getting a pool warning for a pool that has 100 meg allocated in a 2 gig license but LM shows only 23 MB indexed today!</title>
      <link>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45786#M13854</link>
      <description>&lt;P&gt;We are sharing 100 megabytes of our 2 gigabytes daily license with another system that monitors an Apache web log. The volume of log data is typically around 25 MB a day. URL/manager/system/licensing page shows only 23 MB used by this pool so far today, but the warning we are getting on the yellow warning bar is:&lt;/P&gt;

&lt;P&gt;Daily indexing volume limit exceeded for 1 slaves. See License Manager for details.&lt;/P&gt;

&lt;P&gt;Clicking on that the message is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2 pool warnings reported by 1 indexer   Correct by midnight to avoid violation
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Drilling down, we see&lt;/P&gt;

&lt;P&gt;indexing quota exceeded for this pool, poolsz=104857600 bytes&lt;/P&gt;

&lt;P&gt;Why is that being generated? Had this four times last week. At midnight this will make a fifth violation. Previously the log file was many gigabytes, and based on splunkd.log was getting re-read, so those four I understand. But yesterday I rolled-out that log, and hup'd the Apache server creating the logs, so started with new log file at 0 bytes, now ~23 megs. followtail = 0 in inputs.conf. Any ideas what the heck is going on?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2012 18:11:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45786#M13854</guid>
      <dc:creator>wrangler2x</dc:creator>
      <dc:date>2012-08-28T18:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: Getting a pool warning for a pool that has 100 meg allocated in a 2 gig license but LM shows only 23 MB indexed today!</title>
      <link>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45787#M13855</link>
      <description>&lt;P&gt;Did you switch to a local Master License server at some point?&lt;/P&gt;

&lt;P&gt;I had something similar due to switching to a local local master and then back.&lt;/P&gt;

&lt;P&gt;To fix it, I had to switch back to local Master , get a reset key and then switched back to being a slave.&lt;/P&gt;

&lt;P&gt;Seems similar somehow ...&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2012 20:06:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45787#M13855</guid>
      <dc:creator>gryz</dc:creator>
      <dc:date>2012-08-28T20:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: Getting a pool warning for a pool that has 100 meg allocated in a 2 gig license but LM shows only 23 MB indexed today!</title>
      <link>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45788#M13856</link>
      <description>&lt;P&gt;I think I get what this is now. The 5 warnings must be the four warnings&lt;BR /&gt;
we saw yesterday, plus the one generated at midnight last night. So I think&lt;BR /&gt;
it is announcing not that this pool went over quota today, but that it has&lt;BR /&gt;
five times in the past.&lt;/P&gt;

&lt;P&gt;And the second message must be a confirmation that these 5 warnings&lt;BR /&gt;
places the pool in violation of the license.&lt;/P&gt;

&lt;P&gt;Can anyone confirm if this is what is going on?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2012 20:24:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45788#M13856</guid>
      <dc:creator>wrangler2x</dc:creator>
      <dc:date>2012-08-28T20:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: Getting a pool warning for a pool that has 100 meg allocated in a 2 gig license but LM shows only 23 MB indexed today!</title>
      <link>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45789#M13857</link>
      <description>&lt;P&gt;That is in fact what was going on.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2013 23:59:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Getting-a-pool-warning-for-a-pool-that-has-100-meg-allocated-in/m-p/45789#M13857</guid>
      <dc:creator>wrangler2x</dc:creator>
      <dc:date>2013-02-12T23:59:44Z</dc:date>
    </item>
  </channel>
</rss>

