Can some on help to solve this issue, I have installed DB connect on Splunk enterprise after launch the apps I am getting following error message
Error: Can not communicate with task server, please check your settings.
JDK 8 is installed
I have followed the following article but does not help me
I have gone though all the answers and done all required changes in config but nothing will happend.
Finally, I use below steps to reslove this issue.
check your db it will be okay now.
Happy Splunking !..
DBConnect 3.3.1 Initial Setup Encountering "cannot communicate with task server" & python script error DBConnect has this issue our environment when a user’s setting for Time Zone is set to anything other than "–Default System Timezone-".
That's all folks!!!
I have the same problem. I can see that the task Server is properly responding at:
netstat -a -b
shows me, that the TaskServer is up and listening to the port. Maybe this might be helpful.
The splunkd.log is showing the following output after restarting Splunk:
ERROR ExecProcessor - message from
Which is not really helpful for me.
I did the change to 1025 - it didn't work. and I turned it again to 9998 - same result.
In both cases, when I start Splunk I have the following output:
[splunk@srvsplunk bin]$ ./splunk start Splunk> CSI: Logfiles. Checking prerequisites... Checking http port : open Checking mgmt port : open Checking appserver port [127.0.0.1:8065]: open Checking kvstore port : open Checking configuration... Done. Checking critical directories... Done Checking indexes... Validated: _audit _internal _introspection _telemetry _thefishbucket history main omega_ca_nt omega_ds omega_ds_idx_01 omega_nt_ora summary Done Checking filesystem compatibility... Done Checking conf files for problems... Invalid key in stanza [dbx_java_installation_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 17: doc_title (value: DB Connect JVM installation). Invalid key in stanza [dbx_driver_installation_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 41: doc_title (value: DB Connect JDBC Driver installation). Invalid key in stanza [dbx_connections_configuration_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 69: doc_title (value: DB Connect connection configuration,DB Connect identity configuration). Invalid key in stanza [dbx_data_lab_configuration_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 85: doc_title (value: DB Connect input configuration,DB Connect output configuration,DB Connect lookup configuration). Invalid key in stanza [dbx_java_server_configuration_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 98: doc_title (value: DB Connect Java Server configuration). Your indexes and inputs configurations are not internally consistent. For more information, run 'splunk btool check --debug' Done Checking default conf files for edits... Validating installed files against hashes from '/opt/splunk/splunk-6.5.2-67571ef4b87d-linux-2.6-x86_64-manifest' All installed files intact. Done All preliminary checks passed. Starting splunk server daemon (splunkd)... Done [ OK ] Waiting for web server at http://127.0.0.1:8000 to be available........ Done If you get stuck, we're here to help. Look for answers here: http://docs.splunk.com The Splunk web interface is at http://srvsplunk:8000
the very strange thing on the above - is that the startup problems DO NOT appear with the 9998 port as an original setting after the DB Connect App Install, but they DO appear even when the port is set again to 9998 (after trying 1025).
thank you, but how can this be performed when I am re-directed to the URL?
which then hangs. the original (title) message "Can not communicate with task server, please check your settings." - I can fully see only with a Print-screen to Bmp
ps. and I did all on the URL given above to no result
Any updates to this problem. I am facing a similar issue in Mac Env. The Splunk Enterprise version is crashing and indicating that it is not able to communicate with the Task Server.