Known issues

This topic lists known issues that are specific to the universal forwarder. For information on fixed issues, see Fixed issues.

Universal forwarder issues

Date filed	Issue number	Description
2024-11-04	SPL-265630, SPL-259202, SPL-265631, SPL-265632, SPL-265633	Windows Universal Forwarder high cpu where Splunk user does not have read access to all of the files in the monitored directory
2024-07-17	SPL-259202, SPL-265630	Windows Universal Forwarder high cpu where Splunk user does not have read access to all of the files in the monitored directory
2023-12-14	SPL-248479, SPL-253092	9.1.1 HF enters state of constant blocking due to broken S2S protocol Workaround: To fix the issue, customers will have to add queueSize on the Splunk HF/IHF instance where persistent queue is enabled, in inputs.conf under the same stanza where persistentQueueSize is set. inputs.conf [<input stanza>] persistentQueueSize=<no change. keep existing value> queueSize=<100MB or 1% of total system memory(whichever is less)>
2022-08-17	SPL-228646, SPL-228645	Restart is needed when AWS access key pairs rotate (w/o grace period) or other S3 config settings for Ingest Actions become invalid
2022-06-23	SPL-226019	Warning appears in the universal forwarder whenever any spl command is run: Warning: Attempting to revert the SPLUNK_HOME ownership Warning: Executing "chown -R splunk /opt/splunkforwarder". This warning is expected and will not affect functionality.
2022-06-06	SPL-225379	Ownership of files mentioned in manifest file is splunk:splunk instead of root:root after enabling boot start as root user for initd Workaround: When changing UF user, manually chown SPLUNK_HOME to the new user, including first time install/upgrade, or manually enable boot-start.
2022-03-23	SPL-221239	System Introspect App fails when universal forwarder is installed at non-admin user