-
Notifications
You must be signed in to change notification settings - Fork 15
db_clickhouse unreachable from gprofiler-ps-ch-rest-service #21
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
Comments
Looks like |
Used to start stack: |
Hi, tnx for your response. |
c5.2xl on AWS running Ubuntu 22 and 6.5 kernel |
It looks like the problem is starting clickhouse. Let's troubleshoot: Bring down the existing containers and remove volumes: docker-compose --profile with-clickhouse down -v Ensure no containers are left: docker ps -a Start only clickhouse: docker-compose --profile with-clickhouse up -d db_clickhouse If it fails, check: docker-compose logs db_clickhouse Used ports: sudo lsof -i -P -n | grep LISTEN If you uncommented the debug section in the Docker Compose file, comment it again and retry: docker-compose --profile with-clickhouse up -d db_clickhouse Please follow these steps and let us know the results. |
|
diagnostic.sh is giving a false positive. The containers are actually connecting to each other even though the error is throwing. I suggest an update to the script |
I am running into an issue where it seems like the frontend cannot connect to the backend. When I run the diagnostic I get the error:
[ERROR] container unreachable from gprofiler-ps-ch-rest-service
Error response from daemon: No such container: db_clickhouse
[ERROR] container unreachable from db_clickhouse
When I look into it further and pull the error logs I find this error for ports 8123, 9000, 9004, 9005, 9009:
Application: Listen [0.0.0.0]:8123 failed: Poco::Exception. Code: 1000, e.code() = 98, Net Exception: Address already in use: 0.0.0.0:8123 (version 22.8.21.38 (official build)). If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host>0.0.0.0</listen_host> . Example for disabled IPv4: <listen_host>::</listen_host>
Any insight?
The text was updated successfully, but these errors were encountered: