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!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...