<?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: Upgrade from 6.5.2 to 6.6.2 introduced delayed Web Start in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359102#M8112</link>
    <description>&lt;P&gt;That resolved the issue.  Thanks for the response!&lt;/P&gt;</description>
    <pubDate>Wed, 09 Aug 2017 18:03:34 GMT</pubDate>
    <dc:creator>wayn23</dc:creator>
    <dc:date>2017-08-09T18:03:34Z</dc:date>
    <item>
      <title>Upgrade from 6.5.2 to 6.6.2 introduced delayed Web Start</title>
      <link>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359100#M8110</link>
      <description>&lt;P&gt;The config in version 6.5.2 enable the web UI to use standard port 8000.  Upgraded to Splunk 6.6.2 following the recommended process and all proceeded as expected.  However, now whenever a Splunk instance is restarted (Indexer or search head), there is about a 5 minute delay before it starts listening on port 8000.  There is nothing indicating in the splunkd.log as to what is causing the delay.  Once it starts listening on port 8000, then a login can occur and everything works as expected.&lt;BR /&gt;
While not an actual error, does add extra elapsed when doing some configuration changes in Splunk that needs a reboot.&lt;BR /&gt;
Any ideas on what is happening?&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;BR /&gt;
Wayne&lt;/P&gt;</description>
      <pubDate>Tue, 08 Aug 2017 15:21:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359100#M8110</guid>
      <dc:creator>wayn23</dc:creator>
      <dc:date>2017-08-08T15:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade from 6.5.2 to 6.6.2 introduced delayed Web Start</title>
      <link>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359101#M8111</link>
      <description>&lt;P&gt;see &lt;A href="https://answers.splunk.com/answers/545000/slow-splunkweb-startup-caused-by-splunk-instrument.html"&gt;https://answers.splunk.com/answers/545000/slow-splunkweb-startup-caused-by-splunk-instrument.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;"On a server which doesn't have access to the proxy, I just put the following in my splunk-launch.conf: "&lt;BR /&gt;
 QUICKDRAW_URL=0&lt;/P&gt;</description>
      <pubDate>Wed, 09 Aug 2017 09:02:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359101#M8111</guid>
      <dc:creator>teunlaan</dc:creator>
      <dc:date>2017-08-09T09:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade from 6.5.2 to 6.6.2 introduced delayed Web Start</title>
      <link>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359102#M8112</link>
      <description>&lt;P&gt;That resolved the issue.  Thanks for the response!&lt;/P&gt;</description>
      <pubDate>Wed, 09 Aug 2017 18:03:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Upgrade-from-6-5-2-to-6-6-2-introduced-delayed-Web-Start/m-p/359102#M8112</guid>
      <dc:creator>wayn23</dc:creator>
      <dc:date>2017-08-09T18:03:34Z</dc:date>
    </item>
  </channel>
</rss>

