<?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 Why is there Master UI issue after upgraded to v9.1.0.2? in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Why-is-there-Master-UI-issue-after-upgraded-to-v9-1-0-2/m-p/655171#M13202</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;We were running v9.0.5 and I upgraded the master to v9.1.0.2.&amp;nbsp; This is on CentOS 7.&amp;nbsp; The upgrade ran successfully, rebooted, and splunk started with all ports opened:&lt;/P&gt;
&lt;P&gt;Checking prerequisites...&lt;BR /&gt;Checking http port [8000]: open&lt;BR /&gt;Checking mgmt port [8089]: open&lt;BR /&gt;Checking appserver port [127.0.0.1:8065]: open&lt;BR /&gt;Checking kvstore port [8191]: open&lt;/P&gt;
&lt;P&gt;These are running for splunk status:&lt;/P&gt;
&lt;P&gt;splunkd is running (PID: 4730).&lt;BR /&gt;splunk helpers are running (PIDs: 4784 4828).&lt;/P&gt;
&lt;P&gt;Inside the instance, I can ping localhost.&amp;nbsp; But when I ping localhost 8000; it hung for a long time.&lt;/P&gt;
&lt;P&gt;Also, from my indexer instance; I can ping the master ip but not with port 8000 and 8089.&lt;/P&gt;
&lt;P&gt;I checked security groups and such.&amp;nbsp; Ports are allowed.&amp;nbsp; Nothing changed.&amp;nbsp; The UI was running before I started the upgrade.&lt;/P&gt;
&lt;P&gt;Anyone ran into this issue with the upgrade?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 22 Aug 2023 20:31:24 GMT</pubDate>
    <dc:creator>beach</dc:creator>
    <dc:date>2023-08-22T20:31:24Z</dc:date>
    <item>
      <title>Why is there Master UI issue after upgraded to v9.1.0.2?</title>
      <link>https://community.splunk.com/t5/Installation/Why-is-there-Master-UI-issue-after-upgraded-to-v9-1-0-2/m-p/655171#M13202</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;We were running v9.0.5 and I upgraded the master to v9.1.0.2.&amp;nbsp; This is on CentOS 7.&amp;nbsp; The upgrade ran successfully, rebooted, and splunk started with all ports opened:&lt;/P&gt;
&lt;P&gt;Checking prerequisites...&lt;BR /&gt;Checking http port [8000]: open&lt;BR /&gt;Checking mgmt port [8089]: open&lt;BR /&gt;Checking appserver port [127.0.0.1:8065]: open&lt;BR /&gt;Checking kvstore port [8191]: open&lt;/P&gt;
&lt;P&gt;These are running for splunk status:&lt;/P&gt;
&lt;P&gt;splunkd is running (PID: 4730).&lt;BR /&gt;splunk helpers are running (PIDs: 4784 4828).&lt;/P&gt;
&lt;P&gt;Inside the instance, I can ping localhost.&amp;nbsp; But when I ping localhost 8000; it hung for a long time.&lt;/P&gt;
&lt;P&gt;Also, from my indexer instance; I can ping the master ip but not with port 8000 and 8089.&lt;/P&gt;
&lt;P&gt;I checked security groups and such.&amp;nbsp; Ports are allowed.&amp;nbsp; Nothing changed.&amp;nbsp; The UI was running before I started the upgrade.&lt;/P&gt;
&lt;P&gt;Anyone ran into this issue with the upgrade?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 20:31:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Why-is-there-Master-UI-issue-after-upgraded-to-v9-1-0-2/m-p/655171#M13202</guid>
      <dc:creator>beach</dc:creator>
      <dc:date>2023-08-22T20:31:24Z</dc:date>
    </item>
  </channel>
</rss>

