<?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 stop responding -&amp;gt; ERROR AdminManager in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148188#M1714</link>
    <description>&lt;P&gt;We are still being affected by this issue. We have captured pstacks. Splunk tech support identified a dead lock bug in openssl. However, the issue is not fixed in Splunk 6.1.2. Are you still being affected by this issue?&lt;/P&gt;</description>
    <pubDate>Fri, 26 Sep 2014 13:18:30 GMT</pubDate>
    <dc:creator>lpolo</dc:creator>
    <dc:date>2014-09-26T13:18:30Z</dc:date>
    <item>
      <title>splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148183#M1709</link>
      <description>&lt;P&gt;Splunkd stop responding after the  event presented below.&lt;/P&gt;

&lt;P&gt;Splunk Tech. Support filed a bug against Splunk Enterprise version 6.0.1.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;02-12-2014 13:59:01.768 +0000 ERROR AdminManager - Stack trace from python handler:\nTraceback (most recent call last):\n  File "/opt/splunk/lib/python2.7/site-packages/splunk/admin.py", line 70, in init\n    hand.execute(info)\n  File "/opt/splunk/lib/python2.7/site-packages/splunk/admin.py", line 527, in execute\n    if self.requestedAction == ACTION_LIST:     self.handleList(confInfo)\n  File "/opt/splunk/etc/system/bin/DataModelAccelerationHandler.py", line 20, in handleList\n    sc_rest.BaseRestHandler.handleList(self, confInfo)\n  File "/opt/splunk/etc/system/bin/sc_rest.py", line 74, in handleList\n    ent = self.all()\n  File "/opt/splunk/etc/system/bin/sc_rest.py", line 221, in all\n    offset=self.posOffset)\n  File "/opt/splunk/lib/python2.7/site-packages/splunk/entity.py", line 129, in getEntities\n    atomFeed = _getEntitiesAtomFeed(entityPath, namespace, owner, search, count, offset, sort_key, sort_dir, sessionKey, uri, hostPath, **kwargs)\n  File "/opt/splunk/lib/python2.7/site-packages/splunk/entity.py", line 222, in _getEntitiesAtomFeed\n    serverResponse, serverContent = rest.simpleRequest(uri, getargs=kwargs, sessionKey=sessionKey, raiseAllErrors=True)\n  File "/opt/splunk/lib/python2.7/site-packages/splunk/rest/__init__.py", line 469, in simpleRequest\n    raise splunk.SplunkdConnectionException, 'Error connecting to %s: %s' % (path, str(e))\nSplunkdConnectionException: Splunkd daemon is not responding: ('Error connecting to /servicesNS/-/-/data/models: _ssl.c:506: The handshake operation timed out',)\n
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This issue was identified as deadlock bug in openssl. &lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2014 16:39:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148183#M1709</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2014-02-12T16:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148184#M1710</link>
      <description>&lt;P&gt;Anything result from this? I'm seeing the same issue.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2014 18:09:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148184#M1710</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2014-03-05T18:09:56Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148185#M1711</link>
      <description>&lt;P&gt;I have sent 2 diags to Splunk Tech support. &lt;BR /&gt;
We have not received any work around or fix yet. I will update the notes once I have more information.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2014 21:30:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148185#M1711</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2014-03-05T21:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148186#M1712</link>
      <description>&lt;P&gt;I increased the ulimit to 65536. Let's see how it behaves.  &lt;/P&gt;

&lt;P&gt;[host]# ulimit -n&lt;BR /&gt;
65536&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2014 19:59:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148186#M1712</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2014-03-07T19:59:54Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148187#M1713</link>
      <description>&lt;P&gt;I had a similar problem when I tried to use SplunkDBConnect (dbx) app, i had similar errors (which were actually a missing mysql driver problem) and the jbridge was hanging all the time.&lt;/P&gt;

&lt;P&gt;If you have DB inputs, check that you have the correct driver for DB engine:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/Installdrivers"&gt;http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/Installdrivers&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also, in java.conf for dbx app you might want to add the bridge stanza:&lt;BR /&gt;
[bridge]&lt;BR /&gt;
addr = 127.0.0.1&lt;BR /&gt;
port = XXX&lt;BR /&gt;
threads = 10&lt;/P&gt;

&lt;P&gt;This worked for me!&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2014 16:27:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148187#M1713</guid>
      <dc:creator>alexsayegh</dc:creator>
      <dc:date>2014-03-13T16:27:15Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148188#M1714</link>
      <description>&lt;P&gt;We are still being affected by this issue. We have captured pstacks. Splunk tech support identified a dead lock bug in openssl. However, the issue is not fixed in Splunk 6.1.2. Are you still being affected by this issue?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2014 13:18:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148188#M1714</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2014-09-26T13:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148189#M1715</link>
      <description>&lt;P&gt;Our problem is that splunkd stop responding due to a deadlock bug. Therefore, we are forced to restart the splunk service.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2014 13:20:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148189#M1715</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2014-09-26T13:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd stop responding -&gt; ERROR AdminManager</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148190#M1716</link>
      <description>&lt;P&gt;Issue address in release 6.1.4.&lt;BR /&gt;
vulnerability is :CVE-2014-1912&lt;/P&gt;</description>
      <pubDate>Wed, 01 Oct 2014 17:40:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-stop-responding-gt-ERROR-AdminManager/m-p/148190#M1716</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2014-10-01T17:40:17Z</dc:date>
    </item>
  </channel>
</rss>

