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.
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
Thanks for investigating and giving assistance for a less-intrusive workaround for this issue.
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