After upgrade to 5.0 (with docker-compose): failed to connect to server
See original GitHub issueEverything was working fine and we upgraded form v3 to v4 to v5 with the docker-compose upgrade command, and the redash UI is loading fine, but cannot execute any query.
The UI displays an error: Error running query: (psycopg2.OperationalError) could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
And the docker-compose logs shows the following:
redash-worker | [2018-10-15 10:40:30,331][PID:46][INFO][Worker-13] waiting tracker 14a3e1bd6ffb17fda50f3ef34071f77f finished
redash-worker | [2018-10-15 10:40:30,332][PID:46][INFO][Worker-13] waiting tracker e321600e578ecd0d5e4bbfd0cb7eb0a7 finished
redash-worker | [2018-10-15 10:40:30,333][PID:1][INFO][MainProcess] Task redash.tasks.cleanup_tasks[bd77acf9-104f-45f6-a037-b54e64f638fd] succeeded in 0.0124485739998s: None
redash-worker | [2018-10-15 10:40:30,377][PID:14][INFO][Beat] Scheduler: Sending due task refresh_queries (redash.tasks.refresh_queries)
redash-worker | [2018-10-15 10:40:30,380][PID:1][INFO][MainProcess] Received task: redash.tasks.refresh_queries[29fcf6b1-9873-425d-ac6e-0972299e6bd3]
redash-worker | [2018-10-15 10:40:30,381][PID:49][INFO][Worker-14] task_name=redash.tasks.refresh_queries task_id=29fcf6b1-9873-425d-ac6e-0972299e6bd3 Refreshing queries...
redash-worker | [2018-10-15 10:40:30,390][PID:1][ERROR][MainProcess] Task redash.tasks.refresh_queries[29fcf6b1-9873-425d-ac6e-0972299e6bd3] raised unexpected: OperationalError('(psycopg2.OperationalError) could not connect to server: No such file or directory\n\tIs the server running locally and accepting\n\tconnections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?\n',)
Any ideas? Thank you so much
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Docker-Compose Cannot Connect to Server w/ mysqli_connect
Simply updating the host name you're trying to connect to from 127.0.0.1 to database should be all you need to do.
Read more >How to Resolve the “cannot connect to the Docker daemon ...
1. First, check if the Docker engine is running: sudo service docker status · 2. If the Docker engine isn't working, start it...
Read more >[SOLVED] Docker Failed to Start - Docker Desktop for Windows
Issue Type: Docker Failed to Start OS Version/Build: Windows 10 - 10.0.18363 Build 18363. App Version: “Client: Docker Engine - Community
Read more >Compose file versions and upgrading - Docker Documentation
An upgrade of version 3 that introduces new parameters only available with Docker Engine version 1.13.1+, and higher. Introduces the following additional ...
Read more >Docker Compose release notes
Added support for windows/arm64 and linux/riscv64. Updates . Updated Dockerfile syntax to latest stable and renamed docs Dockerfile. Dependencies update: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The docker-compose.yml file we use:
Just a typo here, it’s correct in the docker-compose file. I have
REDASH_DATABASE_URL: "postgresql://postgres@postgres/postgres"
in theserver
container andREDASH_DATABASE_URL: "postgresql://postgres@postgres/postgres"
in theworker
container, and the result of thedocker-compose up -d
command is:OperationalError: (psycopg2.OperationalError) fe_sendauth: no password supplied