Incubator-superset: Superset dashboard or no data loading after login

[swapnil-chenoa]

Even after successful docker-compose up with latest updates from master branch after login welcome page keeps loading no dashboards or no data can be seen.
Checked the logs for PostgreSQL in image no error or exception in logs.
Even executed docker-init.sh successfully.

Expected results

Superset should load default roles and dashboard after login.

Actual results

welcome page keeps loading after login, no dashboards or no data can be seen.

Screenshots

How to reproduce the bug

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Environment

(please complete the following information):

• superset version: superset version
• python version: python --version
• node.js version: node -v
• npm version: npm -v

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

• [x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
• [x] I have reproduced the issue with at least the latest released version of superset.
• [x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.93. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[dpgaspar]

Please post docker-init logs from the superset-init container

[swapnil-chenoa]

I run the docker-init command twice (considering resources not downloaded on first attempt) so in logs it says admin user already exists.
Please find attached logs.

superset-init.log

[dpgaspar]

ok, that seems more or less ok. Looking at the uploaded picture you provided it seems that the docker build step may have failed. Try issuing a docker-compose build first (after docker-compose down)

[TheMelter]

@swapnil-chenoa Are you sure you've waited for superset-node container to finish before loading page? Looks like you're missing JS files generated from webpack.

[swapnil-chenoa]

ok, that seems more or less ok. Looking at the uploaded picture you provided it seems that the docker build step may have failed. Try issuing a docker-compose build first (after docker-compose down)

Thanks for your response.
The docker build was successful with all 32 steps executed few container initialization failed so used docker-compose build command which was successful.

It took hours for 11th step to complete.

Step 11/32 : RUN cd /app/superset/assets && npm run build && rm -rf node_modules
---> Running in ec3cd24edd7d

[email protected] build /app/superset/assets
cross-env NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production webpack --mode=production --colors --progress
clean-webpack-plugin: /app/superset/assets/dist has been removed.
Starting type checking service...
Using 1 worker with 2048MB memory limit
92% chunk asset optimization OptimizeCssAssetsWebpackPluginBrowserslist: caniuse-lite is outdated. Please r 92% chunk asset optimization TerserPlugin

[flutterWang]

I met the same problem as yours, how do you resolve it

[swapnil-chenoa]

@swapnil-chenoa Are you sure you've waited for superset-node container to finish before loading page? Looks like you're missing JS files generated from webpack.

Thanks for your response.
Yes we waited for same even for log-in page resources didn't load.
If we missed something how to recover JS files from webpack.

[swapnil-chenoa]

I met the same problem as yours, how do you resolve it

No that issue not yet resolved.
We are looking for solution.

[flutterWang]

my superset-work is unhealthy, do you have the same situation ？

[swapnil-chenoa]

my superset-work is unhealthy, do you have the same situation ？

No. all were in healthy state.

[flutterWang]

the default username & password is admin & admin ?

[swapnil-chenoa]

the default username & password is admin & admin ?

Yes its written in docker-init.sh.

[flutterWang]

I used cd superset/assets \ && npm install \ && npm run build \ && rm -rf node_modules to resolve it, but i met another problem：

[dpgaspar]

@flutterWang you have to wait for the superset-init to finish, it takes a while since it's upgrading the db, and downloading all the data for the examples dashboards

[flutterWang]

@dpgaspar

but my superset-init has been exited, did this mean it was finish?

[dpgaspar]

seems like superset-init failed, can you post the full log?

[nabinkhadka]

This is happening to me as well on macosx

[craig-rueda]

@dpgaspar

but my superset-init has been exited, did this mean it was finish?

@flutterWang - looks like you were running this while github was having some issues, as you can see from the SSL error. Were you able to retry this at all?

[craig-rueda]

This is happening to me as well on macosx

@nabinkhadka - how much RAM are you allocating to your Docker VM? I'd recommend at least 4GB, as the default of 2 isn't enough to get Terser off the ground.

[nabinkhadka]

This is what I have. @craig-rueda

[craig-rueda]

Ok, I'll take a deeper look at this. I'm wondering if there's a way to disable Terser for local development 🤔 ...

[jpatdalton]

@nabinkhadka I looked into the issue you merged #8883 , as I had the same error message.. turns out I was missing webpack. npm update then retrying docker-compose up fixed the issue for me.

[gk1089]

I have noticed another aspect of this bug while trying out the dremio support update. I have installed the latest superset using pip git+https://github.com/apache/incubator-superset in a Ubuntu 18.04 VM with 8 GB RAM. I have followed the steps outlined at default installation instructions page https://superset.incubator.apache.org/installation.html

However, I played around with saved states of my VM and realized that if I skip the command flask fab create-admin, at least the login page comes up. But, of course without any default credentials and not having created any credentials, I am unable to login.

I hope this helps in someway.

[feroult]

@nabinkhadka I looked into the issue you merged #8883 , as I had the same error message.. turns out I was missing webpack. npm update then retrying docker-compose up fixed the issue for me.

That worked for me!

Outside docker, on your local repo, you should enter superset/assets/ folder and run npm update.

And the, as @nabinkhadka said run docker-compose up

[chongzixin]

@nabinkhadka I looked into the issue you merged #8883 , as I had the same error message.. turns out I was missing webpack. npm update then retrying docker-compose up fixed the issue for me.

That worked for me!

Outside docker, on your local repo, you should enter superset/assets/ folder and run npm update.

And the, as @nabinkhadka said run docker-compose up

superset/assets/ doesnt exist anymore. has it been renamed to something else?

[willbarrett]

@chongzixin yes, superset/assets/ has been moved to superset-frontend/

[righttracknana]

Hi all,
New to superset and your comments above have been really helpful.

I just downloaded superset yesterday and I am able to login without any errors but I am unable to view any charts or dashboards. I have run the npm update on superset/superset-frontend/
but still getting chart plugin errors when inspecting the code (screenshot attached).

Any help would be really useful.

[AramisN]

Just follow along with the Dockerfile configuration and your compose file and things will be OK.
you might get into some errors which I never bumped into and based on your resources(RAM+CPU) and your internet speed you will face delays, it will usually take about 1 hour to install cause lets face it, you are basically running 4 or 5 services and each will interfere with each other, if you wait for all stages to finish and if you found any "unhealthy" status, just do the docker container restart [container-id] and what @jpatdalton said about running the image as a build not docker up.

but also, do the npm update, do the restarting and give your server some fermentation time :smile:

superset is a heavy software, it demands to check, restart and reboot a couple of times.

Good luck and thanks to the community.

[keehl1213]

I used cd superset/assets \ && npm install \ && npm run build \ && rm -rf node_modules to resolve it, but i met another problem：

I have the same problem. Have you resolved?

[EnixCoda]

If you get HTTP 401 errors from browser console, try remove admin accounts from superset's internal postgres database. (You'd need to know how to manipulate postgres)

I caught this error because I ran docker image pulled from docker hub before pull and run the source code version. And resolved that by removing up admin account and rerun docker-compose up

[stale[bot]]

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. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[superrrrrrrrL]

my superset-work is unhealthy, do you have the same situation ？

@flutterWang I met the same problem as yours, how do you resolve it

[pbegle]

This issue has not been resolved yet. I have more than 4GB of RAM allocated to Docker, I ran npm update in superset-frontend, I have waited over two hours after running docker-compose up and allowed all the images to finish installing packages and setting things up but still not getting anything to load after the login page. What is the magic trick do get a hello-world example running on MacOS? For reference, tried on MacOS 10.15.7. Getting this as output:

superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/theme.d16f7015.entry.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/theme.d16f7015.entry.js HTTP/1.1" 404 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/vendors.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:43] "GET /static/assets/vendors.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:44] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:44] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | 172.20.0.1 - - [21/Nov/2020 22:49:44] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.20.0.1 - - [21/Nov/2020 22:49:44] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -

[pbegle]

Upon further inspection, I noticed that the superset_node container died. Here is the tail of the logs for it:

<s> [webpack.Progress] 94% after asset optimization
<s> [webpack.Progress] 94% after seal
<s> [webpack.Progress] 95% emitting
<s> [webpack.Progress] 95% emitting fork-ts-checker-webpack-plugin
<s> [webpack.Progress] 95% emitting clean-webpack-plugin
<s> [webpack.Progress] 95% emitting ManifestPlugin
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! [email protected] dev: `webpack --mode=development --colors --debug --watch`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the [email protected] dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-11-21T22_04_07_103Z-debug.log
npm WARN using --force I sure hope you know what you are doing.
/usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js
/usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js
+ [email protected]
+ [email protected]
updated 2 packages in 7.314s
npm WARN using --force I sure hope you know what you are doing.

[keehl1213]

Upon further inspection, I noticed that the superset_node container died. Here is the tail of the logs for it:

<s> [webpack.Progress] 94% after asset optimization
<s> [webpack.Progress] 94% after seal
<s> [webpack.Progress] 95% emitting
<s> [webpack.Progress] 95% emitting fork-ts-checker-webpack-plugin
<s> [webpack.Progress] 95% emitting clean-webpack-plugin
<s> [webpack.Progress] 95% emitting ManifestPlugin
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! [email protected] dev: `webpack --mode=development --colors --debug --watch`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the [email protected] dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-11-21T22_04_07_103Z-debug.log
npm WARN using --force I sure hope you know what you are doing.
/usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js
/usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js
+ [email protected]
+ [email protected]
updated 2 packages in 7.314s
npm WARN using --force I sure hope you know what you are doing.

Status 137 is out of memory. Maybe 4 GB of RAM is not enough. My docker has 5 GB of memory and 3 GB of swap on windows 10. It works fine for me.

[anivon]

I had the same issue, in fact the container superset_node takes very long time for first npm-install (more than 20 minutes on my configuration)...
A tip if you want to check if still installing is to go into this container, then in /app/superset-frontend/node_modules or /app/superset-frontend/node_modules/.staging and do some ls -lah | wc -l. Normally, the number of folder will vary ;).