Splunk® Enterprise

Release Notes

Download manual as PDF

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

6.3.3

Splunk Enterprise 6.3.3 was released on February 4, 2016.

The following issues have been resolved in this release. For information about security fixes not related to authentication or authorization, refer to the Splunk Security Portal.

Data input issues

Publication date Defect number Description
2016-2-2 SPL-109903, SPL-96886 MAX_DIFF_SECS_AGO and MAX_DIFF_SECS_HENCE accept events outside the expected time range

Search, saved search, alerting, scheduling, and job management issues

Publication date Defect number Description
2016-2-2 SPL-111500, SPL-109489 ParseNodeGROUP::associate shows poor performance.
2016-2-2 SPL-111364 Search to specific field of lookup crashes.
2016-2-2 SPL-111343 ConfReplicationThread log fields incorrectly parsed due to log format.
2016-2-2 SPL-109929 Space and double quote is reported in broken cookie handling.
2016-2-2 SPL-109918 Missing app icons and settings menu due to cookie parsing fail.
2016-2-2 SPL-112730, SPL-111621 BatchSearch (in Parallel Pipelines mode) SegFaults with invalid DatabaseDirectoryManager object because of Multithreading concurrency issues in updating IndexerGlobals::instance()

Splunk Web, DMC, and Home interface issues

Publication date Defect number Description
2016-2-2 SPL-111179 When max bucket size is set to anything less than 1024 with unit MB while creating an index, the unit will be shown as GB when you open the index next time.
2016-2-2 SPL-109809, SPL-109219 After upgrading to 6.3.x, the DMC overview page shows a total license stack size several times larger than the actual one
2016-2-2 SPL-107915 Overlay (right) Y-Axis label changes to match left Y-Axis label after resizing a panel inside dashboard.
2016-2-2 SPL-107484 When results are sorted by a column in dashboard's events viewer, the wrong event details appear upon expanding an event row.
2016-2-2 SPL-106277 When user performs a fetch from eventtypes/_new then creates a post with the same attributes from the fetch, a color attribute is added and causes an error.

Distributed deployment, forwarder, and deployment server issues

Publication date Defect number Description
2016-2-2 SPL-111343 ConfReplicationThread log fields incorrectly parsed due to log format.
2015-11-06 SPL-109514 Number of concurrent searches increases in an idle SHC member. Workaround:

In limits.conf set:

shc_role_quota_enforcement = false shc_local_quota_check = true

This will replicate 6.2 behavior, and avoid this issue.

Distributed search and search head clustering issues

Publication date Defect number Description
2016-2-2 SPL-111515 Bundles in lookup_tmp not reaped in SHC peers.
2016-2-2 SPL-109555 Skipped scheduled searches are not properly accounted for in scheduler.log and metrics.log / group=searchscheduler.

Windows-specific issues

Publication date Defect number Description
2016-2-2 SPL-110983, SPL-109585 perfmon monitor crash.
2016-2-2 SPL-110578 Result filtering using search filter box on manager listing page does not work when app context checkbox is selected
2016-2-2 SPL-109502 Splunk Web fails to start with: ERROR - cannot import name lib on Windows.

Unsorted issues

Publication date Defect number Description
2016-2-2 SPL-110878, SPL-104699 Splunk does not start on OSX 10.11 (El Capitan).
2016-2-2 SPL-109238 cherrypy IOError: Port 8065 not free on '127.0.0.1' when installing apps with web.conf.
2016-2-2 SPL-110235 libxml2 deadlock introduced in libxml 2.9.2.
2016-2-2 SPL-108219 File deadlock. Can cause repeated entry in splunkd.log which contains, "is already locked with state=<initcrc>". In certain conditions, deadlock can result in elevated CPU usage.
PREVIOUS
6.3.4
  NEXT
6.3.2

This documentation applies to the following versions of Splunk® Enterprise: 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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