• What's New
  • What's new in Splunk 3.4
    • New Splunk forwarder and light forwarder applications
    • New Splunk desktop application
    • Support for Vista
    • Support for 64-bit Windows
    • Receiving enabled in Splunk with a Free License
• Known Issues
  • Known Issues for release 3.4.1
    • General issues and considerations
    • Search issues, including deprecated commands
    • Splunk Web issues and considerations
    • Windows-specific considerations and known issues
    • Distributed search issues and considerations
    • Configuration considerations and issues
    • Splunk Toolbar considerations and issues
    • API considerations and issues
  • Workaround for SSL configuration for users of Firefox 3
    • Background
    • Symptoms
    • Workaround
• Changelogs by Version
  • 3.4
  • 3.4.1
• Credits
  • Credits
  • APSW
  • boost
  • elementree
  • expat
  • fpconst
  • gadfly
  • libarchive
  • libiconv
  • libxml2
  • libxslt
  • log4py
  • numeric
  • openLDAP
  • OpenSSL
  • pcre
  • popt1.7
  • pyopenssl
  • pysqlite
  • python
  • pyxml
  • SOAPppy 0.11.6
  • sqlite
  • twisted
  • xmlwrapp 0.5.0
  • zope
  • zlib

3.4.1

The following issues have been resolved in this release of Splunk:

• An issue with incorrect timestamp extraction for MST timezone has been resolved. (SPL-17664)
• An issue with timezone offsets has been resolved. (SPL-16691)
• Various crashes related to shutdown of Splunk on Windows have been resolved. (SPL-17235, SPL-16960)
• An issue related to Windows logfiles being pre-populated with null characters (and the resultant data showing up in Splunk search results) has been resolved. (SPL-14682)
• Forwarders will now continue to try to connect to the Splunk receiver until network instability issues are resolved, instead of giving up when unable to resolve via DNS. (SPL-16707)
• An issue with the field extractor on Windows 2k3 has been resolved. (SPL-16346, SPL-16785)