@PickleRick hello, because the Splunk documentation recommends running the commands like /opt/splunk/bin/splunk start|stop|restart using sudo. https://docs.splunk.com/Documentation/Splunk/9.1.2/Admin/RunSplunkassystemdservice#Manage_clusters_under_systemd There is also the following information "Under systemd, splunk start|stop|restart commands are mapped to systemctl start|stop|restart commands." Therefore, I believe that in this case there should be no difference in how exactly the restart is carried out. If you want to reproduce the problem yourself, here is a sample list of steps 1) Create Ubuntu 22.04 VM in Google Cloud Platform as example 2) Install Splunk Enterprise 9.1.2 dpkg -i splunk-9.1.2-b6b9c8185839-linux-2.6-amd64.deb 3) Enable Systemd Unit for Splunk /opt/splunk/bin/splunk enable boot-start -systemd-managed 1 -user splunk -group splunk --accept-license 4) Try to do commands like /opt/splunk/bin/splunk start|stop|restart and compare with systemd unit status, you will see errors. Well, in the end, you have commands like /opt/splunk/bin/splunk offline, which are not called through systemd.
... View more