Postgres database is missing relations

[victor-at-square]

We're prototyping a self-hosted Langfuse solution with a RDS Postgres backend, and running into some errors related to missing relations in the database.

• We've verified that Langfuse is able to successfully connect to our RDS instance in our database logs.
• We're running langfuse/langfuse:2.
• We have a hacky startup script that is based on Langfuse's Dockerfile, which is not ideal but required for us to load some secrets from our Kubernetes setup into environment variables. (We have a secrets management setup that writes secrets as files in the Kubernetes pod, rather than environment variables. So we need to read from these files.)

My guess is that the startup script is the culprit, and we're missing a step to initialize the Postgres database instance. What can we do if we need to execute some custom script prior to running the Langfuse server?

#!/bin/sh

# ... Load some secrets into environment variables ...

echo "Configuring Postgres at $POSTGRES_HOST:$POSTGRES_PORT/$POSTGRES_DATABASE"

dumb-init -- node /app/web/server.js --keepAliveTimeout 110000

[dosubot[bot]]

Hey @victor-at-square! I'm here to assist you with any bugs, questions, or contributions you have for Langfuse. Let's work together to resolve this issue!

I found a similar discussion that might be helpful: Getting issue with local setup. The issue was resolved by running Langfuse locally via Docker Compose, which helped address Postgres connection configuration issues ^[1].

For your specific issue with missing relations in the Postgres database, ensure that the database schema is properly initialized. You can do this by running the necessary database migrations. Langfuse automatically applies migrations during container startup if the database schema has changed. You can also manually execute migrations using the command:

pnpm run models:migrate

Make sure your environment variables are correctly set, especially DATABASE_URL or the individual components like DATABASE_HOST, DATABASE_USERNAME, DATABASE_PASSWORD, and DATABASE_NAME. If your database user lacks the CREATE DATABASE permission, you might need to create a shadow database and configure the SHADOW_DATABASE_URL ^[2][3].

To continue talking to Dosu, mention @dosu.

[victor-at-square]

Overriding the entrypoint was indeed the issue. Configure environment variables and running the Langfuse container as-is fixed it.

[marcklingen]

Thanks for sharing. Is there a need for you to build the image yourself? In most cases that’s not necessary. We’re open for contributions if you want to push something upstream that might be interesting for other teams as well