After enabling boot start, the server was not starting up on the Linux based server.
1. Confirmed with the end user whether Splunk service is using initd file or systemd file.
2. If the server is using initd file, the location of the file would be $SPLUNK_HOME/etc/init.d
3. If the server is using systemd file, the location of the file would be $SPLUNK_HOME/etc/systemd/system
4. Either systemd or initd should be used on the server and not both.
5. Provided the below command to run under the bin directory for boot start enable:-
[sudo] $SPLUNK_HOME/bin/splunk enable boot-start -user <username> -systemd-managed 1
6. After performing the boot-start enable, the issue was still persisting.
The reason it failed was due to the generation of multiple service files while enabling boot-start mapping with the days timestamp.
Workaround :-
1. Stop the splunk service -
$SPLUNK_HOME/bin/ ./splunk stop
2. Disable the boot-start in the bin directory -
[sudo] $SPLUNK_HOME/bin/splunk disable boot-start
3. Use the rm -rf command to remove all the service unit files which were enabled -
rm -rf <service file-name>
4. Enable boot-start by using the below command -
[sudo] $SPLUNK_HOME/bin/splunk enable boot-start
5. Start the splunk service -
$SPLUNK_HOME/bin/ ./splunk start
Configure Splunk to Start at Boot Time
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |