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
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...