Splunk® Enterprise

Release Notes

Splunk Enterprise version 7.1 is no longer supported as of October 31, 2020. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk® Enterprise. For documentation on the most recent version, go to the latest release.

Fixed issues

Splunk Enterprise 7.1.6 was released on January 22, 2019. This release includes fixes for the following issues.

Issues are listed in all relevant sections. Some issues might appear more than once. To check for additional security issues related to this release, visit the Splunk Security Portal.


Date resolved Issue number Description
2019-01-08 SPL-164251, SPL-163808 CIM Setup page is showing single line because of syntax error in underlying search
2019-01-03 SPL-163531, SPL-162247 After adding Tags Whitelist for Data Models, the newly added tags disappears when there is a change in the acceleration setting for the respective datamodel from the UI.
2019-01-03 SPL-164267, SPL-158199 when merging tsidx files, splunk optimize failed to open temporary manifest file due to file name collision cause by race condition
2019-01-02 SPL-163553, SPL-157146 Diag with SPLUNK_DB set to drive name and \ results in improper format on Windows
2018-12-18 SPL-158779, SPL-160529, SPL-163474 Indexer search process crash with thread: BatchSearch
2018-12-14 SPL-163975, SPL-157230 conf-mutator.pid cleanup error during GUI initiated restart
2018-12-10 SPL-154925, SPL-161164, SPL-162971 KVstore restore failure sometimes when having >1000 rows in the collection
2018-12-06 SPL-158665, SPL-162689, SPL-163621 Token inside HTML element is not localized
2018-11-27 SPL-163030, SPL-157014 Search results on a dashboard are given with system timezone instead of user timezone
2018-11-20 SPL-162981, SPL-152828 Splunk does not start as specified user on boot on MacOS
2018-11-19 SPL-158551, SPL-157891 Unable to open bucket as bucket is stuck in stale state
2018-11-14 SPL-162724, SPL-159413 "Failed to localize" due to "ERROR CacheManagerHandler"..."not an owner"..."and the bucket is draining"
2018-11-14 SPL-160401, SPL-158148 S2 Migration - Remove-excess-buckets triggering summary reaping from S3 inadvertently - Customer seeing slow searches when using tstats / dma
2018-11-09 SPL-161253, SPL-159966 ADP: "Failed to localize" after startup because bucket is not registered with the CacheManager until repair finishes
2018-11-06 SPL-162307, SPL-161462 Splunk is crashing with CacheManager FATAL error
2018-11-06 SPL-158943, SPL-157993, SPL-163684 S2 / Indexes UI - When maxTotalDataSizeMB != maxGlobalDataSizeMB only maxTotalDataSizeMB shown in UI on S2
2018-10-25 SPL-161770, SPL-159234 Splunk WebUI always defaults to http://localhost:8000/en-US local even if browser is configured to use other language
2018-10-10 SPL-161122, SPL-154451 Only 100 indexes are listed when creating or modifying a HEC on SH
Last modified on 12 August, 2024
Timestamp recognition of dates with two-digit years fails beginning January 1, 2020   Deprecated features

This documentation applies to the following versions of Splunk® Enterprise: 7.1.6


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters