Splunk admin has configured the boot-start with systemd managed service, but the splunk service is not starting automatically after server reboot. If started manually using $SPLUNK_HOME/bin/splunk start, Splunk runs without issues.
Splunkd.service is placed in /etc/systemd/system. Run a long-listing of that folder and confirm the file Splunkd.service exists:ls -l /etc/systemd/system
/etc/init.d:ls -l /etc/init.d
<username> is replaced with the user which runs Splunk (by default, the user is splunk unless specified otherwise by your system administrator:/opt/splunk/bin/splunk enable boot-start -systemd-managed 1 -user <username>
systemctl status Splunkd.service
If it is not running, check whether Splunk itself is running:/opt/splunk/bin/splunk status
If the service is not running but Splunk is, stop Splunk, then start the systemd service, then check the status of the service:/opt/splunk/bin/splunk stop
sudo systemctl start Splunkd.service
sudo systemctl status Splunkd.service
# systemctl start Splunkd.service
Job for Splunkd.service failed because the control process exited with error code.
See “systemctl status Splunkd.service” and “journalctl -xeu Splunkd.service” for details.
# systemctl status Splunkd.service
Splunkd.service - Systemd service file for Splunk, generated by 'splunk enable boot-start'
Loaded: loaded (/etc/systemd/system/Splunkd.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-08-26 10:43:54 PDT; 10s ago
Process: 1614509 ExecStart=/opt/splunk/bin/splunk _ internal_Launch_under_systend (code-exited, status=203/EXEC)
Process: 1614510 ExecStartPost=/bin/bash -c chown -R root:root /sys/fs/cgroup/system.slice/Splunkd.service (code-exited, >
Main PID: 1614509 (code-exited, status=203/EXEC)
CPU: 8msAug 26 10:43:54 your.hostname systemd[1]: Splunkd.service: Scheduled restart job, restart counter is at 5.
Aug 26 10:43:54 your.hostname systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'
Aug 26 10:43:54 your.hostname systemd[1]: Splunkd.service: Start request repeated too quickly.
Aug 26 10:43:54 your.hostname systemd[1]: Splunkd.service: Failed with result 'exit-code'.
Aug 26 10:43:54 your.hostname systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'
sudo journalctl -xeu Splunkd.service
If the output shows messages like this, then very likely SELinux is not allowing the process to start:systemd[1614503]: Splunkd.service: Failed at step EXEC spawning /opt/splunk/bin/splunk: Permission denied
systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'.
systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'.
systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'.
systemd[1614505]: Splunkd.service: Failed to locate executable /opt/splunk/bin/splunk: Permission denied
systemd[1614505]: Splunkd.service: Failed at step EXEC spawning /opt/splunk/bin/splunk: Permission denied
systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'.
systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'.
systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start’
systemd[114507]: Splunkd.service: Failed to locate executable /opt/splunk/bin/splunk: Permission denied
systemd[114507]: Splunkd.service: Failed at step EXEC spawning /opt/splunk/bin/splunk: Permission denied
getenforce
NOTE: If the output of getenforce does not show "Enabled" OR, setting it to permissive mode (as shown below) still produces a permissions issue, see the suggestion regarding the chown command in the resolution panesudo setenforce 0
getenforce
systemctl start Splunkd.service
ll -Z /opt
An example output from this command showing the context is not set for Splunk:
# 11 -Z
total 4
drwxr-xr-x. 3 splunk splunk system_u:object_r:usr_t:s0 17 Mar 25 07:52 MySoftware
drwxr-xr-x. 7 splunk splunk system_u:object_r:usr_t:s0 173 Mar 25 07:53 managesoft
drwxr-xr-x. 4 splunk splunk system_u:object_r:usr_t:s0 40 Mar 25 07:55 microsoft
drwxrwxr-x. 8 splunk splunk system_u:object_r:usr_t:s0 73 Mar 25 07:55 nessus_agent
drwxr-xr-x. 13 splunk splunk system_u:object_r:unlabeled_t:s0 4096 Aug 18 13:26 splunk
drwxr-xr-x. 3 splunk splunk system_u:object_r:unlabeled_t:s0 26 Mar 25 07:54 Tanium
If the Splunkd.service is failing with permissions issues but SELinux was either disabled or set to Permissive, OR, if setting SELinux to Permissive mode did not resolve the issue, consider file ownership in the $SPLUNK_HOME directory as a possible source of the problem. In this case, chown everything in the $SPLUNK_HOME path to ensure the user that runs Splunk has proper ownership of all files (-h includes symmlinks if present and any files within the source symmlink path; -R runs the command recursively:
sudo chown -hR splunk:splunk /opt/splunk
In the scenario which prompted this article, SELinux was set to Enforcing mode. Rather than leaving it at Permissive mode, since the context had not been set on the $SPLUNK_HOME directory, the below command was run to set the default context. On this system, SELinux was configured in a way to allow the service to run if the application is set with the default context. To change the context:
cd /opt/splunk/bin
./splunk stop
sudo restorecon -r /opt/splunk
ll -Z /opt
An example output from this command showing the context is not set for Splunk:
# 11 -Z
total 4
drwxr-xr-x. 3 splunk splunk system_u:object_r:usr_t:s0 17 Mar 25 07:52 MySoftware
drwxr-xr-x. 7 splunk splunk system_u:object_r:usr_t:s0 173 Mar 25 07:53 managesoft
drwxr-xr-x. 4 splunk splunk system_u:object_r:usr_t:s0 40 Mar 25 07:55 microsoft
drwxrwxr-x. 8 splunk splunk system_u:object_r:usr_t:s0 73 Mar 25 07:55 nessus_agent
drwxr-xr-x. 13 splunk splunk system_u:object_r:usr_t:s0 4096 Aug 26 10:23 splunk
drwxr-xr-x. 3 splunk splunk system_u:object_r:unlabeled_t:s0 26 Mar 25 07:54 Tanium
sudo setenforce 1
sudo systemctl enable Splunkd.service
sudo systemctl start Splunkd.service
systemctl status Splunkd.service
If setting the context does not resolve the issue, work with your security team to ensure SELinux is configured with a rule allowing Splunkd to run in permissive mode. Alternatively, you could set SELinux to run in Permissive mode overall, such that it persists after server reboots:
/etc/selinux/config. Update the selinux parameter:selinux = Permissive
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |