Splunk Search

Splunk_TA_stream stops capture (Windows) - know issue STREAM-4301, STREAM-4409

gunzola
Path Finder

Hi

In  known issues this problem is listed (STREAM-4301, STREAM-4409 😞

https://docs.splunk.com/Documentation/StreamApp/7.2.0/ReleaseNotes/Knownissues

The proposed workaround is unclear:

Workaround:
Manually re-configure streams for the forwarder to resume or restart Splunk Forwarder service in Windows

 

My question. How do we manually reconfigure streams for the forwarder to resume. Hopefully, this is a workaround for an automated recovery from this error. 

0 Karma
1 Solution

jbarlow_splunk
Splunk Employee
Splunk Employee

bit late...but came across this as working on same scenario ...

When i reproduce the error...   can make changes to stream configs per https://docs.splunk.com/Documentation/StreamApp/7.3.0/User/ConfigureStreams

I just added/removed a field and it restarted the capture after the stream fwd detected the config change

View solution in original post

gunzola
Path Finder

Thanks for investigating and giving assistance for a less-intrusive workaround for this issue.

0 Karma

jbarlow_splunk
Splunk Employee
Splunk Employee

bit late...but came across this as working on same scenario ...

When i reproduce the error...   can make changes to stream configs per https://docs.splunk.com/Documentation/StreamApp/7.3.0/User/ConfigureStreams

I just added/removed a field and it restarted the capture after the stream fwd detected the config change

Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...