Monitoring Splunk

sh: btool: command not found

Path Finder

I have just installed Splunk 6.0.2 on Mac OS X 10.7.5 and am getting the following error when starting splunk:

bash-3.2# ./splunk start
sh: btool: command not found
sh: btool: command not found

Splunk> Take the sh out of IT.

Checking prerequisites...
sh: btool: command not found
    Checking mgmt port [8089]: sh: btool: command not found
open
    Checking conf files for typos...  execve: No such file or directory
        There might be typos in your conf files. For more information, run 'splunk btool check --debug'
    Checking conf files for typos...  execve: No such file or directory
    There was an error validating your search head pooling configuration. For more information, run 'splunk pooling validate'
    Checking conf files for typos...  execve: No such file or directory
    There was an error preparing your conf files for search head pooling. For more information, run 'splunk btool find-dangling'.
    Checking conf files for typos...    Done
sh: btool: command not found
sh: btool: command not found
All preliminary checks passed.

Starting splunk server daemon (splunkd)...  
Done

bash-3.2# ./splunk btool check --debug
execve: No such file or directory
bash-3.2# find / -name "*execve*"

The error has mainly to do with the btool command not being found as well as the execve directory.

As you can see I have already executed a search for the directory and tried to run the commands suggested after starting splunk from the command line.

Any help in resolving this would be great, I have already tried a re-install.

Tags (4)
0 Karma
1 Solution

Path Finder

Install Splunk 6.0.1 instead.

I took @Inguinn's advice and uninstalled Splunk 6.0.2 and installed 6.0.1.

This solved the above issues on Mac OS X 10.7.5

There appear to be a few bugs with the 6.0.2 installer for mac.

View solution in original post

0 Karma

Path Finder

Install Splunk 6.0.1 instead.

I took @Inguinn's advice and uninstalled Splunk 6.0.2 and installed 6.0.1.

This solved the above issues on Mac OS X 10.7.5

There appear to be a few bugs with the 6.0.2 installer for mac.

View solution in original post

0 Karma

Legend

Try downloading 6.01 instead - it looks to me like this is a flaw in the installation package.