You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "akzincsystems (via GitHub)" <gi...@apache.org> on 2024/03/12 16:29:04 UTC
[I] Failure to connecto to Trino [superset]
akzincsystems opened a new issue, #27481:
URL: https://github.com/apache/superset/issues/27481
### Bug description
Following instructions at https://superset.apache.org/docs/databases/trino/ to create a Trino DB connection fails with errors
### How to reproduce the bug
1. Go to DB admin in Superset
2. Add new Database, Select Trino
3. Add trino://trino@host.docker.internal:8080 as the URI
4. Click Connect. Get errors
I have also tried with using the IP of the trino server (running in another docker container)
url: trino://trino@172.18.238.40:8080
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Firefox
### Additional context
Trino python requirement met in docker/requirements-local.txt
`trino`
log entries from trying to connect to trino://trino@host.docker.internal:8080
```
2024-03-12 15:53:36,897:DEBUG:superset.stats_logger:[stats_logger] (incr) test_connection_attempt
2024-03-12T15:53:36.907803583Z 2024-03-12 15:53:36,907:DEBUG:superset.models.core:Database._get_sqla_engine(). Masked URL: trino://trino@host.docker.internal:8080
2024-03-12T15:53:36.908761089Z 2024-03-12 15:53:36,908:DEBUG:tzlocal:/etc/timezone found, contents:
2024-03-12T15:53:36.908774515Z Etc/UTC
2024-03-12T15:53:36.908778045Z
2024-03-12T15:53:36.909230727Z 2024-03-12 15:53:36,909:DEBUG:tzlocal:/etc/localtime found
2024-03-12T15:53:36.911009289Z 2024-03-12 15:53:36,910:DEBUG:tzlocal:2 found:
2024-03-12T15:53:36.911028513Z {'/etc/timezone': 'Etc/UTC', '/etc/localtime is a symlink to': 'Etc/UTC'}
2024-03-12T15:53:36.913787430Z 2024-03-12 15:53:36,913:DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): host.docker.internal:8080
2024-03-12T15:53:36.980169376Z 2024-03-12 15:53:36,979:DEBUG:urllib3.connectionpool:Starting new HTTP connection (2): host.docker.internal:8080
2024-03-12T15:53:37.144343853Z 2024-03-12 15:53:37,144:DEBUG:urllib3.connectionpool:Starting new HTTP connection (3): host.docker.internal:8080
2024-03-12T15:53:37.657422366Z 2024-03-12 15:53:37,657:INFO:trino.client:failed after 3 attempts
2024-03-12T15:53:37.657860569Z 2024-03-12 15:53:37,657:DEBUG:superset.stats_logger:[stats_logger] (incr) test_connection_error.DBAPIError
2024-03-12T15:53:37.669486593Z 2024-03-12 15:53:37,669:DEBUG:superset.stats_logger:[stats_logger] (incr) db_creation_failed.SupersetErrorsException
2024-03-12T15:53:37.674472686Z 2024-03-12 15:53:37,674:DEBUG:superset.stats_logger:[stats_logger] (incr) DatabaseRestApi.post.error
2024-03-12T15:53:37.674488816Z 2024-03-12 15:53:37,674:DEBUG:superset.stats_logger:[stats_logger] (timing) DatabaseRestApi.post.time | 920.0662940274924
2024-03-12T15:53:37.675189870Z
```
Log entries from trying to connect to trino://trino@172.18.238.40:8080
```
2024-03-12 15:58:48,543:DEBUG:superset.stats_logger:[stats_logger] (incr) test_connection_attempt
2024-03-12T15:58:48.556825436Z 2024-03-12 15:58:48,556:DEBUG:superset.models.core:Database._get_sqla_engine(). Masked URL: trino://trino@172.18.238.40:8080
2024-03-12T15:58:48.559007485Z 2024-03-12 15:58:48,558:DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 172.18.238.40:8080
2024-03-12T15:59:03.173740470Z 2024-03-12 15:59:03,173:DEBUG:superset.stats_logger:[stats_logger] (incr) health
2024-03-12T15:59:03.174326423Z 127.0.0.1 - - [12/Mar/2024:15:59:03 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.88.1"
2024-03-12T15:59:18.592287726Z 2024-03-12 15:59:18,591:DEBUG:superset.stats_logger:[stats_logger] (incr) test_connection_error.SupersetTimeoutException
2024-03-12T15:59:18.612454029Z 2024-03-12 15:59:18,611:DEBUG:superset.stats_logger:[stats_logger] (incr) db_creation_failed.SupersetTimeoutException
2024-03-12T15:59:18.630726532Z 2024-03-12 15:59:18,630:DEBUG:superset.stats_logger:[stats_logger] (incr) DatabaseRestApi.post.warning
2024-03-12T15:59:18.630893546Z
```
### 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] Failure to connecto to Trino [superset]
Posted by "akzincsystems (via GitHub)" <gi...@apache.org>.
akzincsystems closed issue #27481: Failure to connecto to Trino
URL: https://github.com/apache/superset/issues/27481
--
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] Failure to connecto to Trino [superset]
Posted by "akzincsystems (via GitHub)" <gi...@apache.org>.
akzincsystems commented on issue #27481:
URL: https://github.com/apache/superset/issues/27481#issuecomment-1999148996
Figured it out.
Containers on different networks cannot see each other. You can either:
1. use the `docker network connect` command to join a container to a network
2. create an external link in your docker compose file to point at the external network and add that to container configuration e.g.
```
networks:
external_net:
name: <name_of_other_network>
external: true
services:
myservice:
networks:
external_net:
```
--
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] Failure to connecto to Trino [superset]
Posted by "akzincsystems (via GitHub)" <gi...@apache.org>.
akzincsystems commented on issue #27481:
URL: https://github.com/apache/superset/issues/27481#issuecomment-1993681217
Test connection button just sits and spins. The results above are from hitting the Connect button. No authentication is required, I can connect to Trino from Jetbrains IDE and via the Trino CLI (on my local host) just fine without authentication.
FYI I installed Superset with instructions from https://superset.apache.org/docs/installation/installing-superset-using-docker-compose and used the `docker compose -f docker-compose-non-dev.yml up` command to bring up the containers.
The Trino and supporting containers are spun up using a separate docker-compose.yml and use their own network configuration to put all the containers on static IPs in the subnet. I don't know if that is relevant?
--
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] Failure to connecto to Trino [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27481:
URL: https://github.com/apache/superset/issues/27481#issuecomment-1996425086
Well, that does provide some more context to go on... it's not the obvious things I hoped for. I wonder if @nytai might have any ideas here... I *think* he has some trino experience, in case there's a known peculiarity.
--
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] Failure to connecto to Trino [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27481:
URL: https://github.com/apache/superset/issues/27481#issuecomment-1992191277
Does the "test connection" button show success or failure in the DB connection modal?
Does your local Trino instance require authentication, perchance?
--
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