<?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 splunkweb will not stop in Security</title>
    <link>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90350#M2981</link>
    <description>&lt;P&gt;Can't get to the web UI and during restart we are getting &lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
Timed out waiting for splunkweb to stop.                   [FAILED]&lt;BR /&gt;
&lt;/PRE&gt;&lt;BR /&gt;
And then during startup:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
splunkweb is already running.                              [FAILED]&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;trying to restart splunkweb returns the same errors. &lt;/P&gt;

&lt;P&gt;Can find lots of info about splunkweb NOT starting, but not much on a timed out shutdown. Any suggestions?  web_service.log shows the following:&lt;/P&gt;

&lt;PRE&gt;
2011-10-11 22:52:12,933 ERROR   [4e9500dced2aaaaccb4710] utility:59 - name=javascript, class=Splunk.Error, lineNumber=0, message=uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: &lt;A href="https://10.20.72.89:8000/enUS/static/@101277.2/js/common.min.js" target="test_blank"&gt;https://10.20.72.89:8000/enUS/static/@101277.2/js/common.min.js&lt;/A&gt; :: &lt;TOP_LEVEL&gt; :: line 13066"  data: no], fileName=
2011-10-11 22:59:16,043 ERROR   [4e9502840a2aaaaccc8550] utility:59 - name=javascript, class=Splunk.Error, lineNumber=8234, message=response is null, fileN                         ame=https://10.20.72.89:8000/en-US/static/@101277.2/js/common.min.js
2011-10-12 08:21:50,861 INFO    [4e94386bc81a2b2550] root:133 - ENGINE: Caught signal SIGTERM.
2011-10-12 08:21:50,861 INFO    [4e94386bc81a2b2550] root:133 - ENGINE: Bus STOPPING
&lt;/TOP_LEVEL&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 12 Oct 2011 12:57:56 GMT</pubDate>
    <dc:creator>hharvey</dc:creator>
    <dc:date>2011-10-12T12:57:56Z</dc:date>
    <item>
      <title>splunkweb will not stop</title>
      <link>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90350#M2981</link>
      <description>&lt;P&gt;Can't get to the web UI and during restart we are getting &lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
Timed out waiting for splunkweb to stop.                   [FAILED]&lt;BR /&gt;
&lt;/PRE&gt;&lt;BR /&gt;
And then during startup:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
splunkweb is already running.                              [FAILED]&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;trying to restart splunkweb returns the same errors. &lt;/P&gt;

&lt;P&gt;Can find lots of info about splunkweb NOT starting, but not much on a timed out shutdown. Any suggestions?  web_service.log shows the following:&lt;/P&gt;

&lt;PRE&gt;
2011-10-11 22:52:12,933 ERROR   [4e9500dced2aaaaccb4710] utility:59 - name=javascript, class=Splunk.Error, lineNumber=0, message=uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: &lt;A href="https://10.20.72.89:8000/enUS/static/@101277.2/js/common.min.js" target="test_blank"&gt;https://10.20.72.89:8000/enUS/static/@101277.2/js/common.min.js&lt;/A&gt; :: &lt;TOP_LEVEL&gt; :: line 13066"  data: no], fileName=
2011-10-11 22:59:16,043 ERROR   [4e9502840a2aaaaccc8550] utility:59 - name=javascript, class=Splunk.Error, lineNumber=8234, message=response is null, fileN                         ame=https://10.20.72.89:8000/en-US/static/@101277.2/js/common.min.js
2011-10-12 08:21:50,861 INFO    [4e94386bc81a2b2550] root:133 - ENGINE: Caught signal SIGTERM.
2011-10-12 08:21:50,861 INFO    [4e94386bc81a2b2550] root:133 - ENGINE: Bus STOPPING
&lt;/TOP_LEVEL&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 12 Oct 2011 12:57:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90350#M2981</guid>
      <dc:creator>hharvey</dc:creator>
      <dc:date>2011-10-12T12:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: splunkweb will not stop</title>
      <link>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90351#M2982</link>
      <description>&lt;P&gt;Bit of a wild one this but do a splunk stop, followed with;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ps x | grep splunk
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;At the start of each row is the PID of the app, type;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;kill -9 PID
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will then kill the instance. I would be tempted to kill each splunk entry (the web one should start with python -O and then the rest of the name lists off into the Splunk directory.&lt;/P&gt;

&lt;P&gt;This is a bit of a hack and a slash method however, once done try starting it up again.&lt;BR /&gt;
If that fails it might be the lock file (If I remember this correctly) and it may not be getting cleared or it may have been created by a user of a higher level and splunk is now having a fit when trying to start.&lt;/P&gt;

&lt;P&gt;Note: this assumes linux &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2011 13:22:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90351#M2982</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2011-10-12T13:22:27Z</dc:date>
    </item>
    <item>
      <title>Re: splunkweb will not stop</title>
      <link>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90352#M2983</link>
      <description>&lt;P&gt;this did it - thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2011 13:38:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90352#M2983</guid>
      <dc:creator>hharvey</dc:creator>
      <dc:date>2011-10-12T13:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: splunkweb will not stop</title>
      <link>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90353#M2984</link>
      <description>&lt;P&gt;no probs &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2011 14:12:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunkweb-will-not-stop/m-p/90353#M2984</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2011-10-12T14:12:19Z</dc:date>
    </item>
  </channel>
</rss>

