Installation

Why is there Master UI issue after upgraded to v9.1.0.2?

beach
Loves-to-Learn Everything

Hello,

We were running v9.0.5 and I upgraded the master to v9.1.0.2.  This is on CentOS 7.  The upgrade ran successfully, rebooted, and splunk started with all ports opened:

Checking prerequisites...
Checking http port [8000]: open
Checking mgmt port [8089]: open
Checking appserver port [127.0.0.1:8065]: open
Checking kvstore port [8191]: open

These are running for splunk status:

splunkd is running (PID: 4730).
splunk helpers are running (PIDs: 4784 4828).

Inside the instance, I can ping localhost.  But when I ping localhost 8000; it hung for a long time.

Also, from my indexer instance; I can ping the master ip but not with port 8000 and 8089.

I checked security groups and such.  Ports are allowed.  Nothing changed.  The UI was running before I started the upgrade.

Anyone ran into this issue with the upgrade? 

Thanks!

Labels (2)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...