[Splunk DB Connect] PostgreSQL Inputs Not Working in Splunk DB Connect v3.9 [Invalid Connection Error]

Applicability

Description

The PostgreSQL inputs are not working on Splunk DB Connect version 3.9, whereas they were functioning correctly in version 3.7.

• In DB Connect 3.9, attempting to select the connection in the input configuration page results in an "Invalid connection" error in the Splunk UI.
• The connection can be saved successfully, but it still appears as an "Invalid connection" when selected.
• DB Connect 3.9 includes the db_connection_types.conf file containing the default JDBC URL used when configuring the connection.

Investigation

• The database connection was working correctly in Splunk DB Connect 3.7.
• This led to the following error:

  java.sql.SQLException: [Amazon][JDBC](11380) Null pointer exception.

   

  In DB Connect 3.7, there was no SSL parameter directly appended in the JDBC URL, so this issue did not occur. The db_connection_types.conf file lists the supported database types, driver parameters, and test queries. The file contains the specifications for database connection types.

Resolution

In DB Connect 3.9, the db_connection_types.conf file introduced a default JDBC URL configuration, which automatically appends ssl=true.

• Connection Configuration:

  • The connection was successfully saved after adjusting the JDBC URL configuration.
    

    Add ssl=false in JDBC URL

  • The error no longer appeared when selecting the connection in the input configuration page.

• SQL Query Execution Issue while configuring the input in Splunk DB Connect:

  • While executing an SQL query, the following error was encountered:
    

    database "database_name;ssl=false" does not exist

• To resolve this, the ssl=false parameter was removed from the JDBC URL and instead added separately in the parameters section.
• After making this change, the query executed successfully.