When Splunk UF was upgraded, the account ownership for /opt/splunkforwarder/ was changed from root to another user - dmadmin. Then Splunk service stopped and multiple permission errors are reflecting.
Then the ownership was changed back from dmadmin to root, but the issue still persisted.
If Splunk Enterprise is running on Linux as a non-root user, and use an RPM to upgrade, the RPM writes the $SPLUNK_HOME/var/log/introspection directory as root. This can cause errors when the instance is attempted to start.
To prevent this, change the ownership to user with chown $SPLUNK_HOME/var/log/introspection directory Splunk Enterprise runs after upgrading and before restarting Splunk Enterprise.
But here, .tgz package was used instead of RPM.
SPLUNK_OS_USER=dmadmin
SPLUNK_OS_USER=root
Note : In order to change from root to other user in the future scenarios, using facl permission to the respective user/respective dir will avoid such issues.
Setfacl allows for much greater control over who has access to a specific file or folder.
What-is-the-best-way-to-make-var-log-audit
How-to-handle-Splunking-Linux-logs-through-the-Splunk-nix-TA
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |