<?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: Upgraded from Splunk 7.0.3 to 7.2.1 and the Splunk Web Server is unavailable. in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Upgraded-from-Splunk-7-0-3-to-7-2-1-and-the-Splunk-Web-Server-is/m-p/405239#M5437</link>
    <description>&lt;P&gt;The workaround is to disable health reporting in health.conf (until the Bug is fixed in Splunk 7.2.x).&lt;/P&gt;

&lt;P&gt;The issue is a known and is caused by the Bugs below.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;SPL-162549&lt;/STRONG&gt;&lt;BR /&gt;
splunkweb fails to start and SHC member shows as down&lt;BR /&gt;
Affects: 7.1.4&lt;BR /&gt;
Fixed in: 7.1.6&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;SPL-160230&lt;/STRONG&gt;&lt;BR /&gt;
Splunkd web fails to start due to deadlock among Health Reporter threads&lt;BR /&gt;
Affects: 7.1.2&lt;BR /&gt;
Fixed in: 7.1.6&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Steps&lt;/STRONG&gt;&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Make the changes to the file below:&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;/etc/system/local/health.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[clustering]
disabled = 1

[feature:batchreader]
disabled = 1

[feature:tailreader]
disabled = 1

[feature:s2s_autolb]
disabled = 1

[feature:indexers]
disabled = 1

[feature:data_durability]
disabled = 1

[feature:cluster_bundles]
disabled = 1

[feature:indexing_ready]
disabled = 1

[feature:data_searchable]
disabled = 1

[feature:searchheadconnectivity]
disabled = 1

[feature:replication_failures]
disabled = 1

[feature:master_connectivity]
disabled = 1

[feature:slave_state]
disabled = 1

[feature:slave_version]
disabled = 1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;2.Restart Splunk.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jan 2019 10:44:21 GMT</pubDate>
    <dc:creator>christopherr_sp</dc:creator>
    <dc:date>2019-01-15T10:44:21Z</dc:date>
    <item>
      <title>Upgraded from Splunk 7.0.3 to 7.2.1 and the Splunk Web Server is unavailable.</title>
      <link>https://community.splunk.com/t5/Installation/Upgraded-from-Splunk-7-0-3-to-7-2-1-and-the-Splunk-Web-Server-is/m-p/405238#M5436</link>
      <description>&lt;P&gt;Upgraded from Splunk 7.0.3 and 7.2.1 the Splunk Web Server is unavailable.&lt;/P&gt;
&lt;P&gt;When Splunk is started from the command line, the following output appears on the screen:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;Waiting for web server at &lt;A href="http://127.0.0.1:8000" target="test_blank"&gt;http://127.0.0.1:8000&lt;/A&gt; to be available...........................
..........................................................................................

WARNING:  web interface does not seem to be available!
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 15 Jun 2020 17:47:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Upgraded-from-Splunk-7-0-3-to-7-2-1-and-the-Splunk-Web-Server-is/m-p/405238#M5436</guid>
      <dc:creator>christopherr_sp</dc:creator>
      <dc:date>2020-06-15T17:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: Upgraded from Splunk 7.0.3 to 7.2.1 and the Splunk Web Server is unavailable.</title>
      <link>https://community.splunk.com/t5/Installation/Upgraded-from-Splunk-7-0-3-to-7-2-1-and-the-Splunk-Web-Server-is/m-p/405239#M5437</link>
      <description>&lt;P&gt;The workaround is to disable health reporting in health.conf (until the Bug is fixed in Splunk 7.2.x).&lt;/P&gt;

&lt;P&gt;The issue is a known and is caused by the Bugs below.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;SPL-162549&lt;/STRONG&gt;&lt;BR /&gt;
splunkweb fails to start and SHC member shows as down&lt;BR /&gt;
Affects: 7.1.4&lt;BR /&gt;
Fixed in: 7.1.6&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;SPL-160230&lt;/STRONG&gt;&lt;BR /&gt;
Splunkd web fails to start due to deadlock among Health Reporter threads&lt;BR /&gt;
Affects: 7.1.2&lt;BR /&gt;
Fixed in: 7.1.6&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Steps&lt;/STRONG&gt;&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Make the changes to the file below:&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;/etc/system/local/health.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[clustering]
disabled = 1

[feature:batchreader]
disabled = 1

[feature:tailreader]
disabled = 1

[feature:s2s_autolb]
disabled = 1

[feature:indexers]
disabled = 1

[feature:data_durability]
disabled = 1

[feature:cluster_bundles]
disabled = 1

[feature:indexing_ready]
disabled = 1

[feature:data_searchable]
disabled = 1

[feature:searchheadconnectivity]
disabled = 1

[feature:replication_failures]
disabled = 1

[feature:master_connectivity]
disabled = 1

[feature:slave_state]
disabled = 1

[feature:slave_version]
disabled = 1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;2.Restart Splunk.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2019 10:44:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Upgraded-from-Splunk-7-0-3-to-7-2-1-and-the-Splunk-Web-Server-is/m-p/405239#M5437</guid>
      <dc:creator>christopherr_sp</dc:creator>
      <dc:date>2019-01-15T10:44:21Z</dc:date>
    </item>
  </channel>
</rss>

