ClickHouse客户端连接报错：来自localhost:9000的异常数据包
Let’s break down how to troubleshoot and resolve this connection issue step by step:
1. Confirm the server is listening on port 9000
First, verify that the ClickHouse server is actually bound to port 9000 and the correct network addresses. Run this command to check active listeners:
ss -tulnp | grep clickhouse-server
Look for a line like tcp LISTEN 0 128 [::]:9000 [::]:* users:(("clickhouse-serv",pid=xxxx,fd=xx)) — this confirms the server is listening on all IPv6 addresses. If you don’t see this entry, check the server logs for errors related to port binding.
2. Connect using the IPv6 address explicitly
Since you enabled IPv6 in config.xml, the client might default to IPv4 (127.0.0.1) while the server is only listening on IPv6. Try connecting directly with the IPv6 loopback address:
sudo clickhouse-client --host ::1
If this works, you can either set an alias for the client to use this by default, or adjust the server config to listen on both IPv4 and IPv6.
3. Configure the server to listen on both address families
Open /etc/clickhouse-server/config.xml and check the <listen_host> settings. To ensure the server accepts connections from both IPv4 and IPv6, add these lines (or confirm they exist):
<listen_host>::</listen_host> <listen_host>0.0.0.0</listen_host>
Save the config and restart the server:
sudo /etc/init.d/clickhouse-server restart
Now try connecting with sudo clickhouse-client again.
4. Check firewall rules for port 9000
Firewalls (even local ones) might block traffic to port 9000 for IPv6 or IPv4. For IPv6, allow connections on the loopback address:
sudo ip6tables -A INPUT -s ::1 -p tcp --dport 9000 -j ACCEPT
If using firewalld, open the port permanently:
sudo firewall-cmd --add-port=9000/tcp --permanent sudo firewall-cmd --reload
5. Inspect server logs for hidden issues
If the above steps don’t work, dig into the server logs to spot underlying problems. Logs are typically located at /var/log/clickhouse-server/server.log. Look for lines like "Listening for queries" to confirm the server started successfully, or any error messages related to network setup or binding.
内容的提问来源于stack exchange，提问作者dsr301
