Hello,
Sorry, I cannot participate in telegram from work. I am running CH in a container (one of a collection), it has been working fine. The containers were recently recreated on a different machine and we started seeing this error when the service is started:
root@47e7fcd869c9:/var/log/clickhouse-server# service clickhouse-server start
Start clickhouse-server service: Path to data directory in /etc/clickhouse-server/config.xml: /var/lib/clickhouse/
UNKNOWN
It takes about 10 seconds after the "Start ..." line to emit the "UNKNOWN" line. The clickhouse-server.err.log shows:
2019.07.11 18:37:05.517792 [ 1 ] {} <Error> Application: DB::Exception: Listen [::]:8123 failed: 0: DNS error: EAI: -9
We thought that the set up of this machine was the same as the older machine that works, but apparently not. There are two differences, the non-working one was built today, the working one was built a month ago, so possibly different packages (these are Ubuntu-18.04 images). Also the machines are possibly different in some way, possibly different docker configurations (though not intentionally).
Does this log error look familiar to anyone? Thanks in advance for any help,
Matt
Hello,
Sorry, I cannot participate in telegram from work. I am running CH in a container (one of a collection), it has been working fine. The containers were recently recreated on a different machine and we started seeing this error when the service is started:
root@47e7fcd869c9:/var/log/clickhouse-server# service clickhouse-server startStart clickhouse-server service: Path to data directory in /etc/clickhouse-server/config.xml: /var/lib/clickhouse/UNKNOWNIt takes about 10 seconds after the "Start ..." line to emit the "UNKNOWN" line. The clickhouse-server.err.log shows:
2019.07.11 18:37:05.517792 [ 1 ] {} <Error> Application: DB::Exception: Listen [::]:8123 failed: 0: DNS error: EAI: -9We thought that the set up of this machine was the same as the older machine that works, but apparently not. There are two differences, the non-working one was built today, the working one was built a month ago, so possibly different packages (these are Ubuntu-18.04 images). Also the machines are possibly different in some way, possibly different docker configurations (though not intentionally).
Does this log error look familiar to anyone? Thanks in advance for any help,
Matt