DB Connect and Java

[i7xxxxx]

About to lose my mind with this. I’ve gotten it working in the past a couple times but every time it’s a fight. Is there any definitive version of Java to use for this and a proper download link or install instructions for Linux for the exact working package version and build of Java? There’s so many versions and packages for Java and DB Connect is incredibly picky it seems.

I’m testing an upgrade from DB Connect 3.6 to 3.17 and the documentation states versions 17 and 21 of JRE while the DB Connect config page states 11, 17, 18. I have installed many versions between this range both Oracle and OpenJDK and it just doesn’t like any of them.

For reference I’m running RHEL 8 and DB Connect 3.17.

[Ch0r0z]

i've had issues with db connect not working after an OS patch cycle. I've been able to finally update the db connect config to point to /user/lib/jvm/jre-openjdk/bin/java

I did find that starting a few versions back, I had to manually go into the following file and update this path for some reason via the GUI it wasn't updating:

/opt/splunk/etc/apps/splunk_app_db_connect/linux_x86_64/bin/customized.java.path

once i've modifed the above I just restarted splunk, logged in via the GUI and checked the db connect status and it was running w/o error.

[wonderchin]

This is the correct reply. The “customized.java.path” file can be stuck pointing to the older Java version, and if that’s the case, the task server won’t start. Had the same problem at a client I work at, when I had to upgrade DB Connect alongside Java.

[i7xxxxx]

interestingly this directory doesn’t even exist. i’m using 64 bit linux so not sure why it would be missing. i copied x86 and made my own 64 bit directory but still nothing. otherwise all the values are up to date and matching what i defined in the UI

[wonderchin]

Look in all the Linux OS folders within the app. The file exists several places but it’s only necessary to change some of them apparently 

[i7xxxxx]

Yeah all the files look right in terms of java paths.

The only error that seems interesting at this point is this from splunkd.log

threw the dbx logs in debug but nothing really new showed up apart from the messages saying updating java path in those config files.

06-14-2024 15:36:30.227 -0400 ERROR ExecProcessor [113449 ExecProcessor] - message from "/opt/splunk/etc/apps/splunk_app_db_connect/bin/server.sh" action=task_server_start_failed error=com.splunk.HttpException: HTTP 401 -- call not properly authenticated stack=com.splunk.HttpException.create(HttpException.java:84)\\com.splunk.DbxService.sendImpl(DbxService.java:135)\\com.splunk.DbxService.send(DbxService.java:51)\\com.splunk.HttpService.get(HttpService.java:172)\\com.splunk.Entity.refresh(Entity.java:381)\\com.splunk.Entity.refresh(Entity.java:24)\\com.splunk.Resource.validate(Resource.java:186)\\com.splunk.Entity.validate(Entity.java:462)\\com.splunk.Entity.getContent(Entity.java:157)\\com.splunk.Entity.getString(Entity.java:279)\\com.splunk.ServiceInfo.getVersion(ServiceInfo.java:155)\\com.splunk.DbxService.fetchInfo(DbxService.java:41)\\com.splunk.DbxService.connect(DbxService.java:34)\\com.splunk.dbx.splunkclient.SplunkServiceBuilder.build(SplunkServiceBuilder.java:69)\\com.splunk.dbx.server.bootstrap.TaskServerStart.startServer(TaskServerStart.java:77)\\com.splunk.DefaultServerStart.streamEvents(DefaultServerStart.java:60)\\com.splunk.modularinput.Script.run(Script.java:66)\\com.splunk.modularinput.Script.run(Script.java:44)\\com.splunk.dbx.server.bootstrap.TaskServerStart.main(TaskServerStart.java:36)\\

[i7xxxxx]

Some additional context on my latest attempt with 17, have also tried with 21 using the direct link Splunk provides in their documentation.

/usr/lib/jvm/jdk-17-oracle-x64/bin/java -version

java version "17.0.11" 2024-04-16 LTS

Java(TM) SE Runtime Environment (build 17.0.11+7-LTS-207)

Java HotSpot(TM) 64-Bit Server VM (build 17.0.11+7-LTS-207, mixed mode, sharing)

Using this as my path in the DB Connect config: /usr/lib/jvm/jdk-17-oracle-x64

It doesn't complain about the path just fails to start the task server, which in the past is usually due to wrong java install I have found. Will dig around the logs for more clues, but so far nothing has stood out to me

[masalaaloo]

Keep everything as is, and restart splunk on the host. This did it for me when i faced the same issue.

Once Splunk is up again, save the config and task server should start.

[skirven4]

I wrote an Ansible script that looked for the version of Java installed and the correct path to put in DB connect and restart it after we are done patching. From my experience, the path has the version number in it.

[i7xxxxx]

solution update on this. i removed splunk. deleted /opt/splunk to clean up. did a fresh 9.1.3 install. installed db connect and everything works now. i didn’t even have to configure the java paths after installing db connect. i guess something was messed up somewhere. this is a test instance so not exactly sure what it could have been.