Splunk Enterprise Security

Invalid message type: 28 during Splunk ES 7.1 Upgrade

youngsuh
Contributor

Getting this error via UI upgrade to Splunk 7.1:  Invalid message type: 28

We're on version 9.0.4.  Previous upgrade work without this error using the UI.

Labels (3)
0 Karma
1 Solution

youngsuh
Contributor

We deleted the /tmp to clear for the upgrade after failure.  Did the CLI upgrade instead based on the documentation.

Upgrade Splunk Enterprise Security - Splunk Documentation

./splunk install app <path to app> -update 1 -auth <username>:<password>

Then we went the UI portion to finish the configuration.  Watch the usual logs. Restarted the web UI.

View solution in original post

youngsuh
Contributor

We deleted the /tmp to clear for the upgrade after failure.  Did the CLI upgrade instead based on the documentation.

Upgrade Splunk Enterprise Security - Splunk Documentation

./splunk install app <path to app> -update 1 -auth <username>:<password>

Then we went the UI portion to finish the configuration.  Watch the usual logs. Restarted the web UI.

computermathguy
Path Finder

I just noticed the same type-28 error.  Before this occurred, were getting a "500 Internal Server" error. We are on Splunk 9.0.5

Waiting to hear back from Splunk support if they can resolve the UI install issue with ES 7.1.1

youngsuh
Contributor

It appears the problem still around.  I am upgrading to 7.3.1 and still getting the error.  I had to use the CLI option to upgrade. 

0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco &#43; Splunk! We’ve ...