- Apps and Add-ons
- :
- All Apps and Add-ons
- :
- Re: DBConnect "cannot communicate with task server...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk 7.2 running on Ubuntu. I specified /usr/lib/jre1.8.0_191.... tried ports 9998 and 1025.
Cannot communicate with task server, please check your settings
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Lmfao, here's the answer.
So in the newer 3+ versions of DBConnect (by new, I mean multiple years old and somehow someone thought it was unacceptable NOT to do anything about it), you need to specify the JDK path, not JRE. Forget the fact that every version of DBconnect ever has pointed to the JRE, and forget the fact that it literally says to enter the "JRE Installation Path." Here's a suggestion: maybe the configuration shouldn't ASK for the JRE path?? It literally says JRE Installation Path. Just edit one line of your code guys.
Second, that still didn't fix the problem. It gave me the same error message after trying it with the JDK. You need to magically know that, despite getting an error message, despite it telling you it was unable to save your settings or start the task server, everything is actually okay. If you reboot Splunk DBconnect will now be configured.
#logic
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There might be the issue with httpinput app. check the folder- $SPLUNK_HOME/etc/apps/htttp_input. Make sure this directory is available.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Lmfao, here's the answer.
So in the newer 3+ versions of DBConnect (by new, I mean multiple years old and somehow someone thought it was unacceptable NOT to do anything about it), you need to specify the JDK path, not JRE. Forget the fact that every version of DBconnect ever has pointed to the JRE, and forget the fact that it literally says to enter the "JRE Installation Path." Here's a suggestion: maybe the configuration shouldn't ASK for the JRE path?? It literally says JRE Installation Path. Just edit one line of your code guys.
Second, that still didn't fix the problem. It gave me the same error message after trying it with the JDK. You need to magically know that, despite getting an error message, despite it telling you it was unable to save your settings or start the task server, everything is actually okay. If you reboot Splunk DBconnect will now be configured.
#logic
Splunk Platform | Upgrading your Splunk Deployment to Python 3.9
From Product Design to User Insights: Boosting App Developer Identity on Splunkbase
Detect and Resolve Issues in a Kubernetes Environment
