topic Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance in Installation

Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

dbrown_sfdc — Thu, 03 Jan 2013 20:22:45 GMT

Our company has an Enterprise License for Splunk. We have scripted the install for upgrade and for fresh implementations of Splunk 5. However, the acceptance of the End User License agreement is causing our scripts to fail.

In versions prior to Splunk 5 we used the following commands from a shell script:

$SPLUNK_HOME/bin/splunk start --accept-license --answer-yes

Now it fails to accept the license during script run time.

Is there an updated command set to continue past the license acceptance?
Or..
Does anyone know of a scripted method to work around this problem?

Thank you!

Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

jcoates_splunk — Thu, 03 Jan 2013 20:42:10 GMT

here's my new-splunk.sh...

#!/bin/sh

# Support goofy Splunk homes... 
APPS=`echo $SPLUNK_HOME | awk 'BEGIN { FS="/"} {printf "/"; for(i=2;i<=NF-1;i++) printf $i "/"; printf "\n"}'`

#Download directory
. set_demo_home.sh
DOWNLOADS="$DEMO_SCRIPT_HOME/Downloads/"
LICENSE=`ls $DOWNLOADS*.license | sort -n | tail -n 1`

# get the latest version
if [ -e "/tmp/latestsplunkserver" ]
    then SPLUNK=`cat /tmp/latestsplunkserver`
fi

if [ ! -e $DOWNLOADS$SPLUNK ]
    then echo "Can't find Splunk at $DOWNLOADS$SPLUNK!"
    exit 1
fi

# Do the extraction
tar xzf $DOWNLOADS$SPLUNK -C $APPS

# if SPLUNK is not supposed to live in a folder called "splunk" we'll need to
# deal with that.
SPLUNK_FOLDER=`echo $SPLUNK_HOME | awk 'BEGIN { FS="/"} {print $NF}'`
if [ ! $SPLUNK_FOLDER = "splunk" ]
    then mv $APPS/splunk $SPLUNK_HOME
fi

DIR="$SPLUNK_HOME/etc"

# Need to uncomment and change SPLUNK_HOME from /opt/splunk to /Applications/splunk
sed 's/# SPLUNK_HOME/SPLUNK_HOME/g' < $DIR/splunk-launch.conf.default > $DIR/splunk-launch.conf
sed 's/opt/Applications/g' < $DIR/splunk-launch.conf.default > $DIR/splunk-launch.conf

# let's change a few default settings
fix-splunk-defaults.sh

# don't need deployment apps or Getting Started
rm -rf $DIR/deployment-apps
rm -rf $DIR/apps/gettingstarted
rm -rf $DIR/apps/sample_app

BIN="$SPLUNK_HOME/bin/splunk"

# handle licensing
$BIN start --accept-license
$BIN login -auth admin:changeme 
$BIN add licenses $LICENSE

echo "Splunk is refreshed now (NOTE: it still needs a restart)."

Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

tbarnard — Fri, 04 Jan 2013 00:17:55 GMT

This is what I use for my scripted installs.

/sbin/service splunk start --answer-yes --no-prompt --accept-license

Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

dbrown_sfdc — Mon, 07 Jan 2013 20:57:14 GMT

Does this work in version 5?

Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

dbrown_sfdc — Mon, 07 Jan 2013 20:58:17 GMT

This seemed to work. Does it work for version 5 in your environment?

Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

jcoates_splunk — Mon, 07 Jan 2013 21:00:24 GMT

yes, I'm using it in automated builds for some demo and test environments.

Re: Scripted Install fails for Splunk 5 due to End User License Agreement acceptance

jay007ant — Fri, 01 Feb 2013 18:14:05 GMT

Hi,
In versions prior to Splunk 5 I used the following commands from a shell script:
$SPLUNK_HOME/bin/splunk start --accept-license --answer-yes --auto-ports --no-prompt