Getting Data In

DB Connect 3.1 Errors

linush
Engager

Our Splunk (6.2.2) is running on a Linux box. I downloaded Java JDK 1.8 131 and verified:

Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)

However, when I go to Health Check I see the following error:

Check                             Results
Java Server configuration         The bootstrap conditions of the Java Server fail.

and the detail error is:

The modular input to start the Java Server failed to be registered to Splunk

In app | Configuration | Settings, the error is:

Cannot communicate with task server, please check your settings.

I've also verified the port (9998) and it seems to be correct.

What could be the problem?

Tags (1)

jplumsdaine22
Influencer

By any chance are you running dbx on an indexer? By default the task server uses port 9998, which is also the default ssl input for an indexer.

You can modify the port the task server uses on the configuration -> settings page. Try port 9999 for example

0 Karma

natalienguyen
Explorer

Hi,
Did you ever figure this out? We're getting "The bootstrap conditions of the Java Server fail." as well.

0 Karma

tmccombs
Explorer

I have this same issue as well.

I tried to install 3.1.1 by itself alongside 1.1.7 We're ultimately trying to upgrade but can't because we can't get a copy of 1.2.2 from Splunk so far... yes we have a ticket on this. 😕

Getting this issue inside the Health Check along with a host of other problems I'm working on trying to resolve.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...