Splunk® Enterprise

Release Notes

Acrobat logo Download manual as PDF


Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. 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. Click here for the latest version.
Acrobat logo Download topic as PDF

6.6.11

Splunk Enterprise 6.6.11 was released on October 3, 2018.

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.

Search issues

Date resolved Issue number Description
2018-11-27 SPL-153464, SPL-157516, SPL-158568, SPL-158570 Job Progress Status goes from 0 to 100 back to 0
2018-09-17 SPL-157725, SPL-144000 Can't search for indexed fields included in summary index since fields.conf "INDEXED = true" since 6.6
2018-08-14 SPL-157433, SPL-158332, SPL-158580, SPL-158581 lookup OUTPUTNEW commands mistakenly cause optimizer to remove preceding search commands resulting in missing field values
2018-08-03 SPL-142710, SPL-149132, SPL-153835, SPL-153836 Splunk ignores "is_risky=false" setting for any command that is not an actual custom script like sendemail. For example the setting is ignored for outputlookup and outputcsv.

Saved search, alerting, scheduling, and job management issues

Date resolved Issue number Description
2018-08-10 SPL-153792, SPL-155699, SPL-158566, SPL-158567 Datamodel works both accelerated and non-accelerated in standalone, but fails on indexer instance when accelerated in an indexer clustered environment

Data model and pivot issues

Date resolved Issue number Description
2018-08-10 SPL-153792, SPL-155699, SPL-158566, SPL-158567 Datamodel works both accelerated and non-accelerated in standalone, but fails on indexer instance when accelerated in an indexer clustered environment

Indexer and indexer clustering issues

Date resolved Issue number Description
2018-08-10 SPL-148413, SPL-151331, SPL-158272, SPL-158273 Bucket fix-up stack stuck with reason "potential dup primaries" prevents cluster from advertising all data searchable

Distributed search and search head clustering issues

Date resolved Issue number Description
2018-08-10 SPL-157978, SPL-157926, SPL-157927, SPL-157928 Scheduler blocked during pruning savedsearch history due to slow LDAP server

Monitoring Console/DMC issues

Date resolved Issue number Description
2018-08-16 SPL-156694, SPL-158060, SPL-158341, SPL-158342 "Failed to fetch DMC settings to verify status" error in web_service.log when clicking "Settings> Data Inputs" from Splunk Web

Authentication and Authorization issues

Date resolved Issue number Description
2018-09-25 SPL-147611, SPL-157938, SPL-160381, SPL-160382, SPL-160868 Socket error message in splunkd after login to SplunkWeb with self-signed cert

Admin and CLI issues

Date resolved Issue number Description
2018-08-14 SPL-136970, SPL-156715, SPL-158503, SPL-158504 default and local meta files getting corrupted or being altered in such a way as to cause warnings

Uncategorized issues

Date resolved Issue number Description
2018-10-03 SPL-160858, SPL-160037 Windows 2016 Standard blocked Splunk Enterprise 6.6.10 installation on a VM with BIOS UEFI mode enabled + Secure Boot enabled due to "A digitally signed driver is required"
2018-09-24 SPL-142546, SPL-159412, SPL-160869, SPL-160870, SPL-160871 System message emanating from a search peer prompts to restart the search-head instead of the search peer it originates from
2018-09-18 SPL-159535 large number of buckets leads to slow splunkd restart (hours)
2018-09-17 SPL-158875, SPL-159174, SPL-159613, SPL-159614, SPL-159644 splunk shipped python in *nix doesn't work with iso2022_jp
2018-09-13 SPL-159597, SPL-152084 S2S: clientCert required in outputs.conf on SSL client although requireClientCent=false set on SSL server
2018-09-07 SPL-154378, SPL-156205, SPL-156206, SPL-156207 Splunk Introspection mem_used misreporting very high values "17592186044029.098"
2018-08-27 SPL-146261, SPL-159051, SPL-159186, SPL-159188 Search Assistant executes subsearches incurring subsearch side effects and increased CPU and memory usage
Last modified on 27 July, 2020
PREVIOUS
Timestamp recognition of dates with two-digit years fails beginning January 1, 2020
  NEXT
6.6.10

This documentation applies to the following versions of Splunk® Enterprise: 6.6.11, 6.6.12


Was this documentation topic helpful?

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