Issues with hosting_plausible_events_db_1 creation

[jen140]

hosting_plausible_1 is unable to connect to hosting_plausible_events_db_1 host on port 8123.
docker logs hosting_plausible_1 show the following error(removed the rest for clarity):

** (UndefinedFunctionError) function :econnrefused.exception/1 is undefined (module :econnrefused is not available)

docker logs hosting_plausible_events_db_1 show the following error:

<Warning> Application: Listen [::1]:8123 failed: Poco::Exception. Code: 1000, e.code() = 99, e.displayText() = Net Exception: Cannot assign requested address: [::1]:8123 (version 20.11.4.13 (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>

And for some reason, it being a warning (probably because of this ClickHouse/ClickHouse#4406) it doesn't bind the port.

So this change will only listen on ipv4 and fix the problem.

[mabasic]

I have tried this fix and it worked for me, but this disables IPv6?

Error output:

2020.12.02 20:29:34.703489 [ 1 ] {} <Warning> Application: Listen [::1]:8123 failed: Poco::Exception. Code: 1000, e.code() = 99, e.displayText() = Net Exception: Cannot assign requested address: [::1]:8123 (version 20.11.4.13 (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>

[jen140]

Yup, this disables ipv6.
But if I'm reading correctly, ipv6 is disabled by default in docker(https://docs.docker.com/config/daemon/ipv6/), so this shouldn't create any issue.

[mabasic]

Could it be that if we were to enable IPv6 in docker, by following the instructions in the link you provided, the issue would be solved without this fix?

Not sure which approach is best...

[jen140]

I suppose doing this fix and also adding the --ipv6 flag to the docker-compose somewhere would fix that, but I don't think that it's a "portable" solution, as this change requires host docker changes that might break something.

[mabasic]

@jen140 I agree.

[patschi]

I've ran into the same issue since latest changes. By default the docker container of clickhouse ships etc/clickhouse-server/config.d/docker_related_config.xml within the container. Due to the commit 1c2004f the file is overwritten and clickhouse stops working.

My workaround was rather using following:

      - ./clickhouse/clickhouse-config.xml:/etc/clickhouse-server/config.d/logging.xml:ro
      - ./clickhouse/clickhouse-user-config.xml:/etc/clickhouse-server/users.d/logging.xml:ro

As clickhouse recursively merges the settings, this might also be more ideal in the future.

[ukutaht]

I think @patschi's solution is the best. I will create a PR with it ASAP to fix the issue

[ukutaht]

Issue fixed in #28