<?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 not responding in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28400#M320</link>
    <description>&lt;P&gt;How about ...are the rights on the directories as expected after the restore? I had similar messages after installing the first heavy forwarder. I needed to replace several ACLs on the windows server to get it working.&lt;/P&gt;</description>
    <pubDate>Fri, 18 Dec 2015 15:50:00 GMT</pubDate>
    <dc:creator>peewee42</dc:creator>
    <dc:date>2015-12-18T15:50:00Z</dc:date>
    <item>
      <title>splunkd not responding</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28398#M318</link>
      <description>&lt;P&gt;I have a indexer, that crashed and I restored.&lt;/P&gt;

&lt;P&gt;I can start splunkd and splunkweb services, but cannot use the CLI, or connect with the search-head, and splunkweb login fails (the version displayed is UNKNOWN)&lt;BR /&gt;
But splunkd is indexing, and my firewalls are open.&lt;/P&gt;

&lt;P&gt;I saw some errors in splunkd.log after a restart.&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
08-07-2012 12:19:02.807 -0700 ERROR SSLCommon - Can't read key file D:\Program Files\Splunk\etc\auth\server.pem errno=151429224 error:0906A068:PEM routines:PEM_do_header:bad password read.&lt;BR /&gt;
08-07-2012 12:19:02.807 -0700 ERROR ServerConfig - Couldn't initialize SSL Context for HTTPClient in ServerConfig&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28398#M318</guid>
      <dc:creator>mataharry</dc:creator>
      <dc:date>2020-09-28T12:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd not responding</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28399#M319</link>
      <description>&lt;P&gt;Did you restored the configuration from another server ?&lt;/P&gt;

&lt;P&gt;The error means that the ssl certificated used for splunkd (port 8089) is not working.&lt;BR /&gt;
check in $SPLUNK_HOME/etc/system/local/server.conf and web.conf&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Verify that the ssl certificate exists&lt;/LI&gt;
&lt;LI&gt;that the password is the good one.&lt;/LI&gt;
&lt;LI&gt;that the $SPLUNK_HOME/etc/auth/splunk.secret has not be modified&lt;/LI&gt;
&lt;LI&gt;regenerated the ssl password, by typing the password in clear in $SPLUNK_HOME/etc/system/local/server.conf
&lt;PRE&gt;
[sslConfig]
sslKeysfilePassword = password
&lt;/PRE&gt;
and restart to apply
if you are using the default ssl, shipped with splunk, simply comment the password line and restart it will encrypt the one from the default settings.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 07 Aug 2012 23:42:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28399#M319</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-08-07T23:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: splunkd not responding</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28400#M320</link>
      <description>&lt;P&gt;How about ...are the rights on the directories as expected after the restore? I had similar messages after installing the first heavy forwarder. I needed to replace several ACLs on the windows server to get it working.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Dec 2015 15:50:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunkd-not-responding/m-p/28400#M320</guid>
      <dc:creator>peewee42</dc:creator>
      <dc:date>2015-12-18T15:50:00Z</dc:date>
    </item>
  </channel>
</rss>

