Deadlock reported by database about authentik HOT 6 OPEN

Hello,

I had a similar issue.
I was trying to deploy a clean install of authentik and i was having this error.

I spent a couple of days trying to actually understand the issue but without success.

I was having issues reporting that the initial-setup page was not found and after a couple of changes i was able to get to the page to create the akadmin user but every time that i set a password i got another error.

The workaround i found it is quite peculiar but it worked.

I used the docker images as seen on the image above.

Started with the first release 2023.1.1 which worked without any issue.
I then used the image 2023.8.1 which is required before updating to the later version 2023.10.2 and where i believe the login has an issue as it did not require a password when login. This was reported on the post below.

https://github.com/goauthentik/authentik/security/advisories/GHSA-rjvp-29xq-f62w.

This issue was resolved on the version 2013.10.2.
I then used the version of 2024.2.0 which also worked and then proceeded to update it to the latest version 2024.4.2

Best Regards

from authentik.

Started with the first release 2023.1.1 which worked without any issue. I then used the image 2023.8.1 which is required before updating to the later version 2023.10.2 and where i believe the login has an issue as it did not require a password when login. This was reported on the post below.

https://github.com/goauthentik/authentik/security/advisories/GHSA-rjvp-29xq-f62w.

This issue was resolved on the version 2013.10.2. I then used the version of 2024.2.0 which also worked and then proceeded to update it to the latest version 2024.4.2

@excaliburzarau: Same issue for me and your solution helped!

from authentik.

I'm facing the same error message. I went from 2024.2.1 to 2024.2.2 to 2024.2.3 and now to 2024.4.2 where the error occurs. Running on Kubernetes K3S 1.26.10 with an Postgresl 16.1 database (cloudnative-pg).

from authentik.

I'm facing the same error message. I went from 2024.2.1 to 2024.2.2 to 2024.2.3 and now to 2024.4.2 where the error occurs. Running on Kubernetes K3S 1.26.10 with an Postgresl 16.1 database (cloudnative-pg).

Hello,

What actually worked for me was the progressive upgrade. I would suggest to start on the 2023.1.1 and then use the 2023.8.1 (which has a login bug when the login is bypasses). This has to BE done because it seems that you can not go directly to the 2023.10.2 but after that you can go to the 2024 Release.
I cannot tell you for sure if it Will work for you but it did work for me every time .

Best Regards

from authentik.

We are facing the same issue. I tried to go through the list above, but that didn't help.

from authentik.

If this is a clean installation i would ensure that the volumes/mountpoints were empty. It did happened once on the Second time i tried it. Cheers

from authentik.