<?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: &amp;quot;Cannot parse into key-value pair&amp;quot; error after upgrading to 4.1.4 in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/quot-Cannot-parse-into-key-value-pair-quot-error-after-upgrading/m-p/17759#M175</link>
    <description>&lt;P&gt;This problem is caused by a bogus configuration file entry.  To prevent this error message, open up your &lt;CODE&gt;$SPLUNK_HOME/etc/apps/search/default/inputs.conf&lt;/CODE&gt; config file, which could contain the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# Copyright (C) 2005-2010 Splunk Inc.  All Rights Reserved.  Version 4.1.4
This file intentionally left empty. Please do not delete it.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Simply remove or comment out (add a "#") to the second line and the error message will go away.  &lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;Example of a fixed file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# Copyright (C) 2005-2010 Splunk Inc.  All Rights Reserved.  Version 4.1.4
# This file intentionally left empty. Please do not delete it.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 21 Jul 2010 03:41:18 GMT</pubDate>
    <dc:creator>Lowell</dc:creator>
    <dc:date>2010-07-21T03:41:18Z</dc:date>
    <item>
      <title>"Cannot parse into key-value pair" error after upgrading to 4.1.4</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/quot-Cannot-parse-into-key-value-pair-quot-error-after-upgrading/m-p/17758#M174</link>
      <description>&lt;P&gt;I just upgraded one of my splunk forwarders to version 4.1.4 and now I'm seeing the following error message in my internal logs:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;&lt;CODE&gt;WARN  IniFile - C:\Program Files\Splunk\etc\apps\search\default\inputs.conf, line: 2: Cannot parse into key-value pair: This file intentionally left empty. Please do not delete it&lt;/CODE&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Wed, 21 Jul 2010 03:37:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/quot-Cannot-parse-into-key-value-pair-quot-error-after-upgrading/m-p/17758#M174</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-07-21T03:37:42Z</dc:date>
    </item>
    <item>
      <title>Re: "Cannot parse into key-value pair" error after upgrading to 4.1.4</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/quot-Cannot-parse-into-key-value-pair-quot-error-after-upgrading/m-p/17759#M175</link>
      <description>&lt;P&gt;This problem is caused by a bogus configuration file entry.  To prevent this error message, open up your &lt;CODE&gt;$SPLUNK_HOME/etc/apps/search/default/inputs.conf&lt;/CODE&gt; config file, which could contain the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# Copyright (C) 2005-2010 Splunk Inc.  All Rights Reserved.  Version 4.1.4
This file intentionally left empty. Please do not delete it.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Simply remove or comment out (add a "#") to the second line and the error message will go away.  &lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;Example of a fixed file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# Copyright (C) 2005-2010 Splunk Inc.  All Rights Reserved.  Version 4.1.4
# This file intentionally left empty. Please do not delete it.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 21 Jul 2010 03:41:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/quot-Cannot-parse-into-key-value-pair-quot-error-after-upgrading/m-p/17759#M175</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-07-21T03:41:18Z</dc:date>
    </item>
  </channel>
</rss>

