You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "danielrosehill (via GitHub)" <gi...@apache.org> on 2024/04/28 17:21:30 UTC
[I] "There was an error connecting to the database." [superset]
danielrosehill opened a new issue, #28251:
URL: https://github.com/apache/superset/issues/28251
### Bug description
I know this issue has been described before but I thought I'd file it again - and to open source the solution in case I find it.
Connected several PostgreSQL databases and enabled CSV upload. For debugging, disabled limiting upload permissions to any particular scheme.
Although the DB connections seems to have succeeded, when I attempt to upload a CSV I get this error message:
### How to reproduce the bug
Installation was via Docker Compose on a Linux (Ubuntu) VPS.
The database connection is to an externally hosted PostgreSQL.
As basic initial debugging I made sure that all required ports were opened.
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] "There was an error connecting to the database" ... and general database connection woes! [superset]
Posted by "danielrosehill (via GitHub)" <gi...@apache.org>.
danielrosehill commented on issue #28251:
URL: https://github.com/apache/superset/issues/28251#issuecomment-2081571268
Ah .. well that was an easy "bug" fix ... max connections seem to have been set to -1 in my managed database (now to ask them why!).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] "There was an error connecting to the database" ... and general database connection woes! [superset]
Posted by "danielrosehill (via GitHub)" <gi...@apache.org>.
danielrosehill closed issue #28251: "There was an error connecting to the database" ... and general database connection woes!
URL: https://github.com/apache/superset/issues/28251
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org