<?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 Re: Splunk exhausting memory crashing linux server in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150375#M30566</link>
    <description>&lt;P&gt;I am having the same problem.  My indexers are on VMware, ran fine on spunk 5. I am up to the latest rpm.&lt;/P&gt;

&lt;P&gt;logindex2 ~]# uname -a&lt;BR /&gt;
Linux ifw9bct-logindex2.fws.doi.net 2.6.18-371.8.1.el5 #1 SMP Thu Apr 24 18:19:36 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux&lt;BR /&gt;
logindex2 ~]# cat /etc/redhat-release &lt;BR /&gt;
CentOS release 5.10 (Final)&lt;BR /&gt;
logindex2 ~]# splunk --version&lt;BR /&gt;
Splunk 6.1.1 (build 207789)&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 16:40:23 GMT</pubDate>
    <dc:creator>rickblair</dc:creator>
    <dc:date>2020-09-28T16:40:23Z</dc:date>
    <item>
      <title>Splunk exhausting memory crashing linux server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150372#M30563</link>
      <description>&lt;P&gt;I have some RHEL servers that are my splunk indexers that have been crashing lately.  They all get into the same Out Of Memory state and the box is effectively hung.&lt;/P&gt;

&lt;P&gt;There's nothing of note in /var/log and the only thing these boxes do is  splunk indexing. &lt;/P&gt;

&lt;P&gt;After rebooting, it comes up just fine, and has ample free memory:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[root@REXSPLUNK-CH2-03 log]# free -tm
             total       used       free     shared    buffers     cached
Mem:         32183       4183      27999          0        241       3171
-/+ buffers/cache:        770      31412
Swap:         4095          0       4095
Total:       36279       4183      32095
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I could look into making swap bigger, but considering there's only 4Gb of 32Gb used of physical RAM, I don't think that would help. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; uname -a
Linux REXSPLUNK-CH2-03.sys.comcast.net 2.6.18-238.19.1.el5 #1 SMP Sun Jul 10 08:43:41 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
 cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 5.6 (Tikanga)
 /opt/splunk/bin/splunk --version
Splunk 6.0.1 (build 189883)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We're going to install the latest splunk today to see if there is any improvement.  Just wondering how we could troubleshoot this further.  Any ideas where to start?&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2014 12:26:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150372#M30563</guid>
      <dc:creator>richard_whiffen</dc:creator>
      <dc:date>2014-05-02T12:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk exhausting memory crashing linux server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150373#M30564</link>
      <description>&lt;P&gt;Thanks for your reply to my question - "could this be ulimit?" I pulled my answer, in hopes that an unanswered question will attract more views and a real answer!&lt;/P&gt;</description>
      <pubDate>Sat, 03 May 2014 09:28:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150373#M30564</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-05-03T09:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk exhausting memory crashing linux server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150374#M30565</link>
      <description>&lt;P&gt;Not an answer, more like information....are you aware of this &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.3/ReleaseNotes/SplunkandTHP"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.3/ReleaseNotes/SplunkandTHP&lt;/A&gt; known issue within RHEL and other *nix&lt;/P&gt;</description>
      <pubDate>Sat, 03 May 2014 09:35:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150374#M30565</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2014-05-03T09:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk exhausting memory crashing linux server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150375#M30566</link>
      <description>&lt;P&gt;I am having the same problem.  My indexers are on VMware, ran fine on spunk 5. I am up to the latest rpm.&lt;/P&gt;

&lt;P&gt;logindex2 ~]# uname -a&lt;BR /&gt;
Linux ifw9bct-logindex2.fws.doi.net 2.6.18-371.8.1.el5 #1 SMP Thu Apr 24 18:19:36 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux&lt;BR /&gt;
logindex2 ~]# cat /etc/redhat-release &lt;BR /&gt;
CentOS release 5.10 (Final)&lt;BR /&gt;
logindex2 ~]# splunk --version&lt;BR /&gt;
Splunk 6.1.1 (build 207789)&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:40:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150375#M30566</guid>
      <dc:creator>rickblair</dc:creator>
      <dc:date>2020-09-28T16:40:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk exhausting memory crashing linux server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150376#M30567</link>
      <description>&lt;P&gt;This is the article from Oracle that explains how to manage the OOM. While you can tell it to be "nicer" to Splunk, even they don't recommend turning it off.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html"&gt;http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;We are going to disable THP too and see if it helps with our issue (seems to be the same).  You should manually look at the /var/log/messages to confirm if OOM is killing splunkd.  For some reason we we not seeing the messages in Splunk, but they were in /var/log/messages.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Dec 2014 06:13:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150376#M30567</guid>
      <dc:creator>rsolutions</dc:creator>
      <dc:date>2014-12-31T06:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk exhausting memory crashing linux server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150377#M30568</link>
      <description>&lt;P&gt;I have the same problem. Rhel 5.8 - 32GB ram. Memory is consumed and swap too. Seeing "sar -r"  after hard reboot reveals the same issue. My sar config pulls data each minute. No cpu issue, no disk io issue (local disk raid 10). &lt;BR /&gt;
Splunk v6.0.5. It only happens to me after a couple weeks of keeping Splunkd running. Seems like a memory leak to me. Splunk support wants a diag but it's pointless right now. The system is still healthy. All I see at the time was lots of search requests from search head to indexer. &lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2015 04:36:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-exhausting-memory-crashing-linux-server/m-p/150377#M30568</guid>
      <dc:creator>BP9906</dc:creator>
      <dc:date>2015-02-05T04:36:11Z</dc:date>
    </item>
  </channel>
</rss>

