<?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: How to resolve Indexer ERROR TcpInputConfig - SSL context not found. Will not open splunk to splunk (SSL) IPv4 port in Security</title>
    <link>https://community.splunk.com/t5/Security/How-to-resolve-Indexer-ERROR-TcpInputConfig-SSL-context-not/m-p/616602#M16406</link>
    <description>&lt;P&gt;The solution was to request new&amp;nbsp;cert in company's CA,&amp;nbsp;generate new private key and new certificate chains&lt;/P&gt;</description>
    <pubDate>Tue, 11 Oct 2022 07:04:21 GMT</pubDate>
    <dc:creator>justynap_ldz</dc:creator>
    <dc:date>2022-10-11T07:04:21Z</dc:date>
    <item>
      <title>How to resolve Indexer ERROR TcpInputConfig - SSL context not found? (Won't open Splunk to Splunk (SSL) IPv4 port 9997)</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Indexer-ERROR-TcpInputConfig-SSL-context-not/m-p/614966#M16385</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;We keep getting the errors from one of our indexers (there are 3 in the cluster, only one is affected):&lt;BR /&gt;&lt;EM&gt;&lt;SPAN class=""&gt;ERROR&lt;/SPAN&gt; &lt;SPAN class=""&gt;TcpInputConfig&lt;/SPAN&gt; [&lt;SPAN class=""&gt;60483&lt;/SPAN&gt; &lt;SPAN class=""&gt;TcpListener&lt;/SPAN&gt;] &lt;SPAN class=""&gt;-&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;SSL&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;context&lt;/SPAN&gt; &lt;SPAN class=""&gt;not&lt;/SPAN&gt; &lt;SPAN class=""&gt;found.&lt;/SPAN&gt; &lt;SPAN class=""&gt;Will&lt;/SPAN&gt; &lt;SPAN class=""&gt;not&lt;/SPAN&gt; &lt;SPAN class=""&gt;open&lt;/SPAN&gt; &lt;SPAN class=""&gt;splunk&lt;/SPAN&gt; &lt;SPAN class=""&gt;to&lt;/SPAN&gt; &lt;SPAN class=""&gt;splunk&lt;/SPAN&gt; (&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;SSL&lt;/SPAN&gt;&lt;/SPAN&gt;) &lt;SPAN class=""&gt;IPv4&lt;/SPAN&gt; &lt;SPAN class=""&gt;port&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;9997&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;All indexers have the same SSL config:&lt;/P&gt;
&lt;P&gt;/opt/splunk/etc/system/local/inputs.conf&lt;BR /&gt;[default]&lt;BR /&gt;host = z1234&lt;/P&gt;
&lt;P&gt;[splunktcp-ssl:9997]&lt;BR /&gt;disabled = 0&lt;BR /&gt;connection_host = ip&lt;/P&gt;
&lt;P&gt;[SSL]&lt;BR /&gt;serverCert = /opt/splunk/etc/auth/z1234_server.pem&lt;BR /&gt;sslPassword = &amp;lt;password&amp;gt;&lt;BR /&gt;requireClientCert = false&lt;BR /&gt;sslVersions = tls1.2&lt;/P&gt;
&lt;P&gt;We have just found additional input.conf on all indexers: in&lt;BR /&gt;/opt/splunk/etc/apps/search/local/inputs.conf&lt;BR /&gt;[splunktcp://9997]&lt;BR /&gt;connection_host = ip&lt;BR /&gt;&lt;BR /&gt;We deleted this config on all indexers as this is no longer valid and shouldn't be active.&lt;BR /&gt;Unfortunately, after splunk restart port 9997 is no longer opened on z1234 host. On other two hosts it is still opened...weird&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any idea what else to check/do to troubleshoot?&lt;BR /&gt;Your help will be much appreciated!&lt;/P&gt;
&lt;P&gt;Greetings,&lt;BR /&gt;Justyna&lt;/P&gt;</description>
      <pubDate>Tue, 11 Oct 2022 13:11:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Indexer-ERROR-TcpInputConfig-SSL-context-not/m-p/614966#M16385</guid>
      <dc:creator>justynap_ldz</dc:creator>
      <dc:date>2022-10-11T13:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve Indexer ERROR TcpInputConfig - SSL context not found. Will not open splunk to splunk (SSL) IPv4 port</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Indexer-ERROR-TcpInputConfig-SSL-context-not/m-p/616602#M16406</link>
      <description>&lt;P&gt;The solution was to request new&amp;nbsp;cert in company's CA,&amp;nbsp;generate new private key and new certificate chains&lt;/P&gt;</description>
      <pubDate>Tue, 11 Oct 2022 07:04:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Indexer-ERROR-TcpInputConfig-SSL-context-not/m-p/616602#M16406</guid>
      <dc:creator>justynap_ldz</dc:creator>
      <dc:date>2022-10-11T07:04:21Z</dc:date>
    </item>
  </channel>
</rss>

