/opt/splunkforwarder/bin/splunk enable boot-start ... Unknown option: levels (chkconfig)

[ggrissom]

splunkforwarder-7.0.4-68ba48f99743-Linux-x86_64.tgz

uname -a
Linux HOSTNAME 4.4.143-94.47-default #1 SMP Thu Aug 9 12:47:15 UTC 2018 (6bff971) x86_64 x86_64 x86_64 GNU/Linux

cat /etc/SuSE-release
SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 3

This file is deprecated and will be removed in a future service pack or release.

Please check /etc/os-release for details about this release.

cat /etc/os-release
NAME="SLES"
VERSION="12-SP3"
VERSION_ID="12.3"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP3"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles_sap:12:sp3"

/opt/splunkforwarder/bin/splunk enable boot-start
Unknown option: levels
usage:
chkconfig -A|--allservices (together with -l: show all services)
chkconfig -t|--terse names
chkconfig -e|--edit names
chkconfig -s|--set [name state]... (configure services)
chkconfig -l|--list [--deps] names
chkconfig -L|--liston [--deps] names
chkconfig -c|--check name state
chkconfig -a|--add names
chkconfig -d|--del names
chkconfig -h|--help (print usage)
chkconfig -f|--force ... (call insserv with -f)
chkconfig [name] same as chkconfig -t
chkconfig name state... same as chkconfig -s name state
chkconfig --root= ... use as the root file system

[lakshman239]

Are you running as root or sudo user?

https://docs.splunk.com/Documentation/Splunk/7.2.4/Admin/ConfigureSplunktostartatboottime

[ggrissom]

Thanks for the feedback.

Running as root.

I originally followed the very link you provided for the forwarder installation.

The issue appears connected to the

chkconfig command called by:

/opt/splunkforwarder/bin/splunk enable boot-start

For some reason, option levels is not recognized as valid.

[nsommars]

chkconfig is (breifly explained) just a functionality that creates symlinks to the initscript in the different startup runlevel folders, and also provides an overview of what services that are started at different runlevels.

"runlevels" no longer exist for systems using systemd (or related init systems), so perhaps SuSE removed that option?

There is on the other hand no need to run the splunk script to make splunk start after boot....just use your systems built in auto start mechanisms and "point it" at the splunk binary $SPLUNK_HOME/bin/splunk

(the splunk enable boot-start functionality just creates a init script and, sets the runlevels for which splunk should run in that script and then use chkconfig with the same information to make the system changes at once.