Developing for Splunk Enterprise

Splunk DB Connect java_home stanza error

Recently installed Splunk DB Connect and the path to the JRE has been entered into the WebUI.

However on startup of the Heavy Forwarder it is installed on you get the following error

Checking conf files for problems...
Invalid key in stanza [java] in /opt/splunk/etc/apps/splunk_app_db_connect/local/dbx_settings.conf, line 2: javaHome  (value:  /usr/java/latest/jre).

Upon running btool you see:

$ splunk btool check --debug
Checking: /opt/splunk/etc/apps/splunk_app_db_connect/local/dbx_settings.conf
                Invalid key in stanza [java] in /opt/splunk/etc/apps/splunk_app_db_connect/local/dbx_settings.conf, line 2: javaHome  (value:  /usr/java/latest/jre).
        Did you mean 'java_home'?
        Did you mean 'jvm_options'?

The contents of /opt/splunk/etc/apps/splunk_app_db_connect/local/dbx_settings.conf

javaHome = /usr/java/latest/jre

connector = INFO
dbinput = INFO
dboutput = INFO

Now I now the issue is simple to correct because looking at the spec of shows it should be java_home not javaHome, but we never set javaHome the settings of DBConnect did.
alt text

We have no active support contract so can't even report this as an issue it appears.

Was wondering if everyone is running into this issue?

NOTE: No environment variable for JAVA_HOME exists.


Hi - The issue is that the spec file is incorrect. The config checker looks for any options that don't have a match in the spec file.

If you change java_home to javaHome in etc/apps/splunk_app_db_connect/README/dbx_settings.conf.spec then "splunk cmd btool check" stops reporting the error.

The DBconnect app itself sets and expects to find an option called javaHome.

This issue has been corrected in the latest version of the app (3.1.3).


State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!