Closed boesr closed 1 year ago
The only thing I could imagine causing issues with this is https://github.com/goauthentik/authentik/commit/95458570425223a82285bb3ea04ae233aedba54d, but that was reverted with 2023.8.2+
Thanks for the hint. I am going to investigate that further. At the moment I could see that when increasing the connection limit the pgbouncer option does work. At least till I logout and login again (sometimes twice). This leads to exceeding the postgresql connection limit. I try to increase that to have a walkaround till I find another solution.
I also tried so switch back to 2023.6.2. Then everything works again.
Couldn't fix the issue without setting the AUTHENTIK_POSTGRESQL__USE_PGBOUNCER=true
parameter.
I could increase the connection limit and the shared_buffers value to create a walkaround for the problem. Not quiet sure if it even is a walkaround or if it is necessary.
For others facing the same problem:
Seems like authentik in pgbouncer mode is able to open more connections than pgpool could handle in default, which leads to a freezing ui. I couldn't reproduce the error with that configuration.
Still no clue why the mode without pgbouncer isn't working anymore.
I think that could be closed for now since there is a way to fix it.
Seems like the walkaround does not work. It just delays the problem. It seems when using AUTHENTIK_POSTGRESQL__USE_PGBOUNCER=true
some connections won't be closed while new ones are opened leading to a freezing db / ui.
A restart of Authentik fixes that freeze.
@BeryJu I would keep that issue open and investigate that further. Maybe I can find a solution. I will update the issue if so.
Describe your question/ I am running Pgpool II before my database. It was working with version 2023.6.2, but now fails. When running with
AUTHENTIK_POSTGRESQL__USE_PGBOUNCER=true
the frontend loads all data once, but just hangs afterwards. PGpool shows an error, which indicates, that the frontend (Authentik) cannot use authentication methods offered by pgpool (see https://www.pgpool.net/pipermail/pgpool-general/2022-June/008262.html). Without that parameter I just get CSS written on the login page and the frontend isn't usable at all. The logs show the error below.Do I have to switch to certain authentication methods or what did change from 2023.6.2 to 2023.8.x regarding that fact?
Relevant infos 2023.8.3
Screenshots /
Logs
Error when not using PGBOUNCER parameter:
With the parameter pgpool shows the following in the log:
Version and Deployment (please complete the following information):
Additional context /