<?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 Broken Pipe issues when adding new data source to Splunk from GUI in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Broken-Pipe-issues-when-adding-new-data-source-to-Splunk-from/m-p/156431#M31714</link>
    <description>&lt;P&gt;Customer reports that when trying to upload a local file to Splunk (Add Data -&amp;gt; From files and directories -&amp;gt; Upload and index a file -&amp;gt; Save), Splunk reports "Success! Your data is being indexed to Splunk". However, the uploaded file is not available at the selected index. At the server side, i see this log entry at the second when clicking "Save": &lt;/P&gt;

&lt;P&gt;splunkd.log&lt;BR /&gt;
WARN HttpListener - Socket error from 127.0.0.1 while accessing /services/receivers/stream: Broken pipe &lt;/P&gt;</description>
    <pubDate>Wed, 19 Feb 2014 09:09:02 GMT</pubDate>
    <dc:creator>dshakespeare_sp</dc:creator>
    <dc:date>2014-02-19T09:09:02Z</dc:date>
    <item>
      <title>Broken Pipe issues when adding new data source to Splunk from GUI</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Broken-Pipe-issues-when-adding-new-data-source-to-Splunk-from/m-p/156431#M31714</link>
      <description>&lt;P&gt;Customer reports that when trying to upload a local file to Splunk (Add Data -&amp;gt; From files and directories -&amp;gt; Upload and index a file -&amp;gt; Save), Splunk reports "Success! Your data is being indexed to Splunk". However, the uploaded file is not available at the selected index. At the server side, i see this log entry at the second when clicking "Save": &lt;/P&gt;

&lt;P&gt;splunkd.log&lt;BR /&gt;
WARN HttpListener - Socket error from 127.0.0.1 while accessing /services/receivers/stream: Broken pipe &lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2014 09:09:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Broken-Pipe-issues-when-adding-new-data-source-to-Splunk-from/m-p/156431#M31714</guid>
      <dc:creator>dshakespeare_sp</dc:creator>
      <dc:date>2014-02-19T09:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: Broken Pipe issues when adding new data source to Splunk from GUI</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Broken-Pipe-issues-when-adding-new-data-source-to-Splunk-from/m-p/156432#M31715</link>
      <description>&lt;P&gt;The issue was seen for non admin users that tried to add data to Splunk. By adding the "edit_tcp" capability to the users role, the error disappeared and uploaded data gets indexed. &lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2014 09:24:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Broken-Pipe-issues-when-adding-new-data-source-to-Splunk-from/m-p/156432#M31715</guid>
      <dc:creator>dshakespeare_sp</dc:creator>
      <dc:date>2014-02-19T09:24:38Z</dc:date>
    </item>
  </channel>
</rss>

