-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
"error: database is closed" when running with SQLite backend in Kubernetes #4038
Comments
Best: 2 |
I've had a brief look into this. At a guess, when we reload the Teleport process (using |
I also found this kind of msg in my teleport running in Kubernetes |
@espadolini Do you think your recent fixes might have addressed this? |
Looks unrelated, nothing prevents the enforcer from being halfway through a call when we hit The latter is only called during a scram so it's not a big deal to have some errors, but for the former we need to tie a clean enforcer shutdown (which needs to be written) into the supervisor machinery, probably with an |
...or we could just catch "backend is closed" and swallow it, and stop there, as we can't possibly proceed anyway. |
What happened: A couple of customers have reported the same issues around running Teleport in Kubernetes with an SQLite backend.
Customer 1 (using their own Helm chart, the
Deployment
is functionally very similar to ours):Customer 2 (using our Helm chart):
What you expected to happen: No error.
How to reproduce it (as minimally and precisely as possible): Run Teleport in Kubernetes. Rest is as yet uncertain.
Environment
teleport version
):Customer 1:
Teleport 4.3.0
Customer 2:
Teleport Enterprise v4.2.7git:v4.2.7-0-gbc57b85f go1.13.2
The text was updated successfully, but these errors were encountered: