self-hosted icon indicating copy to clipboard operation
self-hosted copied to clipboard
Published 3 weeks ago • verified publisher icon getsentry

Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported

Open makhomed opened this issue 2 months ago • 7 comments

Self-Hosted Version

25.10.0

CPU Architecture

x86_64

Docker Version

Docker version 28.5.1, build e180ab8

Docker Compose Version

Docker Compose version v2.40.2

Machine Specification

  • [x] My system meets the minimum system requirements of Sentry

Steps to Reproduce

  1. install version 25.9.0
  2. upgrade to version 25.10.0
  3. run command docker logs sentry-self-hosted-clickhouse-1

Expected Result

expected clean log, without fatal errors.

It is need to disable IPv6 in the clickhouse?

so,

<listen_host>0.0.0.0</listen_host>

must be present inside self-hosted-25.10.0/clickhouse/config.xml file?

Actual Result

Processing configuration file '/etc/clickhouse-server/config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/sentry.xml'.
Logging warning to /var/log/clickhouse-server/clickhouse-server.log
Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
2025.10.28 19:44:56.162757 [ 1 ] {} <Warning> Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:44:56.306950 [ 1 ] {} <Warning> Context: Server has databases (for example `default`) with Ordinary engine, which was deprecated. To convert this database to the new Atomic engine, create a flag /var/lib/clickhouse/flags/convert_ordinary_to_atomic and make sure that ClickHouse has write permission for it. Example: sudo touch '/var/lib/clickhouse/flags/convert_ordinary_to_atomic' && sudo chmod 666 '/var/lib/clickhouse/flags/convert_ordinary_to_atomic'
2025.10.28 19:44:56.318381 [ 1 ] {} <Warning> Application: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:44:56.318468 [ 1 ] {} <Warning> Application: Listen [::]:9000 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:44:56.318539 [ 1 ] {} <Warning> Application: Listen [::]:9004 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:44:56.318593 [ 1 ] {} <Warning> Application: Listen [::]:9005 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
Processing configuration file '/etc/clickhouse-server/config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/sentry.xml'.
Logging warning to /var/log/clickhouse-server/clickhouse-server.log
Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
2025.10.28 19:53:00.365302 [ 1 ] {} <Warning> Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:53:00.507204 [ 1 ] {} <Warning> Context: Server has databases (for example `default`) with Ordinary engine, which was deprecated. To convert this database to the new Atomic engine, create a flag /var/lib/clickhouse/flags/convert_ordinary_to_atomic and make sure that ClickHouse has write permission for it. Example: sudo touch '/var/lib/clickhouse/flags/convert_ordinary_to_atomic' && sudo chmod 666 '/var/lib/clickhouse/flags/convert_ordinary_to_atomic'
2025.10.28 19:53:00.519440 [ 1 ] {} <Warning> Application: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:53:00.519553 [ 1 ] {} <Warning> Application: Listen [::]:9000 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:53:00.519612 [ 1 ] {} <Warning> Application: Listen [::]:9004 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>
2025.10.28 19:53:00.519660 [ 1 ] {} <Warning> Application: Listen [::]:9005 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>

Event ID

No response

makhomed avatar Oct 28 '25 21:10 makhomed

I don't see any of the logs on my instance. Are you running Docker with IPv6 enabled? https://docs.docker.com/engine/daemon/ipv6/

aldy505 avatar Oct 29 '25 03:10 aldy505

I don't see any of the logs on my instance. Are you running Docker with IPv6 enabled? https://docs.docker.com/engine/daemon/ipv6/

I do not enable IPv6 in the docker configuration:

# cat /etc/docker/daemon.json

{
  "bip": "172.28.0.1/16",
  "log-driver": "syslog",
  "default-address-pools" : [
    {
      "base" : "172.29.0.0/16",
      "size" : 24
    }
  ]
}

# docker network ls
NETWORK ID     NAME                         DRIVER    SCOPE
b5d315edccc5   bridge                       bridge    local
8d49265e5ee6   host                         host      local
0d5dc5a3f889   none                         null      local
b22a0f0ecfa8   sentry-self-hosted_default   bridge    local

# docker network inspect b22a0f0ecfa8 | grep IPv6 | sort | uniq
        "EnableIPv6": false,
                "IPv6Address": ""

IPv6 not enabled for the docker, and this is reason of clickhouse error:

2025.10.28 19:53:00.519440 [ 1 ] {} Application: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 25.3.6.10034.altinitystable (altinity 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>

makhomed avatar Oct 29 '25 11:10 makhomed

Hi, sorry for the very late reply. Is this issue making your self-hosted sentry unusable? I don't have this issue on my instance, and I'm using the default ClickHouse configuration provided by the repository.

aldy505 avatar Nov 12 '25 13:11 aldy505

Hi, sorry for the very late reply. Is this issue making your self-hosted sentry unusable? I don't have this issue on my instance, and I'm using the default ClickHouse configuration provided by the repository.

At time of writing my first message I have a big amount of such error messages in logs, like this:

# docker compose logs | less -S

relay-1 | 2025-11-12T21:02:32.821137Z ERROR relay_server::services::health_check: Health check probe 'auth' failed
relay-1 | 2025-11-12T21:02:35.822920Z ERROR relay_server::services::health_check: Health check probe 'auth' failed
relay-1 | 2025-11-12T21:02:38.823479Z ERROR relay_server::services::health_check: Health check probe 'auth' failed

and I was looking for root cause of problem. I don't know is the ClickHouse exceptions the root cause of this problem or not, but such (may be unrelated) exceptions and error messages make sentry debug using docker compose logs more hard work.

so, it is useful for debug process to make ClickHouse more quiet, without not necessary and unrelated error messages.

P.S.

relay error "Health check probe 'auth' failed" was fixed by full reinstall of sentry containers.

also I changed "log-driver" to "journald" in /etc/docker/daemon.json

makhomed avatar Nov 12 '25 21:11 makhomed

relay does not interact with clickhouse in any way. Was doing systemctl restart docker fixed it for you?

I also wonder whether we should explicitly configure <listen_host>0.0.0.0</listen_host> on the ClickHouse config.

aldy505 avatar Nov 16 '25 07:11 aldy505

relay does not interact with clickhouse in any way. Was doing systemctl restart docker fixed it for you?

complete reinstall fixed issue.

I drop all except volumes, and reinstall, and issue was fixed, relay after this work without errors.

sentry status after remove all containers and images. 

# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

# docker image ls
IMAGE   ID             DISK USAGE   CONTENT SIZE   EXTRA

# docker volume ls
DRIVER    VOLUME NAME
local     sentry-clickhouse
local     sentry-data
local     sentry-kafka
local     sentry-postgres
local     sentry-redis
local     sentry-seaweedfs
local     sentry-self-hosted_sentry-clickhouse-log
local     sentry-self-hosted_sentry-kafka-log
local     sentry-self-hosted_sentry-nginx-cache
local     sentry-self-hosted_sentry-nginx-www
local     sentry-self-hosted_sentry-secrets
local     sentry-self-hosted_sentry-smtp
local     sentry-self-hosted_sentry-smtp-log
local     sentry-self-hosted_sentry-symbolicator
local     sentry-self-hosted_sentry-taskbroker
local     sentry-self-hosted_sentry-vroom
local     sentry-self-hosted_sentry-zookeeper-log

I also wonder whether we should explicitly configure <listen_host>0.0.0.0</listen_host> on the ClickHouse config.

Why not?

inside sentry only IPv4 used, and explicitly configure <listen_host>0.0.0.0</listen_host> on the ClickHouse config will stop flood of errors Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported when IPv6 not enabled for Docker containers.

makhomed avatar Nov 16 '25 09:11 makhomed

I've got the same issue

demshin avatar Nov 17 '25 14:11 demshin

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

getsantry[bot] avatar Dec 21 '25 08:12 getsantry[bot]