Closed gcarrarom closed 1 year ago
We had the same issue, we fixed it by setting pool_mode to session in the pgbouncer
We found out that we had not set use_pgbouncer
config option. Setting that helped and we could remove the pool_mode pgbouncer setting
Amazing! Thanks a bunch guys! For future reference, I've just added the following to the root of my values file for authentik k8s deployment:
env:
AUTHENTIK_POSTGRESQL__USE_PGBOUNCER: true
Description
I've upgraded Authentik from 2023.8.1 to 2023.8.2 and it came up with this error after the upgrade. There seems to be a cursor that wasn't committed to the Database during the upgrade and it's now not found when trying to read some data.
After the upgrade, the system seems to be working fine on all applications and authentication, but it will not show data properly when navigating to it. It is taking many refreshes to get data to appear on Authentik due to errors.
Here's an example when loading the user interface:
After a few refreshes, it just works:
Reproducing
I am not sure how to reproduce this, but I assume it's something of my environment.
It could be related to something else? Another way to reproduce the 500 errors is just loading the pages and it'll throw this exception from time to time - only happening after the upgrade to 2023.8.2:
Expected Behaviour
No exceptions and the database should self-heal in the case of exceptions as such.
Screenshots
Admin page load with missing information: Failing to load objects in the outposts: Outposts showing after clicking refresh a couple of times:
Logs
Version and deployment