FATAL: database "admin" does not exist

[secsilm]

I see a lot of this error in docker logs: FATAL: database "admin" does not exist. Should I be worried about this error?

llm_monitor-postgres-1         | 2025-11-12 03:20:13.859 UTC [11250] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:16.991 UTC [11258] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:20.110 UTC [11267] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:23.242 UTC [11276] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:26.375 UTC [11284] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:29.498 UTC [11292] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:32.620 UTC [11300] FATAL:  database "admin" does not exist
llm_monitor-postgres-1         | 2025-11-12 03:20:35.757 UTC [11308] FATAL:  database "admin" does not exist

• langfuse version: 3.72.1

[inkeep-ai-assistant[bot]]

This error means something in your environment is trying to connect to a Postgres database named "admin", but that database does not exist on your Postgres server. Langfuse requires a Postgres database for its transactional data, but the expected database name and connection parameters should match what you configured for Langfuse itself(1)(2). As long as Langfuse is running as expected and the database it uses (typically specified by the DATABASE_URL or related environment variables) exists and is healthy, these log lines are likely caused by an unrelated service or a misconfigured client attempting to connect to "admin"(1)(2).

If Langfuse's main functionality is unaffected and you can access the UI, traces, and other features, you do not need to be worried about these errors for Langfuse itself. However, you may want to review your Docker Compose, Kubernetes, or other service configurations to identify what is attempting to connect to the "admin" database and either create that database if needed or correct the configuration so it targets the correct database(1)(2).

📚 Sources:

1. Postgres Database
2. Deployment Guide (v2)

---

Have another question? Just tag @inkeep.

[jannikmaierhoefer]

Hi @secsilm, was inkeep able to help you here?