Open fbahacker21 opened 6 months ago
i have the same problem
FYI, found a fix for this @ezotrickser and @fbahacker21.
You can connect to the clickhouse instance via it's active server using the following:
clickhouse-client --host {Private IP DNS name of ClickHouseNode1} --port 9000 --user default --password {password-created-during-creation}
Note, this doesn't fully fix the issue here. Seems like there should be a way to access everything through the ELB and not through a private IP.
Hi, thanks for the feedback.
So for running clickhouse-client command, please run the command by specifying the host clickhouse-client --host <private-ip>
and then input username and password. We also provided a Grafana Web Console so you can access in this way.
And for this issue:
When I tried to check the server status I received the following: [ec2-user@ip-xx-x-xx-xxx ~]$ service clickhouse-server status Redirecting to /bin/systemctl status clickhouse-server.service Unit clickhouse-server.service could not be found.
Please make sure that you are running service clickhouse-server status
command on the clickhouse server instance, not the ClickHouseAdminClient instance. clickhouse-server runs only on the clickhouse server instance.
Suppose I have gone through everything from step1 to step6:
https://aws-ia.github.io/cfn-ps-clickhouse-cluster/
when I got to the final step step6 try to start clickhouse-client it received the following error:
[ec2-user@ip-xx-x-xx-xxx ~]$ clickhouse-client ClickHouse client version 23.3.8.21 (official build). Connecting to localhost:9000 as user default. Code: 210. DB::NetException: Connection refused (localhost:9000). (NETWORK_ERROR)
When I tried to check the server status I received the following:
[ec2-user@ip-xx-x-xx-xxx ~]$ service clickhouse-server status Redirecting to /bin/systemctl status clickhouse-server.service Unit clickhouse-server.service could not be found.