-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Hi @sotazum, thank you for sharing this guide!
I’ve tried deploying Langfuse v3 on GCP using your Terraform configuration, and while the deployment completes successfully, I’m seeing some issues in the logs of the langfuse-worker container:
DEFAULT 2025-06-09T07:19:03.609124Z 2025-06-09T07:19:03.607Z error prisma:error
DEFAULT 2025-06-09T07:19:03.609136Z Invalid prisma.$queryRaw() invocation:
DEFAULT 2025-06-09T07:19:03.609143Z Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
DEFAULT 2025-06-09T07:19:03.609183Z 2025-06-09T07:19:03.608Z error prisma:error
DEFAULT 2025-06-09T07:19:03.609188Z Invalid prisma.evalTemplate.findMany() invocation:
DEFAULT 2025-06-09T07:19:03.609193Z Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
DEFAULT 2025-06-09T07:19:03.609379Z 2025-06-09T07:19:03.608Z error prisma:error
DEFAULT 2025-06-09T07:19:03.609383Z Invalid prisma.dashboardWidget.findMany() invocation:
DEFAULT 2025-06-09T07:19:03.609387Z Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
DEFAULT 2025-06-09T07:19:04.007735Z 2025-06-09T07:19:04.006Z error Error running background migrations Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
ERROR 2025-06-09T07:19:04.007780Z PrismaClientInitializationError: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5) at t (/app/node_modules/.pnpm/@prisma+client@6.3.0_prisma@6.3.0_typescript@5.4.5__typescript@5.4.5/node_modules/@prisma/client/runtime/library.js:112:2473)
DEFAULT 2025-06-09T07:19:04.007783Z 2025-06-09T07:19:04.006Z error Error upserting managed evaluators after 65063ms:
DEFAULT 2025-06-09T07:19:04.007789Z Invalid prisma.evalTemplate.findMany() invocation:
DEFAULT 2025-06-09T07:19:04.007796Z Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
DEFAULT 2025-06-09T07:19:04.007801Z 2025-06-09T07:19:04.006Z error Error upserting default model prices after 65136ms:
DEFAULT 2025-06-09T07:19:04.007805Z Invalid prisma.$queryRaw() invocation:
DEFAULT 2025-06-09T07:19:04.007811Z Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
DEFAULT 2025-06-09T07:19:04.007816Z 2025-06-09T07:19:04.006Z error Error upserting Langfuse dashboards after 65061ms:
DEFAULT 2025-06-09T07:19:04.007820Z Invalid prisma.dashboardWidget.findMany() invocation:
DEFAULT 2025-06-09T07:19:04.007826Z Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
It looks like the connection to the Postgres database isn't being established properly — all Prisma queries are timing out when fetching a connection from the pool.
What's strange is that the langfuse-web container works without any problems, so I doubt it's a network or environment variables issue. I also verified that I'm using the official docker image from Docker Hub, while for langfuse-web I built it directly from your repo.
Have you run into this issue before? Were you able to resolve it?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels