<?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: ES Security App: Multi-line header is missing matching quotation, or could not parse CSV header in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284327#M2451</link>
    <description>&lt;P&gt;This is a bug with outputlookup.  When no results are found it overwrites the csv with nothing, which in turns overwrites the header of the csv.  This is being addressed.&lt;/P&gt;

&lt;P&gt;To eliminate this spam&lt;/P&gt;

&lt;P&gt;cd /opt/splunk/etc/&lt;BR /&gt;
create a file called log-local.cfg&lt;BR /&gt;
add this line:&lt;BR /&gt;
category.SearchResults=ERROR&lt;/P&gt;

&lt;P&gt;I would restart splunk to be safe, but this will eliminate those Spam messages.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Apr 2016 19:58:46 GMT</pubDate>
    <dc:creator>jwelch_splunk</dc:creator>
    <dc:date>2016-04-19T19:58:46Z</dc:date>
    <item>
      <title>ES Security App: Multi-line header is missing matching quotation, or could not parse CSV header</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284323#M2447</link>
      <description>&lt;P&gt;I have recurring warnings in splunkd logs with &lt;BR /&gt;
multi-line header is missing matching quotation, or could not parse CSV header&lt;BR /&gt;
Though i have replaced the headers with default value of .csv file.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 09:50:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284323#M2447</guid>
      <dc:creator>neelamsantosh</dc:creator>
      <dc:date>2016-04-06T09:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: ES Security App: Multi-line header is missing matching quotation, or could not parse CSV header</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284324#M2448</link>
      <description>&lt;P&gt;Do this:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/306569/corrupt-csv-header-how-to-find-the-corrupted-csv.html#answer-306586"&gt;https://answers.splunk.com/answers/306569/corrupt-csv-header-how-to-find-the-corrupted-csv.html#answer-306586&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 13:33:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284324#M2448</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-04-06T13:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: ES Security App: Multi-line header is missing matching quotation, or could not parse CSV header</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284325#M2449</link>
      <description>&lt;P&gt;Thanks Woodcock,&lt;BR /&gt;
That didn't help me.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 07:57:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284325#M2449</guid>
      <dc:creator>neelamsantosh</dc:creator>
      <dc:date>2016-04-18T07:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: ES Security App: Multi-line header is missing matching quotation, or could not parse CSV header</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284326#M2450</link>
      <description>&lt;P&gt;This is a bug in ES/Core where the lookup searches/scripts that output the various threat intel lookups do not output headers if there are no results for the lookup in question. The other option is that these messages should only occur at DEBUG, not WARN. I believe it is listed as SPL-114701.&lt;/P&gt;

&lt;P&gt;Edit: Some additional info. You can replace the empty versions of these files with their .default counterparts, but be aware that there is a good chance that they will be replaced with empty versions again on the next run.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 16:16:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284326#M2450</guid>
      <dc:creator>dshpritz</dc:creator>
      <dc:date>2016-04-18T16:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: ES Security App: Multi-line header is missing matching quotation, or could not parse CSV header</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284327#M2451</link>
      <description>&lt;P&gt;This is a bug with outputlookup.  When no results are found it overwrites the csv with nothing, which in turns overwrites the header of the csv.  This is being addressed.&lt;/P&gt;

&lt;P&gt;To eliminate this spam&lt;/P&gt;

&lt;P&gt;cd /opt/splunk/etc/&lt;BR /&gt;
create a file called log-local.cfg&lt;BR /&gt;
add this line:&lt;BR /&gt;
category.SearchResults=ERROR&lt;/P&gt;

&lt;P&gt;I would restart splunk to be safe, but this will eliminate those Spam messages.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2016 19:58:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Security-App-Multi-line-header-is-missing-matching-quotation/m-p/284327#M2451</guid>
      <dc:creator>jwelch_splunk</dc:creator>
      <dc:date>2016-04-19T19:58:46Z</dc:date>
    </item>
  </channel>
</rss>

