
This document last updated: 10/06/08 09:10am
The 3.0 and 3.0.1 releases do not support automated migration from prior releases. Do not attempt this or you may overwrite your configuration files. Install and try the release in a separate file path with different ports. If you wish to migrate now, read about manual migration instructions.
System Requirements
Please check the release notes and download page for details on known issues.
Host Operating SystemYou can verify your installed version of Flash here
Server HardwareTo ensure that Splunk functions properly on FreeBSD ensure you have the following /boot/loader.conf:
kern.maxdsiz="2147483648" # 2GB kern.dfldsiz="2147483648" # 2GB
vm.max_proc_mmap=2147483647 machdep.hlt_cpus=0
Platform-specific installers come in both a package form and a tarball. The Linux build comes in three forms: RPM, deb and tarball. The FreeBSD installer and tarball are both .tgz files. 5.4-intel is the installer, i386 is the tarball.
Follow the instructions for your specific package or tarball.
RPMBasic install:
rpm -i splunk-2.1-0.i386.rpm
Override the default installation directory /opt/splunk:
rpm -i --prefix=/opt/splunk2.1/splunk splunk-2.1-0.i386.rpm
If you would like to verify the rpm package signature, you can find our GPG public key here.
debBasic install:
dpkg -i splunk-2.1-linux-2.6-intel.deb
The Splunk deb package currently cannot be installed in a directory other than its default, /opt/splunk.
Uninstall:
dpkg -r splunk
Purge (delete everything, even config files):
dpkg -P splunk
Splunk package status:
dpkg --status splunk
List all packages:
dpkg --list
Basic install:
pkg_add splunk-2.1-freebsd-5.4-intel.tgz
Override the default installation directory /opt/splunk:
pkg_add -v -p /usr/splunk splunk-2.1-freebsd-5.4-intel.tgz
Uninstall:
pkg_delete splunk
Uninstall from a non-default directory:
pkg_delete -p /usr/splunk splunk
Splunk package info:
pkg_info -L splunk
List all packages:
pkg_info
You need this in /boot/loader.conf:
kern.maxdsiz=\"2147483648\" # 2GB kern.dfldsiz=\"2147483648\" # 2GB
vm.max_proc_mmap=2147483647 machdep.hlt_cpus=0
Basic install:
Override the default installation directory /Applications/splunk:
Command-line install:
installer -pkg splunk.pkg
Command-line install to a different disk or partition:
installer -pkg splunk.pkg -target /Volumes/LaCie\ Disk
-target specifies a target volume, such as another disk, where Splunk will be installed in /Applications/splunk .
To install into a directory other than /Applications/splunk on any volume, use the graphical installer as described above.
Basic install:
pkgadd -d splunk.pkg
Override the default installation directory /opt/splunk:
pkgadd -a none -d splunk.pkg
And then specify the new package base directory when prompted.
Uninstall:
pkgrm splunk
Splunk package info:
pkginfo -l splunk
List all packages:
pkginfo
/opt/splunk/bin/splunk start
The first time you run a new installation, you will be prompted with a license agreement. You must accept the license terms to continue to use Splunk.
Splunk can run as any user on the local system. If you run Splunk as a non-root user you will need to ensure that Splunk has the appropriate permissions to read the inputs that you specify.
The first time you start splunk after a new installation, you will be presented with the license agreement and asked to accept the license. If you want to bypass these steps, you can start splunk and accept the license in one step:
/opt/splunk/bin/splunk start --accept-license
Please note: there are two dashes before the accept-license option.
2. Load the Splunk GUI in your browserhttp://mysplunkhost:8000
(or whatever host and port you installed)
(Use username "admin" and password "changeme" to login to your new Splunk installation for the first time.)
3. Set up one or more data inputsThe first time you browse a new installation, you will see a Guided Setup tool that helps you set up data inputs, licenses, and other configuration options. Alternately, you can configure data inputs from the command line. Below is a typical example.
/opt/splunk/bin/splunk add tail /var/log
Your Splunk Server should show indexed data on its home page immediately after you add a data input. As soon as you see a number greater than "0 events" listed on the server's home page, you're ready to start Splunking!
Step 3: Install your licenseIf you are performing a new installation of Splunk or switching from one license type to another (for example from Free to Enterprise), you must update your license. You can update your license from the CLI or SplunkWeb interface.
Note: This is for splunk 3.0 and 3.1, for earlier versions, see 2.2.3 instructions.
Using SplunkWebcp -p splunk.license /opt/splunk/etc/
When the correct license is in place, start or restart the Splunk Server.
/opt/splunk/bin/splunk restart
Splunk toolbar for Firefox is available from the following locations:



Splunk toolbar is available from the following locations:










We are still working on this topic for 3.0.
Configure Splunk to Start at System StartupStarting with version 3.1.1, Splunk provides a utility that will update your system boot configuration so that Splunk starts when the system boots up. This utility will create a suitable init script (or make a similar configuration change, depending on your OS).
As root, run
splunk enable boot-start
If you don't start Splunk as root, you can pass in the -user parameter to specify which user to start Splunk as. For example, if Splunk runs as the user bob, then as root you would run
splunk enable boot-start -user bob
If you want to stop Splunk from running at system startup time, run
splunk disable boot-start
More information is available in $SPLUNK_HOME/etc/init.d/README and if you type help boot-start from the command line.
If you are using a version that is older than 3.1.1, refer to the README in $SPLUNK_HOME/etc/init.d for instructions on how to modify your startup configuration so that Splunk starts up at boot time.
If Splunk is running as non-root, you must modify the startup script to use sudo. See Running as a non root user for more information.
Note: This is only true for versions older than 3.1.1. The boot-start command does this automatically with the -user flag.
Note: Splunk 3.0 has a new license format. Your Splunk 2.x license will not work with Splunk 3.0. Contact splunk support for a new license.
All Splunk Servers have a license in the subdirectory $SPLUNK_HOME/etc/splunk.license. There are two types of license; the Splunk Free license and the Splunk Enterprise license. Enterprise enables higher volume indexing and additional features. You must purchase a separate license for every instance of Enterprise Splunk that you deploy.
When you first install Splunk, you are allowed to run unlicensed for 30 days. After that you are asked to obtain a Free or Enterprise license. The free license simply requires you to register with Splunk. You are prompted to register when you first install and when you run Splunk unlicensed.
Example of a Splunk license:user@company.com;EQ/GQXW/J7u9VLJShPsW4m8yi+5a+geRrof4Bep70j32xsBpq JItM5pdntRfl4auply366BAjTMnfTB6JyzJOZLplyBQijk02fQjgKjakl0ol4N5G6Wr09ufnS e3iOXVAay24hzFfgDkaijOnkoGOPJqnHaVzaWC9dxIuKUvDPt3UcKTkDv0GkaQ4EZ xAvZKAFImvOF4PmDoNaMiBgLLkWibGhezFTTDh10PLl9kyeVThGzAyN23J512pVM 3xqNIg3pFcd2aJf31xspt1HRdSwofkfnuCVpzildy3qMbae4g85KpCfND+aJ6z2LoUu3 RQ4OV4SpxMXEZ4PgSGZ6dwA==
If you are performing a new installation of Splunk or switching from one license type to another (for example from Free to Enterprise), you must update your license. You can update your license from the CLI or SplunkWeb interface.
cp -p splunk.license /opt/splunk/etc/
/opt/splunk/bin/splunk restart
Use your local package management commands to uninstall Splunk. In most cases, files not originally installed by the package will be retained. This usually means your configuration and index files, which are under the same directory (default /opt/splunk) as the rest of the installation by default.
RedHat Linux# rpm --e splunk-2.1-0
Debian Linux# dpkg -r splunk
Solaris# pkgrm splunk
FreeBSD# pkg_delete splunk
In most cases, files not originally installed by the rpm package will be retained. This usually means the configuration and index files, which are under the same directory (default ///opt/splunk) as the rest of the installation by default.
Manual uninstallIf you can't use package management commands, these commands will remove the installed components except for any init scripts that have been created.
SplunkWeb has a button labeled Help in its upper right corner. Click this button to pop up a set of help pages.
Accessing help in the command line (CLI)From the command line on your Splunk Server host, type this command.
/opt/splunk/bin/splunk help
The best way to explore advanced features is to take the tutorial
You can also explore the command line interface using its inline help. Type $SPLUNK_HOME/bin/splunk help to get started.
I lost my Splunk.com password. What do I do?Use the recover password feature of the site to have your username and/or password emailed to the address on record.
How do I report problems?Submit your issue with on our online case submission form or email us at support@splunk.com.
How can I make suggestions?You can always send an email to our support team at support@splunk.com. Also check out our Live Roadmap where you can vote on upcoming features.
I have some questions that aren't answered here. Where can I get help?Start with our Documentation.
For help from experienced Splunkers, come to our Forums.
For help -- yes, it's free! -- from the Splunk Support team, submit an online support case (you must be a registered user and log in to use this service). You can also use our IRC support channel. The channel name is #splunk on the EFnet IRC (irc.efnet.org) network.
Splunk customers with an enterprise license get additional premium support options. For full information on our support offerings click here.
Installer options