<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: splunk process compulsion stop in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121672#M1435</link>
    <description>&lt;P&gt;@kobayashikenji I am bit curious to know about the purpose of force-stopping Splunk. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 May 2015 02:37:31 GMT</pubDate>
    <dc:creator>miteshvohra</dc:creator>
    <dc:date>2015-05-26T02:37:31Z</dc:date>
    <item>
      <title>splunk process compulsion stop</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121667#M1430</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;

&lt;P&gt;I want to kill the process of Splunk.&lt;BR /&gt;
May be performed by specifying the "PID" with this command ?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;kill -9 &amp;lt;PID&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;There is no problem?&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2015 03:47:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121667#M1430</guid>
      <dc:creator>kobayashikenji</dc:creator>
      <dc:date>2015-05-25T03:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: splunk process compulsion stop</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121668#M1431</link>
      <description>&lt;P&gt;This works, make sure when you restart Splunk, you are using the correct user.&lt;/P&gt;

&lt;P&gt;But why not do  '/opt/splunk/splunk stop' or 'service splunk stop'&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2015 04:28:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121668#M1431</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2015-05-25T04:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: splunk process compulsion stop</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121669#M1432</link>
      <description>&lt;P&gt;You can kill all processes on 'splunkd' with&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;kill `ps -ef | grep splunkd | egrep -v grep | awk '{print $2}'`&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;But, just like @esix_splunk mentioned, make sure you restart Splunk with the correct user and that, using Splunk's native commands to Start/Stop/Restart the service is much cleaner.&lt;/P&gt;

&lt;P&gt;Mitesh.&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2015 07:51:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121669#M1432</guid>
      <dc:creator>miteshvohra</dc:creator>
      <dc:date>2015-05-25T07:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: splunk process compulsion stop</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121670#M1433</link>
      <description>&lt;P&gt;If not stop at Splunk command,&lt;BR /&gt;
Because I want to compulsion stop.&lt;BR /&gt;
Normally, will use the "splunk stop".&lt;BR /&gt;
Answer Thank you very much.&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2015 09:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121670#M1433</guid>
      <dc:creator>kobayashikenji</dc:creator>
      <dc:date>2015-05-25T09:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: splunk process compulsion stop</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121671#M1434</link>
      <description>&lt;P&gt;Thank you very much.&lt;BR /&gt;
I wanted absolutely compulsion stop.&lt;BR /&gt;
Normally, you run the answer @ esix_splunk.&lt;/P&gt;

&lt;P&gt;kenji.&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2015 09:41:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121671#M1434</guid>
      <dc:creator>kobayashikenji</dc:creator>
      <dc:date>2015-05-25T09:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: splunk process compulsion stop</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121672#M1435</link>
      <description>&lt;P&gt;@kobayashikenji I am bit curious to know about the purpose of force-stopping Splunk. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2015 02:37:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-process-compulsion-stop/m-p/121672#M1435</guid>
      <dc:creator>miteshvohra</dc:creator>
      <dc:date>2015-05-26T02:37:31Z</dc:date>
    </item>
  </channel>
</rss>

