Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Installation
- :
- Issue with Upgrade Splunk Enterprise from 7.0.3 to...
- 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
Issue with Upgrade Splunk Enterprise from 7.0.3 to 7.2.3
Hi, I have tried upgrading Splunk Enterprise 7.0.3 to latest 7.2.3 and getting below errors.
ERROR: [App Key Value Store migration] Service(36) terminated before the service availability check could complete. Exit code 48, waited for 0 seconds. [App Key Value Store migration] Checking if migration is needed. Upgrade type 1. This can take up to 600 seconds. ERROR while running mongod-fix-voting-priority migration.
does any one tried upgrading latest version and encounter such issue ?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This appears related and is apparently fixed in 7.2.4: "SPL-162469, SPL-163577, SPL-162764 After upgrade to 7.2 Splunk is unable to start - KVStoreConfigurationThread crash".
See the "Unsorted Issues" section:
https://docs.splunk.com/Documentation/Splunk/7.2.4/ReleaseNotes/Fixedissues
An upvote would be appreciated and Accept Solution if it helps!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any other ERROR message ? Worth to look at https://docs.splunk.com/Documentation/Splunk/7.2.3/Admin/TroubleshootKVstore#KV_store_migration_mess...
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks I ll have a look. No other error. Installation gets terminated after this error.
I have downgraded to 7.2.2 and it worked fine.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is cron related bug in 7.2.2 so not good idea to run on 7.2.2, better to upgrade to 7.2.3
2018-12-21 SPL-164242, SPL-164210 A search scheduled to run monthly or weekly may run daily. "Next Scheduled Time" is incorrect due to cron parsing issue
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for pointing out. I'll check if there is any impact for us.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did this fix your issue?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@SloshBurch : we haven't upgraded to 7.2.2 or 7.2.3. There are some other issues with these version. finally we have upgraded to 7.1.6 which is more stable.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok thanks for the update. But I assume this issue is not present on 7.1.6 at least.
Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA
.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...
A Season of Skills: New Splunk Courses to Light Up Your Learning Journey
