-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Unhandled exception on failed DB connect - exception should be handled. #26744
Comments
on master the WSOD should now be replaced with a string containing the actual error message. Maybe we should backport that fix |
Great, that was a fast fix! :) |
Hmm, now looking at it I'm not 100% sure if it would fix this use case: #26075 |
Hm, honestly I don't understand the purpose of #26075.. |
The purpose is simple: in some code path an error happens so early that the whole templating/logging system could not be initialized. Without these two it is impossible to use them to either render a nice error page or log an error in the log file. So without the fix it would just throw the exception and not print it anywhere: white page. With the fix at least the exception is caught and printed as a plain text within that white page. Hope that explains it. Since you mentioned a white page I suspect that the DB error also occurs quite early so the template system isn't loaded yet when the exception comes, so I think the PR would also catch it. Needs testing. |
I have tested this on stable9.1 and master with a failing Mysql connection (I shut down the server). I can confirm that instead of a white page the exception now appears directly on that page. |
that is, fixed on master |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi,
while migration an OC instance to another machine, I did everything correct (as it turns out) except adapting the PostgreSQL databad credetials for the new database. Yes I know, very stupid and unneccessary mistake.. shame
However, it took me a while to discover it since calling my new OC webinterface ended without any comment in Logfiles with the WSOD.
At the end, I discovered the error using occ, that the database connection failed but was not handled. PLease find the callstack below
I suggest to add a failed postgres connect as a handled exception - I think I'm not the only one doing such stupid mistakes.
:)
Thanks!
Torben
Callstack:
The text was updated successfully, but these errors were encountered: