Known issues
Version 8.0.2 of Splunk Stream contains the following known issues.
If no issues appear below, no issues have yet been reported:
Date filed | Issue number | Description |
---|---|---|
2022-05-24 | STREAM-5170 | SplunkStream process goes down when capturing certain communication data |
2021-08-05 | STREAM-4900 | Un-installing Splunk TA Stream from Windows Universal Forwarder using Deployment Server results in files not getting removed |
2020-01-06 | STREAM-4301, STREAM-4409 | Windows: Capture stops with "pcap_loop returned error code -1 read error: PacketReceivePacket failed; network capture stopped" and isn't restarted Workaround: Re-configure one of the streams assigned to the forwarder in the Stream app, for example, you can add/enable a dummy stream and disable it again later, or change on of the configuration options for an existing Stream https://docs.splunk.com/Documentation/StreamApp/latest/User/ConfigureStreamsMetadata or restarting Splunk Forwarder service in Windows, for example through services.msc Sample scenario where you might run into this:
Reconfiguration of the NIC while Stream is running (for example, changing the flow control mode in our testing) |
PREVIOUS Fixed issues |
NEXT Boost C++ |
This documentation applies to the following versions of Splunk Stream™: 8.0.2
Feedback submitted, thanks!