-
Notifications
You must be signed in to change notification settings - Fork 887
Better error when database OOM or fails to connect (or other cases for cannot read properties of undefined: authMethods) #6983
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
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
Ok this doesn't happen on other platforms and seems to occur when the builtin postgres database runs into a OOM error. Our railway runs on very little resources. We should display a better error here. |
This may occur on other scenarios besides a database OOM but that is certainly one case. We should pretty much never show this specific issue and instead show info relevant to the Coder admin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into a scenario where my database was significantly under-resourced (and would OOM). This is the error I see from Coder:

Any idea how this happened? I deployed Coder using railway which @matifali is working on. Instructions here
The text was updated successfully, but these errors were encountered: