I cannot find it in any of the current online documentation, but I don't think that upgrading from a beta version to a release version is officially supported. So, I wouldn't be surprised if it doesn't work entirely correctly.
I just tried upgrading it to 4.3.1 with the same issue.
How did the other Beta user eventually manage to upgrade to 4.3?
This is really wasting a lot of time, I need to know if it cant be done.
@Dark_Ichigo - I'm afraid I have to agree with dwaddle, it appears that it's not officially supported as I've just been through all the documentation on upgrading and haven't seen anything about upgrading from a BETA to a release version.
Yes this was an unsupported upgrade but aren't most cowboys who want to squeeze the most of Splunk ride in the realm of unsupported?
I know this is very late in the game but I've figured it out -
If you look at $SPLUNK_HOME/var/run/splunk/merged/web.conf
The very last line says versionlabelformat = %sBeta or something like that. Remove the Beta and you're in business.
Thanks for the response, I was waiting for someone to finally help solve this issue.
Although I tried what you mentioned, but after a restart of Splunk it seems to go back to beta, with the web.conf modified back to versionlabelformat = %sBeta
Well I believe that the files in the 'merged' directory are just that, i.e. merged from the various files in
$SPLUNK_HOME/etc/system/(default|local)/<file>.conf etc etc. That means that you need to find the correct web.conf elsewhere in the system and edit it - or put in an overriding value in
Also, if there are any real changes to the product that didn't upgrade correctly from BETA to RELEASE, I hardly think that this type of change would affect anything. To me it looks just like an informational label.
just my 2 cents,
Although this can confuse people who want to upgrade from the Beta version and because of this think its still in Beta 😛