Known issues

Version 8.0.0 of Splunk Stream contains the following known issues.

If no issues appear below, no issues have yet been reported:

Date filed	Issue number	Description
2021-12-10	STREAM-5036	Streamfwd process down when a specific protocol is specified on the Distributed Forwarder Management screen
2021-10-29	STREAM-5007, STREAM-5074	Stream Forwarder fails when processing threads is set to higher than one Workaround: revert back to 7.4
2021-08-05	STREAM-4900	Un-installing Splunk TA Stream from Windows Universal Forwarder using Deployment Server results in files not getting removed
2021-01-31	STREAM-4679, STREAM-4893	Stream app does not propagate HEC token to Independent Stream Forwarder Workaround: Available workaround: Manually configure HEC token in streamfwd.conf file and ISF is able to connect to the inputs data manager and send the events successfully.
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)