-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mash-authentik-server.service was not detected to be running #117
Comments
Can you add the output of |
Not OP, but I believe I have the same problem. This is what
Directly followed by:
And this from PostgreSQL:
It looks like it is this problem: goauthentik/authentik#8863 But different from what goauthentik/authentik#8863 (comment) suggests, when installing using mash-playbook, authentik never seems to recover from that error. The process seems to just terminate and never making any progress, not even after repeated restarts. |
I did some digging in the Authentik source code and it looks like there's a rather brittle database migration in https://github.com/goauthentik/authentik/blob/main/lifecycle/system_migrations/tenant_to_brand.py It assumes: "If there's any previous migration run, but no migration for It seems that the playbook somehow created a partial database, where this assumption is wrong. To fix it, I entered the mash-postgres container and just dropped the Authentik database. After that |
systemctl status mash-authentik-server.service
The text was updated successfully, but these errors were encountered: