- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Installation
- :
- Why is MC broken after upgrade to 8.2.7?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why is MC broken after upgrade to 8.2.7?
Getting 404 errors when trying to access the MC Summary and Health Check pages after an upgrade from 8.1.5 to 8.2.7. First error is:
monitoringconsole_landing.js:283 Uncaught (in promise) TypeError: _swcMc.ThemeUtils.getReactUITheme is not a function
etc. etc.
Any seen something similar? Other pages in MC console work fine.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this still broken for everyone? It's been 3 months for us. I thought there was supposed to be a fix for 8.2.x. Or is 9.x the only way to fix it?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @youngec
Splunk passed me this released fix a few days ago, but I've not had the chance to try it yet.
------------------
The patch for this issue has been released in the following version 8.2.7.2. I have pasted the links below as per the engineering team.
https://download.splunk.com/products/splunk/releases/8.2.7.2/linux/splunk-8.2.7.2-394c9ab9e27e-Linux...
I also want to inform you that Splunk version 8.2.9(sustain/scootaloo) which has the bug fixed will be released in November month.
-------------------------
Note, I checked and 8.2.7.2 is not yet up on the Splunk official download site.
Check for any potential compatibility issues here: https://docs.splunk.com/Documentation/Splunk/8.2.7/Indexer/Systemrequirements#Splunk_Enterprise_vers...
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just adding my experience, after upgrading to 8.2.7.1, I'm also not able to load the health check or summary pages in MC. I can't recall whether I've run the check in the past couple weeks (upgraded from 8.2.5 to 8.2.7 a few weeks ago) but I do know it was working on 8.2.5.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was Splunk supports reply to me:
"This bug (SPL-226483) has been assigned to a Senior Software Engineer and is currently being worked on."
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks! I'll open my own ticket tomorrow to see if that adds some heat. I also forgot to mention I don't see this on the known issues page for 8.2.7 as of this writing, so I'll bring that up in my ticket.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any answer from Splunk about this case
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No updates. As a matter of fact, 8.2.8 was just released and not a word was mentioned about this issue. I am still very unhappy with this.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nevermind what I said about it not being under known issues, it is there, I must have scrolled past it. 😓
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk advised that it's not an issue in Splunk 9+ and suggested upgrading to latest version to resolve. Currently not a big enough issue for us to consider.
They have since downgraded my support ticket to P4 so I doubt that it'll ever be fixed in later Splunk 8.2.7+ versions.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just got word from Splunk support that a fix is in testing right now and that they'll let me know when it's released. You just have to be persistent and refuse to take no for an answer for something like this.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah, and I'll argue that they aren't fixing it as a way of forcing people onto v9. How can break your own product, leave it broken, then tell people to "Just upgrade to 9+" ??
That's a BS answer.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @sebridge
The monitoring console (MC) in our environment is doing the same, after upgrading from 8.05 to 8.2.7 last week. It includes the MC > Settings > Health Check Items page too, just sits there loading and the the DevTool console shows the 404 errors due to endpoints not existing.
It's not just our management server's MC either, but the deployers, hfs and idxs.
I've opened a support case with Splunk about it. For reference, case number is 3017536.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am having the same issue as well. Has there been any updates on your case or is there a way I can see it? I noticed you put the referenced number. New to Splunk!!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @mello920
It took a couple of weeks with Splunk support before they even opened the case internally with their engineering/dev team as they do not appear to have to their own Splunk envs. It is now waiting on dev to confirm if they can reproduce the issue. Still waiting...
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk have confirmed this is an issue in the 8.2.7 release and their Engineering team is working on a workaround/fix.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
New This Month in Splunk Observability Cloud - Metrics Usage Analytics, Enhanced K8s ...
Alerting Best Practices: How to Create Good Detectors
Discover Powerful New Features in Splunk Cloud Platform: Enhanced Analytics, ...
