Splunk could be crashing due to the following reasons:
Not enough memory (check /var/log/messages for OOM errors)
SELINUX, (did you disable SELINUX? CentOS 7, by default, enforces it and running as root might be causing badness)
ES could be causing significant load, but typically won't crash the system (unless it forces OOM killer at the OS level)
Perhaps the OS is shutting down Splunk because of a lack of resources.
While investigating the HF diag you may find the following error:
error: ERROR TailingProcessor [22070 MainTailingThread] - Input stanza path, '$WINDIR\WindowsUpdate.log' is not absolute. This is a configuration error and may not work/break things. Change this path to an absolute path.
Check $SPLUNK_HOME/etc/apps/Splunk_TA_windows\local it has an inputs.conf with most of the monitoring stanzas with disabled = 1. Confirm you are forwarding windows log events from windows add-on to linux server.
As Splunk_TA_Windows was installed on a Linux machine which collects data from the Windows system and it forwards windows logs to linux server incorrectly.
Uninstalling the Splunk_TA_Windows add-on resolved the issue.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |