Skip to content
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

Problem upgrading superset to 0.30 #8290

Closed
cpr88 opened this issue Sep 24, 2019 · 7 comments
Closed

Problem upgrading superset to 0.30 #8290

cpr88 opened this issue Sep 24, 2019 · 7 comments
Labels
!deprecated-label:bug Deprecated label - Use #bug instead inactive Inactive for >= 30 days

Comments

@cpr88
Copy link

cpr88 commented Sep 24, 2019

Superset version
0.27.0

Expected results
upgrading to 0.30.0

Actual results
Error when I try to open Dashboard, Charts, Tables.

Steps to reproduce
1- pip install --upgrade pip.
2- pip install superset --upgrade
3- superset db upgrade
4- superset init
5- superset runserver

Previously, I did pip uninstall superset.
image
image

@issue-label-bot
Copy link

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

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

@issue-label-bot issue-label-bot bot added the !deprecated-label:bug Deprecated label - Use #bug instead label Sep 24, 2019
@Demonya
Copy link

Demonya commented Sep 27, 2019

Hi,I find the same problem,and I kill pid of superset,And then can not found command:superset runserver。 when I try to start with command:superset run -p 8080 --with-threads --reload --debugger,I can not access to service even if there is no warning! Do you kown how to start service normally?Thank a lot!

@mulyadi
Copy link

mulyadi commented Sep 27, 2019

I did the same things that @Demonya listed.

  • Upgraded to 0.30.
  • Could not start Superset server because there is no superset runserver.
  • Ran superset run -p 8080 --with-threads --reload --debugger. The Superset server was not accessible anymore.

Also, in the installation documentation, it says port 8088, but the command above says port 8080.

@Demonya
Copy link

Demonya commented Sep 28, 2019

try command as follow:
GUNICORN_CMD_ARGS="--bind=0.0.0.0:8088 --workers=3" gunicorn superset:app
I can access to webserver,but still have other problems which may cause by my enviroment,Hope you can using normally!

@cpr88
Copy link
Author

cpr88 commented Sep 30, 2019

Hi! My superset is running on port 8088 and work fine. In fact, I can login into superset, but I cannot use Charts, Dashboards, and SQL Lab. I supose the problem is a version of Flask or SQL Alchemy dependency when I did the upgrade.

@stale
Copy link

stale bot commented Nov 29, 2019

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.

@stale stale bot added the inactive Inactive for >= 30 days label Nov 29, 2019
@stale stale bot closed this as completed Dec 6, 2019
@AasthaPoddar
Copy link

Was anyone able to solve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
!deprecated-label:bug Deprecated label - Use #bug instead inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

4 participants