Troubleshooting Installation Errors
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Contents
Troubleshooting Installation Errors
This page is a collection of error messages customers have reported during or after installing Splunk 2.1. If you encounter installation errors not covered on this page, please let us know at support@splunk.com or on our Support Forums.
Splunkd appears to be down
The usual cause at installation time is that the server host has no entry for localhost in /etc/hosts. Either add one, or edit this line in the file /opt/splunk/etc/myinstall/search.xml to replace localhost with 127.0.0.1 or a DNS-supported hostname.
<managerURL>``http://localhost:8089``</managerURL>
If this isn't the problem, see the full help page on Splunkd appears to be down.
useradd: warning: the home directory already exists
This message may appear if you install the Splunk Server over a previously uninstalled version that still retains a skeletal file structure. The message can be ignored. However, make sure you don't have both a $SPLUNK_HOME/etc and a $SPLUNK_HOME/etc.bak directory if you are trying to migrate to version 2.1. The migration process will use the configuration files in etc if they're still there, rather than migrating from etc.bak.
python: syntax error at line 1: `(' unexpected
You may have installed the wrong version of Splunk. Make sure you aren't trying to run the Solaris Intel version on a SPARC server.
FreeBSD memory constraint
Please be aware of the setting:
kern.maxdsize=4G
that should be present in
/boot/loader.conf
Without it, a Splunk instance that's using more than the usual amount of memory (e.g., has multiple user-defined indices, many files being tailed simultaneously) will experience severe performance porblems
This documentation applies to the following versions of Splunk: 2.1 , 2.2 , 2.2.1 , 2.2.3 , 2.2.6 View the Article History for its revisions.