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

Save database record fails #7503

Open
kleiven opened this issue May 14, 2019 · 6 comments

Comments

Projects
None yet
5 participants
@kleiven
Copy link

commented May 14, 2019

Error message when trying to save a database record. The database record is not saved and an error mesage is displayed. It is not possible to save a new database record or save changes in an existing record.

Expected results

  • I Expected that changes in the database record would be saved and changes shown in supersets list of added databases.
  • If I try to save a new database record, I expect the record to be created and the new database shown in the list of added databases.

Actual results

After pressing "Save" in the "Add database" view (/databaseview/add) I am redirected to /databaseview/list/ and the following error is displayed on top of the page:
"Error 111 connecting to localhost:6379. Connection refused."

The SQLAlchemy URI I am trying to add is of type: presto://
However, the same error was given when trying to add a postgres url as well.

In the add database form I only filled in the follwing two form inputs:

  • Database
  • SQLAlchemy URL.
    All other form fields were unaltered from their initial state.

How to reproduce the bug

  1. Go to '/databaseview/add'
  2. Fill in 'Test' to the form field 'Database'
  3. Fill in a url in the 'SQLAlchemy URI'
  4. Click on the "Save" button
  5. See error on top of page after redirect to /databaseview/list/

Environment

  • superset version: 0.32.0rc2
  • python version: 3.6.8
  • node.js version: v8.16.0
  • npm version: 6.4.1

Checklist

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

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

Other context

Superset runs in a kubernetes pod

@issue-label-bot

This comment has been minimized.

Copy link

commented May 14, 2019

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.95. 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 #bug label May 14, 2019

@kentore82

This comment has been minimized.

Copy link

commented May 14, 2019

Im also getting this.

superset version: 0.32.0rc2
python version: 3.6.8
node.js version: v8.16.0
npm version: 6.4.1

Attaching error message for context:
image

Ive tested with both Postgres and Presto, both with Asynchronous Query Execution = false. Test connection checks out fine.

From the port number 6379 this looks related to Redis and async query execution, however this is stange since I dont have this configured, neither in superset config or in the datasources Im trying to add.

Have worked around this for now by adding the datasource directly to the superset backend db.

Any advice?

@mistercrunch

This comment has been minimized.

Copy link
Contributor

commented May 14, 2019

Is there a stack trace on the web server logs?

@villebro

This comment has been minimized.

Copy link
Contributor

commented May 15, 2019

I am unable to replicate on 0.32rc2. Any additional info would be helpful.

@new2itall

This comment has been minimized.

Copy link

commented May 15, 2019

I think I'm confused....what are yoir tryong to figire out

@kentore82

This comment has been minimized.

Copy link

commented May 16, 2019

Sorry for the missing logging info, but I dont see any. No errorlog or stacktrace in the webserver logs. (logging mode DEBUG). :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.