"Cannot communicate with task server" after upgrading DB Connect to v#3.10.0 or above

Applicability

Splunk Enterprise

Description

In Splunk DB Connect it is being noticed that task server is not being connected after upgrading it to v#3.10.0 or above.

Investigation

1. Check whether java it is being installed properly or not.
2. Check whether ports (9998 & 9999) are being allowlist.
3. Drivers needs to be installed.
4. Check KV store status by following running below command and if you find disable or failed kindly raise a core case for the same.

./splunk show kvstore-status

Note: Please makes sure that KV store is up and running before upgrading Splunk DB Connect to v#3.10.0 or above.

Resolution

The error/warn message indicates SSL certificate is expired and is not correct,

1. See the status of KV store by using the following command.

./splunk show kvstore-status 

2. Now create a new SSL certificate in the directory called $SPLUNK_HOME$/etc/auth. Run the below command to create an SSL certificate for this server.

./splunk createssl server -cert 3072 -d /opt/splunk/etc/auth -n server -c <FQDN>

3. Restart Splunk once.

./splunk restart

4. Now check the status of KV store again.

./splunk show kvstore-status 

Furthermore you can also try to create a new file (server.pem) which may fix your issue.
Note: If the above steps do not solve the issue then you will have to create a case to fix KV store issue. This will resolve your DB Connect task server issue. 

Related Links

https://splunkonbigdata.com/failed-to-start-kv-store-process-see-mongod-log-and-splunkd-log-for-details/

Revision History

Revision	Publish Date	Comments
1.0	29-Sep-2026	Initial Release