Applying database migrations failed. This is mostly caused by the database being unavailable

[NanthagopalEswaran]

I used below docker_compose.yml file

services:
  langfuse-server:
    image: langfuse/langfuse:latest
    depends_on:
      db:
        condition: service_healthy
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgresql://postgres:postgres@db:5432/postgres
      - NEXTAUTH_SECRET=xxx
      - ENCRYPTION_KEY=yyy
      - SALT=zzz
      - NEXTAUTH_URL=http://localhost:3000
      - TELEMETRY_ENABLED=false
      - LANGFUSE_ENABLE_EXPERIMENTAL_FEATURES=false

  db:
    image: postgres
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 3s
      timeout: 3s
      retries: 10
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
      - POSTGRES_DB=postgres
    ports:
      - 5432:5432
    volumes:
      - database_data:/var/lib/postgresql/data

volumes:
  database_data:
    driver: local

database launched successfully and is active.
but langfuse server immediately exists with segmentation fault error

docket containers view:

langfuse-server-1 error log:

[dosubot[bot]]

Hey there, @NanthagopalEswaran! I'm Dosu, a bot here to help you with bug fixes, questions, and becoming a contributor. Let's tackle this issue together while we wait for a human maintainer.

The segmentation fault error in the langfuse-server container after database migrations fail is likely due to an invalid ENCRYPTION_KEY environment variable. The ENCRYPTION_KEY should be a valid 32-byte hexadecimal string.

To resolve this issue, generate a valid 32-byte hexadecimal encryption key using the command openssl rand -hex 32 and update the ENCRYPTION_KEY environment variable with the generated value.

Additionally, ensure that the DATABASE_URL and other environment variables are correctly set. Here is an updated version of your docker-compose.yml file with a placeholder for the valid encryption key:

services:
  langfuse-server:
    image: langfuse/langfuse:latest
    depends_on:
      db:
        condition: service_healthy
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgresql://postgres:postgres@db:5432/postgres
      - NEXTAUTH_SECRET=xxx
      - ENCRYPTION_KEY=your_valid_32_byte_hex_key # Replace with a valid key
      - SALT=zzz
      - NEXTAUTH_URL=http://localhost:3000
      - TELEMETRY_ENABLED=false
      - LANGFUSE_ENABLE_EXPERIMENTAL_FEATURES=false

  db:
    image: postgres
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 3s
      timeout: 3s
      retries: 10
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
      - POSTGRES_DB=postgres
    ports:
      - 5432:5432
    volumes:
      - database_data:/var/lib/postgresql/data

volumes:
  database_data:
    driver: local

Make sure to replace your_valid_32_byte_hex_key with the actual key generated by openssl rand -hex 32.

For more details on environment variables and configurations, you can refer to the Langfuse documentation ^[1].

To continue talking to Dosu, mention @dosu.

[NanthagopalEswaran]

@dosu, I just masked the passwords in above message. but I tried giving valid passwords for below keys.

• NEXTAUTH_SECRET
• ENCRYPTION_KEY
• SALT

[dosubot[bot]]

The langfuse-server container might still be failing with a segmentation fault error due to an incorrect DATABASE_URL. The DATABASE_URL should point to the db service defined in the docker-compose.yml file, not to an IP address. The correct DATABASE_URL should be:

DATABASE_URL=postgresql://postgres:postgres@db:5432/postgres

Ensure that the DATABASE_URL in your environment variables is set correctly as shown in the docker-compose.yml file:

services:
  langfuse-server:
    image: langfuse/langfuse:latest
    depends_on:
      db:
        condition: service_healthy
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgresql://postgres:postgres@db:5432/postgres
      - NEXTAUTH_SECRET=xxx
      - ENCRYPTION_KEY=your_valid_32_byte_hex_key # Replace with a valid key
      - SALT=zzz
      - NEXTAUTH_URL=http://localhost:3000
      - TELEMETRY_ENABLED=false
      - LANGFUSE_ENABLE_EXPERIMENTAL_FEATURES=false

  db:
    image: postgres
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 3s
      timeout: 3s
      retries: 10
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
      - POSTGRES_DB=postgres
    ports:
      - 5432:5432
    volumes:
      - database_data:/var/lib/postgresql/data

volumes:
  database_data:
    driver: local

Using DATABASE_URL=postgresql://postgres:[email protected]:5432/postgres might cause connectivity issues, leading to the segmentation fault. Additionally, ensure that your Postgres database is at least version 12, as required by Langfuse, and that all necessary environment variables are correctly configured ^[1][2][3].

To continue talking to Dosu, mention @dosu.

[NanthagopalEswaran]

I found a similar discussion - https://github.com/orgs/langfuse/discussions/1336

I tried DATABASE_URL=postgresql://postgres:[email protected]:5432/postgres as well. got the same error.

[marcklingen]

the configuration here looks good and I cannot reproduce the issue. Can you delete the db volume and try again?

[solargoe]

Can reproduce, after one docker compose and several traces i get this error
docker compose up

[+] Running 1/1
 ✔ langfuse-server Pulled                                                                                                                                                                                                                                                                   1.7s 
[+] Running 3/3
 ✔ Network langfuse_default              Created                                                                                                                                                                                                                                            0.2s 
 ✔ Container langfuse-db-1               Created                                                                                                                                                                                                                                            0.2s 
 ✔ Container langfuse-langfuse-server-1  Created                                                                                                                                                                                                                                            0.2s 
Attaching to db-1, langfuse-server-1
db-1               | 
db-1               | PostgreSQL Database directory appears to contain a database; Skipping initialization
db-1               | 
db-1               | 2024-10-09 10:28:07.933 UTC [1] LOG:  starting PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
db-1               | 2024-10-09 10:28:07.934 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
db-1               | 2024-10-09 10:28:07.934 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db-1               | 2024-10-09 10:28:07.935 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db-1               | 2024-10-09 10:28:07.942 UTC [29] LOG:  database system was shut down at 2024-10-09 10:27:58 UTC
db-1               | 2024-10-09 10:28:07.949 UTC [1] LOG:  database system is ready to accept connections
langfuse-server-1  | Script executed successfully.
langfuse-server-1  | Prisma schema loaded from packages/shared/prisma/schema.prisma
langfuse-server-1  | Datasource "db": PostgreSQL database "postgres", schema "public" at "db:5432"
db-1               | 2024-10-09 10:28:13.031 UTC [42] LOG:  could not receive data from client: Connection reset by peer
langfuse-server-1  | 
langfuse-server-1  | 252 migrations found in prisma/migrations
langfuse-server-1  | 
langfuse-server-1  | Error: P3005
langfuse-server-1  | 
langfuse-server-1  | The database schema is not empty. Read more about how to baseline an existing production database: https://pris.ly/d/migrate-baseline
langfuse-server-1  | 
langfuse-server-1  | Applying database migrations failed. This is mostly caused by the database being unavailable.
langfuse-server-1  | Exiting...
langfuse-server-1 exited with code 1

[marcklingen]

Have a look here: prisma/prisma#21003 (comment)

Did you create the schema manually? Usually this issue does not come up when creating a new postgres database via docker compose for langfuse

[marcklingen]

were you able to resolve this?

[solargoe]

I downgraded to latest stable version, worked as expected Saulius Görlich Triplesense Reply Konsul-Smidt-Straße 14 28217 - Bremen - GERMANY phone: +49 421 365142-10 ***@***.******@***.***> www.reply.de<http://www.reply.de> www.triplesensereply.de<http://www.triplesensereply.de> [Triplesense Reply] On 18. Oct 2024, at 20:24, Marc Klingen ***@***.***> wrote: were you able to resolve this? — Reply to this email directly, view it on GitHub<#3525 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIDCK24TDGBVNHUN54OJZC3Z4FG7DAVCNFSM6AAAAABPBTTEP2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJYGY4DCMY>. You are receiving this because you commented.Message ID: ***@***.***>

…

________________________________ Triplesense Reply GmbH Sitz/Registered Office: Frankfurt am Main Handelsregister/Register of Companies: Amtsgericht Frankfurt am Main, HRB 48863 Geschäftsführer/Managing Directors: Dr. Oliver Bohl, Thorben Fasching, Guiscardo Pin

[marcklingen]

awesome, thanks for sharing