Getting Data In

Broken Pipe issues when adding new data source to Splunk from GUI

dshakespeare_sp
Splunk Employee
Splunk Employee

Customer reports that when trying to upload a local file to Splunk (Add Data -> From files and directories -> Upload and index a file -> 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":

splunkd.log
WARN HttpListener - Socket error from 127.0.0.1 while accessing /services/receivers/stream: Broken pipe

Tags (1)
1 Solution

dshakespeare_sp
Splunk Employee
Splunk Employee

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.

View solution in original post

dshakespeare_sp
Splunk Employee
Splunk Employee

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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...