Hi,
I have 2 Splunk servers with Splunk App DB Connect installed - version 3.1.3 on both. Teradata driver is the same on both as well (terajdbc4.jar v15). All next steps are done in GUI - I have created an identity. When trying to set up a connection to the db server, from one Splunk server it is successful, but from the second one not. There is an error message:
There was an error processing your request. It has been logged (ID a306ca754260b3d5).
going further, in splunk_app_db_connect_server.log I have found this ID:
2020-02-06 11:21:30.135 +0100 [dw-78 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: a306ca754260b3d5
java.lang.NoClassDefFoundError: Could not initialize class com.teradata.tdgss.jtdgss.TdgssManager
The db host is accessible from both Splunk servers directly.
I have updated the Teradata driver to the latest version on not working one, but it did not help, the error is still the same.
Can anyone advise, why is that? What else can be different between these two Splunk servers that one works fine with this specific db server and the second not?
Thank you in advance,
Przemek
The error indicates that the particular class is not available in java classpath
check that you have both terajdbc4.jar AND tdgssconfig.jar installed correctly in different directories:
terajdbc4.jar to the $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers
tdgssconfig.jar to the $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers/terajdbc4-libs
Reload the driver under Settings>Drivers.
The error indicates that the particular class is not available in java classpath
check that you have both terajdbc4.jar AND tdgssconfig.jar installed correctly in different directories:
terajdbc4.jar to the $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers
tdgssconfig.jar to the $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers/terajdbc4-libs
Reload the driver under Settings>Drivers.
Thanks, really tdgssconfig.jar was missing on not working one (no idea why). But reloading drivers was not enough, after splunk restart it started to work.
Many thanks!