-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Navigating to tablemodelview from the Welcome screen causes Superset app to crash hard #2525
Comments
Where's the stacktrace? Without it there's no crash. |
those were the only logs I could get while following the container as it dies. Its very similar to the two issues below but localized to a single page and only when the proxy fix is enabled. |
hello, has anyone been able to check this one out? i see it was flagged and then un-flagged. I can share minikube instructions if you are interested. thanks. |
I do have some additional information on the issue. the /queryview/list page has the same problem. as the tablemodelview page. Also, interestingly if I FIRST go to the /databaseview/list page, then go to the /tablemodelview/list or the /queryview/list page it WONT crash. I suspect the some session information isn't getting passed properly to these views like they are with the databaseview, slices. |
More information: I can now reproduce this without PROXYFIX enabled or behind an NGINX proxy. It can be reproduced with ANY additional middleware passed in from superset_config.py. My example:
|
You need to provide a stack trace or a paste of the Flask debug page |
@mistercrunch sorry. The log above is the full output from the debug. No stack trace is produced. The process just dies after that last line. |
@mistercrunch I've got it to stop... finally. And only by trial and error. I could not get any better logging to show up. Would love some logging tips, I'm capturing everything from stdout which appears to be the normal debug and flask messages. Anyhow, I've been using the community docker file for superset here: This runs a python at version 3.6. Looks like most of the QA for superset is done on 3.4 and 3.5. So, I built my own using alpine 3.5... and boom... it no longer crashes when going to those views with middleware enabled. Here is the resultant dockerfile:
|
Glad you got through this. |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.17.2
Expected results
Expected to be able to see from navigating from the welcome page
http://superset.local/tablemodelview/list/
Actual results
Superset Container crashes and 502 Gateway error returned from k8s ingress nginx proxy
Steps to reproduce
ADDITIONAL INFO:
Python stacktrace literally shows nothing before the crash. The container/process fails hard and kubernetes immediately restarts the container.
If I navigate to the tablemodelview from the databseview or the slicesview there is no crash.
Stack trace with DEBUG = TRUE and SILENCE_FAB = FALSE
The text was updated successfully, but these errors were encountered: