-
-
Notifications
You must be signed in to change notification settings - Fork 900
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
Authentik will not boot anymore #6354
Comments
The same happened to myself when upgrading to 2023.8.1 (I had a quite outdated 2023.5.x version and now proceeded to upgrade aggressively). The error line seems to be the same in my scenario:
followed by gunicorn timeout error, rinse and repeat. |
Update: after doing a hundred upgrade-downgrade procedures and acomplishing nothing, I left the system broken and 20 minutes later the issue solved itself. Maybe the gunicorn timeout and the initialization time are close and you need a bit of luck? (I am running in a constrained kubernetes environment homelab, not very powerful). That is the only explanation I can come up with, but I really have no idea. |
I'm also on a rather constrained homelab and found a workaround for the initialization timeout. My environment started to do this a few days ago after running solid for about a month on this version and each gunicorn worker was hitting 100% cpu utilization during initialization. The restart of the workers would occur every 30 seconds and do it again (which is a gunicorn default timeout). To work around this, I reduced the number of workers via the Authentik environment variables and also used the following variable to tell gunicorn to wait longer (you can go higher than this, but probably keep it reasonable).
There is no specific Authentik env variable for this, so this will only work so long as something isn't passed directly into gunicorn via the command line (see the gunicorn config docs for priority), but I imagine the gunicorn.config.py file would be the place any defaults or overrides would be set in the future. A dedicated Authentik config var for slower systems would be great! |
This is the solution! Thank you very much! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
It seems that for whatever reason the Authentik core will not want to boot.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would have expected it to boot.
Logs
Version and Deployment (please complete the following information):
Additional context
It had been working fine ish, and now it's terminating due to signal 6 what ever that means..
The text was updated successfully, but these errors were encountered: