https://community.splunk.com/t5/Splunk-Search/Issue-with-splunk-stop-restart-command-in-CentOS-7-2/m-p/331539#M174917 <P>The only potential issue I can think of is that "service splunk ..." requires elevated privileges while "/opt/splunk/bin/splunk ..." requires the privileges of whichever user owns /opt/splunk and its files. That's where I'd investigate first.</P> Mon, 17 Apr 2017 12:53:06 GMT jonmargulies 2017-04-17T12:53:06Z https://community.splunk.com/t5/Splunk-Search/Issue-with-splunk-stop-restart-command-in-CentOS-7-2/m-p/331538#M174916 <P>Hi All,</P> <P>Our distributed splunk setup contains a deployment server, an indexer cluster master, 3 peer indexers and 2 search heads. We use CentOS 7.2 for all our splunk instances and use salt stack to manage the nodes from a single point.</P> <P>In our salt script, we use the command: <CODE>service splunk stop/restart</CODE> while installing or upgrading our apps. However, we find that this command works inconsistently. The command <CODE>/opt/splunk/bin/splunk stop/restart</CODE> works correctly.</P> <P>Has anybody else faced this issue? Is this an issue specific to CentOS? Any pointers to this will be really helpful.</P> <P>Thanks,<BR /> Keerthana</P> Mon, 17 Apr 2017 11:53:07 GMT https://community.splunk.com/t5/Splunk-Search/Issue-with-splunk-stop-restart-command-in-CentOS-7-2/m-p/331538#M174916 keerthana_k 2017-04-17T11:53:07Z https://community.splunk.com/t5/Splunk-Search/Issue-with-splunk-stop-restart-command-in-CentOS-7-2/m-p/331539#M174917 <P>The only potential issue I can think of is that "service splunk ..." requires elevated privileges while "/opt/splunk/bin/splunk ..." requires the privileges of whichever user owns /opt/splunk and its files. That's where I'd investigate first.</P> Mon, 17 Apr 2017 12:53:06 GMT https://community.splunk.com/t5/Splunk-Search/Issue-with-splunk-stop-restart-command-in-CentOS-7-2/m-p/331539#M174917 jonmargulies 2017-04-17T12:53:06Z