You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Musa10 (via GitHub)" <gi...@apache.org> on 2024/02/27 11:49:03 UTC
[I] redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused [superset]
Musa10 opened a new issue, #27267:
URL: https://github.com/apache/superset/issues/27267
### Bug description
Cannot connect to superset_cache container from superset_app container..although didn't change any thing in docker compose
### How to reproduce the bug
1. run docker compose up
### 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] redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #27267: redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused
URL: https://github.com/apache/superset/issues/27267
--
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] redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused [superset]
Posted by "michael-s-molina (via GitHub)" <gi...@apache.org>.
michael-s-molina commented on issue #27267:
URL: https://github.com/apache/superset/issues/27267#issuecomment-1969151796
Do you have another Redis instance running locally that would prevent the Docker one from running? Can you share the docker initialization logs?
--
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] redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27267:
URL: https://github.com/apache/superset/issues/27267#issuecomment-2218358259
Closing as stale. I assume you've either fixed this or moved on, but holler if there's still a bug to be dealt with. Docker has smoothed out quite a bit, so I hope/assume all is well.
--
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