search
Tonic.ai

Databricks connection troubleshooting

For issues with connecting to Databricks, here are some suggested troubleshooting steps for self-hosted instances.

hashtag
Retrieving driver logs

If a connection test fails, and you have ruled out other issues such as network access and user permissions, another place to look is the driver logs.

You can send these to Tonic.ai for the support team to use to identify the problem.

To retrieve the driver logs:

  1. Set the environment setting TONIC_LOG_TRACES to true. Changes to this setting require a restart of Structural.

  2. Set the environment setting TONIC_DATABRICKS_ODBC_LOG_LEVEL to 6. You can configure this environment setting from the Environment Settings tab on Structural Settings.

  3. In the workspace settings, test the data connection.

  4. To retrieve the logs:

    1. Open a shell in the Tonic Structural web server container.

    2. Locate the driver logs in the following folder: /var/log/simba

After you retrieve the logs, set TONIC_DATABRICKS_ODBC_LOG_LEVEL back to 0.

hashtag
Running an isql test command

If a connection test fails, and you suspect a networking issue, then you can use an isql test command to check whether the Structural container can connect to the Databricks host.

Before you do this, verify that there isn't a permissions issue.

To run the isql test command:

  1. Open a shell in the Tonic web server container.

  2. Get the host, HTTP path, and password (Personal Access Token) for the Databricks connection.

  3. Run the following command:

If the command succeeds, then you can rule out networking issues related to the ability to access the Databricks host from the Structural container.

If the isql command is not successful, you next check for other network issues that could block the connection, such as issues with:

  • HTTP path

  • IP address allow lists

  • NAT gateways

  • Proxies

  • DNS resolution

Last updated

Was this helpful?