error messages in journal during first start / initialization

[marcelgsteiger]

I'm trying a new install of authentik 2026.5 in a rootless container using podman kube and a postgresql 18.4 server running in a different pod.

When I start the container with an empty database, I get several database errors for the table "authentik_tasks_workerstatus" that is obviously missing (see near the end of the attached log).

Later, I get additional errors about deadlocks in the database - perhaps these are related.

After waiting until the system stabilizes and then stopping the containers, the relation appears to exist and the deadlock errors do not appear anymore.

Moreover, I get messages about POSTGRES_PASSWORD not being defined - however, AUTHENTIK_POSTGRESQL__PASSWORD exists (filled from kube secrets) and the connection to the database works flawlessly.

Maybe this is just cosmetic - I am new to authentik and still learning.

Regards
Marcel

startlog.txt

[dewi-tik]

This looks like a startup race. The worker starts before database migrations have created the authentik_tasks_workerstatus table, then succeeds once migrations finish. Official deployments tolerate this through retries and health checks. As a workaround, start the server first, wait until migrations complete, and then start the worker.

The password warning is unrelated if PostgreSQL connects successfully.

[rissson]

As a workaround, start the server first, wait until migrations complete, and then start the worker.

I actually would not recommend that, since the worker does things that might be required to properly use the server, like applying blueprints.

Moreover, I get messages about POSTGRES_PASSWORD not being defined

Cosmetic, fixed in 2026.8.