ClickHouse DNS error and IPv6 binding failures in Dokploy deployment #153

Open
opened 2025-11-22 20:31:15 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @imran-vz on GitHub (Nov 15, 2025).

Template Name

Signoz

Relevant Logs of the Error

When deploying SigNoz to Dokploy, ClickHouse container fails to start properly with two critical errors:

  • DNS Resolution Error: ClickHouse cannot resolve its own hostname when configured to use clickhouse as the cluster host
  • IPv6 Binding Error: ClickHouse attempts to bind to IPv6 addresses which are not supported in Dokploy environments
{"date_time_utc":"2025-11-15T11:05:39Z","date_time":"1763204739.155821","thread_name":"","thread_id":"738","level":"Error","query_id":"","logger_name":"ZooKeeperClient","message":"Cannot use ZooKeeper host zookeeper-1:2181 due to DNS error: DNS error: Temporary DNS error while resolving: zookeeper-1","source_file":"src\/Common\/ZooKeeper\/ZooKeeperImpl.cpp; void Coordination::ZooKeeper::connect(const zkutil::ShuffleHosts &, Poco::Timespan)","source_line":"515"}
{"date_time_utc":"2025-11-15T11:05:39Z","date_time":"1763204739.156020","thread_name":"","thread_id":"738","level":"Error","query_id":"","logger_name":"virtual bool DB::DDLWorker::initializeMainThread()","message":"Code: 999. Coordination::Exception: Cannot resolve any of provided ZooKeeper hosts due to DNS error. (KEEPER_EXCEPTION), Stack trace (when copying this message, always include the lines below):\n\n0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000f87489b\n1. Coordination::Exception Coordination::Exception::fromMessage<char const (&) [64]>(Coordination::Error, T&&) @ 0x00000000159003ac\n2. Coordination::ZooKeeper::connect(std::vector<zkutil::ShuffleHost, std::allocator<zkutil::ShuffleHost>> const&, Poco::Timespan) @ 0x00000000158ffbba\n3. Coordination::ZooKeeper::ZooKeeper(std::vector<zkutil::ShuffleHost, std::allocator<zkutil::ShuffleHost>> const&, zkutil::ZooKeeperArgs const&, std::shared_ptr<DB::ZooKeeperLog>) @ 0x00000000158f86de\n4. zkutil::ZooKeeper::init(zkutil::ZooKeeperArgs, std::unique_ptr<Coordination::IKeeper, std::default_delete<Coordination::IKeeper>>) @ 0x000000001589b19b\n5. zkutil::ZooKeeper::ZooKeeper(Poco::Util::AbstractConfiguration const&, String const&, std::shared_ptr<DB::ZooKeeperLog>) @ 0x000000001589efda\n6. zkutil::ZooKeeper::create(Poco::Util::AbstractConfiguration const&, String const&, std::shared_ptr<DB::ZooKeeperLog>) @ 0x00000000158abe0e\n7. DB::Context::getZooKeeper() const @ 0x000000001364a559\n8. DB::DDLWorker::getAndSetZooKeeper() @ 0x0000000013709e5c\n9. DB::DDLWorker::initializeMainThread() @ 0x00000000137216a2\n10. DB::DDLWorker::runMainThread() @ 0x0000000013706c71\n11. void std::__function::__policy_invoker<void ()>::__call_impl[abi:ne190107]<std::__function::__default_alloc_func<ThreadFromGlobalPoolImpl<true, true>::ThreadFromGlobalPoolImpl<void (DB::DDLWorker::*)(), DB::DDLWorker*>(void (DB::DDLWorker::*&&)(), DB::DDLWorker*&&)::'lambda'(), void ()>>(std::__function::__policy_storage const*) @ 0x0000000013725fc2\n12. ThreadPoolImpl<std::thread>::ThreadFromThreadPool::worker() @ 0x000000000f9adc12\n13. void* std::__thread_proxy[abi:ne190107]<std::tuple<std::unique_ptr<std::__thread_struct, std::default_delete<std::__thread_struct>>, void (ThreadPoolImpl<std::thread>::ThreadFromThreadPool::*)(), ThreadPoolImpl<std::thread>::ThreadFromThreadPool*>>(void*) @ 0x000000000f9b50da\n14. ? @ 0x000071d02234fac3\n15. ? @ 0x000071d0223e0a04\n (version 25.5.6.14 (official build))","source_file":"src\/Common\/Exception.cpp; void DB::tryLogCurrentExceptionImpl(Poco::Logger *, const std::string &, LogsLevel)","source_line":"285"}

Steps to Reproduce the Error

  1. Deploy the Signoz template and wait for the deployment to fail.

Environment Information

Operating System: Ubuntu 20
VPS: Hetzner
Dokploy Version: v0.25.6

When does this error occur?

During template deployment

Additional Context

No response

Will you send a PR to fix it?

No

Originally created by @imran-vz on GitHub (Nov 15, 2025). ### Template Name Signoz ### Relevant Logs of the Error When deploying SigNoz to Dokploy, ClickHouse container fails to start properly with two critical errors: - DNS Resolution Error: ClickHouse cannot resolve its own hostname when configured to use clickhouse as the cluster host - IPv6 Binding Error: ClickHouse attempts to bind to IPv6 addresses which are not supported in Dokploy environments ```JSONL {"date_time_utc":"2025-11-15T11:05:39Z","date_time":"1763204739.155821","thread_name":"","thread_id":"738","level":"Error","query_id":"","logger_name":"ZooKeeperClient","message":"Cannot use ZooKeeper host zookeeper-1:2181 due to DNS error: DNS error: Temporary DNS error while resolving: zookeeper-1","source_file":"src\/Common\/ZooKeeper\/ZooKeeperImpl.cpp; void Coordination::ZooKeeper::connect(const zkutil::ShuffleHosts &, Poco::Timespan)","source_line":"515"} {"date_time_utc":"2025-11-15T11:05:39Z","date_time":"1763204739.156020","thread_name":"","thread_id":"738","level":"Error","query_id":"","logger_name":"virtual bool DB::DDLWorker::initializeMainThread()","message":"Code: 999. Coordination::Exception: Cannot resolve any of provided ZooKeeper hosts due to DNS error. (KEEPER_EXCEPTION), Stack trace (when copying this message, always include the lines below):\n\n0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000f87489b\n1. Coordination::Exception Coordination::Exception::fromMessage<char const (&) [64]>(Coordination::Error, T&&) @ 0x00000000159003ac\n2. Coordination::ZooKeeper::connect(std::vector<zkutil::ShuffleHost, std::allocator<zkutil::ShuffleHost>> const&, Poco::Timespan) @ 0x00000000158ffbba\n3. Coordination::ZooKeeper::ZooKeeper(std::vector<zkutil::ShuffleHost, std::allocator<zkutil::ShuffleHost>> const&, zkutil::ZooKeeperArgs const&, std::shared_ptr<DB::ZooKeeperLog>) @ 0x00000000158f86de\n4. zkutil::ZooKeeper::init(zkutil::ZooKeeperArgs, std::unique_ptr<Coordination::IKeeper, std::default_delete<Coordination::IKeeper>>) @ 0x000000001589b19b\n5. zkutil::ZooKeeper::ZooKeeper(Poco::Util::AbstractConfiguration const&, String const&, std::shared_ptr<DB::ZooKeeperLog>) @ 0x000000001589efda\n6. zkutil::ZooKeeper::create(Poco::Util::AbstractConfiguration const&, String const&, std::shared_ptr<DB::ZooKeeperLog>) @ 0x00000000158abe0e\n7. DB::Context::getZooKeeper() const @ 0x000000001364a559\n8. DB::DDLWorker::getAndSetZooKeeper() @ 0x0000000013709e5c\n9. DB::DDLWorker::initializeMainThread() @ 0x00000000137216a2\n10. DB::DDLWorker::runMainThread() @ 0x0000000013706c71\n11. void std::__function::__policy_invoker<void ()>::__call_impl[abi:ne190107]<std::__function::__default_alloc_func<ThreadFromGlobalPoolImpl<true, true>::ThreadFromGlobalPoolImpl<void (DB::DDLWorker::*)(), DB::DDLWorker*>(void (DB::DDLWorker::*&&)(), DB::DDLWorker*&&)::'lambda'(), void ()>>(std::__function::__policy_storage const*) @ 0x0000000013725fc2\n12. ThreadPoolImpl<std::thread>::ThreadFromThreadPool::worker() @ 0x000000000f9adc12\n13. void* std::__thread_proxy[abi:ne190107]<std::tuple<std::unique_ptr<std::__thread_struct, std::default_delete<std::__thread_struct>>, void (ThreadPoolImpl<std::thread>::ThreadFromThreadPool::*)(), ThreadPoolImpl<std::thread>::ThreadFromThreadPool*>>(void*) @ 0x000000000f9b50da\n14. ? @ 0x000071d02234fac3\n15. ? @ 0x000071d0223e0a04\n (version 25.5.6.14 (official build))","source_file":"src\/Common\/Exception.cpp; void DB::tryLogCurrentExceptionImpl(Poco::Logger *, const std::string &, LogsLevel)","source_line":"285"} ``` ### Steps to Reproduce the Error 1. Deploy the Signoz template and wait for the deployment to fail. ### Environment Information ```bash Operating System: Ubuntu 20 VPS: Hetzner Dokploy Version: v0.25.6 ``` ### When does this error occur? During template deployment ### Additional Context _No response_ ### Will you send a PR to fix it? No
GiteaMirror added the bug label 2025-11-22 20:31:15 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#153