<?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: Why do I get &amp;quot;Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent&amp;quot;? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271724#M52184</link>
    <description>&lt;P&gt;&lt;CODE&gt;splunktcp-ssl&lt;/CODE&gt; and &lt;CODE&gt;tcp-ssl&lt;/CODE&gt; are two separate input stanza types. &lt;CODE&gt;splunktcp-ssl&lt;/CODE&gt; is intended for receiving data from Splunk forwarders and allows the key &lt;CODE&gt;connection_host&lt;/CODE&gt;. &lt;CODE&gt;tcp-ssl&lt;/CODE&gt; is intended for encrypted communication coming in unparsed (e.g. from 3rd party systems) and does not allow the &lt;CODE&gt;connection_host&lt;/CODE&gt; key.&lt;/P&gt;

&lt;P&gt;Reference: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/Admin/Inputsconf"&gt;Inputs.conf spec&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Dec 2015 21:56:47 GMT</pubDate>
    <dc:creator>nnmiller</dc:creator>
    <dc:date>2015-12-28T21:56:47Z</dc:date>
    <item>
      <title>Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271720#M52180</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;Our &lt;CODE&gt;/opt/splunk/etc/apps/search/local/inputs.conf&lt;/CODE&gt; file on our forwarder contains:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp-ssl://:1470]
connection_host=dns
sourcetype=apm_log
index=security_logs
queueSize=5MB
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When starting the forwarder, I get:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;checking for conf file problems:...
invalid key in stanza [tcp-ssl://:1470] in /opt/splunk/etc/apps/search/local/inputs.conf ...connection_host=dns
your indexes and inputs are not internally consistent.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;btool output offers no additional information.&lt;/P&gt;

&lt;P&gt;Can anyone offer advice?&lt;/P&gt;

&lt;P&gt;Thank you so much.&lt;/P&gt;

&lt;P&gt;msantich&lt;/P&gt;</description>
      <pubDate>Mon, 14 Dec 2015 20:53:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271720#M52180</guid>
      <dc:creator>msantich</dc:creator>
      <dc:date>2015-12-14T20:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271721#M52181</link>
      <description>&lt;P&gt;Are you sure that your stanza syntax is correct? As I read inputs.conf.spec, I would think that it should be&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp-ssl:1470]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Second, are you sure that there are no special characters, etc. in the &lt;CODE&gt;connection_host=dns&lt;/CODE&gt; line? Sometimes I find that people cut-and-paste and unusual characters end up in configuration files. Splunk won't like that.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2015 00:26:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271721#M52181</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2015-12-15T00:26:18Z</dc:date>
    </item>
    <item>
      <title>Re: Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271722#M52182</link>
      <description>&lt;P&gt;Thanks for the input Iguinn.&lt;/P&gt;

&lt;P&gt;I tried each of your suggestions and I still get the same error on startup.&lt;BR /&gt;
I changed the name of the stanza to tcp-ssl:1470 - still get the same error on startup.&lt;BR /&gt;
I retyped the key-value pair "connection_host=dns" to ensure no special characters and I still get the error on startup.&lt;/P&gt;

&lt;P&gt;thanks for your interest in my problem&lt;/P&gt;

&lt;P&gt;msantich&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2015 16:20:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271722#M52182</guid>
      <dc:creator>msantich</dc:creator>
      <dc:date>2015-12-15T16:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271723#M52183</link>
      <description>&lt;P&gt;I am a bit stumped. Perhaps Splunk Support could help?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2015 22:53:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271723#M52183</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2015-12-15T22:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271724#M52184</link>
      <description>&lt;P&gt;&lt;CODE&gt;splunktcp-ssl&lt;/CODE&gt; and &lt;CODE&gt;tcp-ssl&lt;/CODE&gt; are two separate input stanza types. &lt;CODE&gt;splunktcp-ssl&lt;/CODE&gt; is intended for receiving data from Splunk forwarders and allows the key &lt;CODE&gt;connection_host&lt;/CODE&gt;. &lt;CODE&gt;tcp-ssl&lt;/CODE&gt; is intended for encrypted communication coming in unparsed (e.g. from 3rd party systems) and does not allow the &lt;CODE&gt;connection_host&lt;/CODE&gt; key.&lt;/P&gt;

&lt;P&gt;Reference: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/Admin/Inputsconf"&gt;Inputs.conf spec&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Dec 2015 21:56:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271724#M52184</guid>
      <dc:creator>nnmiller</dc:creator>
      <dc:date>2015-12-28T21:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271725#M52185</link>
      <description>&lt;P&gt;I removed connection_host for tcp-ssl and Splunk no longer complained.&lt;/P&gt;</description>
      <pubDate>Sat, 20 Aug 2016 18:30:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271725#M52185</guid>
      <dc:creator>TonyLeeVT</dc:creator>
      <dc:date>2016-08-20T18:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Why do I get "Invalid key in stanza [tcp-ssl://:1470] ... connection_host=dns your indexes and inputs are not internally consistent"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271726#M52186</link>
      <description>&lt;P&gt;Thank you all.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2016 18:43:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-I-get-quot-Invalid-key-in-stanza-tcp-ssl-1470-connection/m-p/271726#M52186</guid>
      <dc:creator>msantich</dc:creator>
      <dc:date>2016-08-29T18:43:59Z</dc:date>
    </item>
  </channel>
</rss>

