<?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: splunkd crash in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171679#M1883</link>
    <description>&lt;P&gt;There is no crash log, and the only resent error I can find in splunkd.log is&lt;/P&gt;

&lt;P&gt;12-04-2013 19:00:36.639 +0100 ERROR ProcessRunner - helper process seems to have died (child killed by signal 9: Killed)!&lt;/P&gt;

&lt;P&gt;Other that that there is only the WARN's that seems a bit worrying. &lt;/P&gt;

&lt;P&gt;best,&lt;BR /&gt;
Preben&lt;/P&gt;</description>
    <pubDate>Mon, 09 Dec 2013 12:12:28 GMT</pubDate>
    <dc:creator>preben12</dc:creator>
    <dc:date>2013-12-09T12:12:28Z</dc:date>
    <item>
      <title>splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171677#M1881</link>
      <description>&lt;P&gt;Splunkd has crashed a couple of times now.&lt;BR /&gt;
The only thing I see in splunkd.log is some log WARNS &lt;BR /&gt;
eg.&lt;/P&gt;

&lt;P&gt;12-09-2013 07:55:09.879 +0100 WARN  HttpListener - Socket error from 10.101.11.1&lt;BR /&gt;
02 while accessing /services/data/indexes: Broken pipe&lt;/P&gt;

&lt;P&gt;and a lot of -&amp;gt;&lt;BR /&gt;
12-09-2013 08:03:17.651 +0100 WARN  HttpListener - HTTP active connections down to 330, unthrottling&lt;/P&gt;

&lt;P&gt;Is there some configuration that needs to be set different - or ??&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2013 07:18:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171677#M1881</guid>
      <dc:creator>preben12</dc:creator>
      <dc:date>2013-12-09T07:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171678#M1882</link>
      <description>&lt;P&gt;have you checked the crash logs, and the splunkd_stderr.log? They may reveal more info.&lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2013 11:48:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171678#M1882</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-12-09T11:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171679#M1883</link>
      <description>&lt;P&gt;There is no crash log, and the only resent error I can find in splunkd.log is&lt;/P&gt;

&lt;P&gt;12-04-2013 19:00:36.639 +0100 ERROR ProcessRunner - helper process seems to have died (child killed by signal 9: Killed)!&lt;/P&gt;

&lt;P&gt;Other that that there is only the WARN's that seems a bit worrying. &lt;/P&gt;

&lt;P&gt;best,&lt;BR /&gt;
Preben&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2013 12:12:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171679#M1883</guid>
      <dc:creator>preben12</dc:creator>
      <dc:date>2013-12-09T12:12:28Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171680#M1884</link>
      <description>&lt;P&gt;Install S.O.S. Then monitor the buggy system for RAM usage. Certain Operating Systems just kill the process when they run out of Memory, and since Splunk "didn't do it", no event is written.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2013 12:22:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171680#M1884</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2013-12-09T12:22:34Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171681#M1885</link>
      <description>&lt;P&gt;I tripled the ram on the box - lets see if this helps splunkd from being killed by linux. &lt;/P&gt;

&lt;P&gt;I still see the warn logs&lt;BR /&gt;
12-09-2013 14:44:59.219 +0100 WARN  HttpListener - HTTP active connections down to 330, unthrottling&lt;/P&gt;

&lt;P&gt;Any hints on the reason for this ??&lt;/P&gt;

&lt;P&gt;Best,&lt;BR /&gt;
Preben&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2013 14:02:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171681#M1885</guid>
      <dc:creator>preben12</dc:creator>
      <dc:date>2013-12-09T14:02:02Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171682#M1886</link>
      <description>&lt;P&gt;Instead of throwing resources at it do as the respondent suggested - use some system level diagnostic tools to find the cause.  You don't mention operating system distribution or release number.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2013 18:36:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171682#M1886</guid>
      <dc:creator>grijhwani</dc:creator>
      <dc:date>2013-12-09T18:36:21Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd crash</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171683#M1887</link>
      <description>&lt;P&gt;Are these relevant to you?&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/105292/what-is-the-cause-of-these-socket-errors-reported-in-splunkd-log-since-upgrading-to-6-0.html"&gt;https://answers.splunk.com/answers/105292/what-is-the-cause-of-these-socket-errors-reported-in-splunkd-log-since-upgrading-to-6-0.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/123473/broken-pipe-issues-when-adding-new-data-source-to-splunk-from-gui.html"&gt;https://answers.splunk.com/answers/123473/broken-pipe-issues-when-adding-new-data-source-to-splunk-from-gui.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 14:14:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-crash/m-p/171683#M1887</guid>
      <dc:creator>bohanlon_splunk</dc:creator>
      <dc:date>2016-01-26T14:14:32Z</dc:date>
    </item>
  </channel>
</rss>

