Skip to main content

FAQs

I can't find my answer in your docs and I still need help!#


No worries! You can open an issue in GitHub and we'll get back to you as soon as we can ๐Ÿ™‚

What metric types are there?#


Check out our metrics reference doc.

What dimension types do you support?#


Check out our dimensions reference doc.

I want to report a bug/request a feature#


Team work makes the dream work ๐Ÿ’ช If you want to report a bug or request a feature, open an issue in GitHub.

Installation error: invalid mount config for type "bind": bind source path does not exist.#


After running: docker compose up, if you get the error:

Error response from daemon: invalid mount config for type "bind":
bind source path does not exist: /tmp/seeker/dbt

This means you havenโ€™t set your DBT_PROJECT_DIR.

In your terminal, run the following (replacing the path with the path to your dbt project):

# Specify the path to your dbt project
# (i.e. the directory containing dbt_project.yml)
# You MUST use the absolute path (i.e no ../../myrepo)
export DBT_PROJECT_DIR=/Users/myuser/dbtrepo

Lightdash crashed! How can I find out what happened?#


If you launched via yarn start:

  1. Check the javascript console in your browser
  • Safari: opt-cmd-c
  1. Check the terminal where you ran yarn start
  • Errors from the dbt server will show in json blobs with a "state": "ERROR" flag
  • Errors from the Lightdash server are anything that doesn't look like a json blob

Command "docker-compose" not found#


When trying to launch Lightdash, if you get a docker-compose not found error message, this is likely because the Docker app isn't running.

Docker needs to be running on your device before you can launch Lightdash. To do this, just open the Docker app.

ECONNREFUSED error (port already in use)#


If you get an error message that looks something like: Couldn't connect to dbt: FetchError: request to http://0.0.0.0.:8580/jsonrpc failed, reason: connect ECONNREFUSED 0.0.0.:8580

This is likely because the 8080 port that is used to launch Lightdash locally is in use. To fix this error, run the following command in your terminal:

lsof -i tcp:8080 # this will find the process using 8080

You should see a bunch of things returned. You want to copy the PID that's listed, then run:

kill -9 <pid> # kills the process with the given PID (i.e. the one using 8080)

Could not connect to Lightdash server. The server may have crashed or be running on an incorrect host and port configuration.#


This means Lightdash couldn't connect to dbt. This is usually because dbt could not start properly.

dbt will fail to start if:

  • Your profiles.yml configuration is wrong (missing profile, syntax error, or file isn't found)
  • Your dbt_project.yml configuration is wrong (syntax error, dbt configuration error or file isn't found)

Finding the problem:

  1. Check the logs from the dbt process, you will likely find an informative message
  2. Can't see anything in the logs? Try running dbt debug in your Lightdash environment
    • For example: in docker you can run `docker run lightdash/lightdash /bin/sh -c 'cd /usr/app/dbt; dbt debug')

Lightdash timedout trying to connect to dbt. Is dbt running correctly?#


This means that Lightdash had to wait too long for dbt to respond. This could be because:

  • You're a bigquery user and use method: oauth in your profiles.yml file. Check that the Lightdash server can access credentials at ~/.config/gcloud
  • You're running dbt in a separate process using the flag LIGHTDASH_SPAWN_DBT=false. In this case please check whether the dbt process process is running correctly.
  • If neither apply please open an issue

I'm using an old version of dbt, is Lightdash supported?#


We only support dbt version 0.20.0. Before using Lightdash, please check your project is compatible with the latest version.