I am using docker based signoz setup on single ser...
# support
n
I am using docker based signoz setup on single server but, I am getting below error logs on clickhouse container. Can any one help what need to do to resolve below errors.
Copy code
{
  "date_time": "1748850279.117008",
  "thread_name": "TCPServerConnection ([#1])",
  "thread_id": "47",
  "level": "Error",
  "query_id": "",
  "logger_name": "ServerErrorHandler",
  "message": "Poco::Exception. Code: 1000, e.code() = 32, I/O error: Broken pipe, Stack trace (when copying this message, always include the lines below):\n\n0. Poco::Net::SocketImpl::error(int, String const&) @ 0x00000000153a1b5f in /usr/bin/clickhouse\n1. Poco::Net::SocketImpl::sendBytes(void const*, int, int) @ 0x00000000153a2bbd in /usr/bin/clickhouse\n2. Poco::Net::StreamSocketImpl::sendBytes(void const*, int, int) @ 0x00000000153a5296 in /usr/bin/clickhouse\n3. Poco::Net::HTTPSession::write(char const*, long) @ 0x00000000153908b3 in /usr/bin/clickhouse\n4. Poco::Net::HTTPHeaderIOS::~HTTPHeaderIOS() @ 0x000000001538bbdb in /usr/bin/clickhouse\n5. Poco::Net::HTTPHeaderOutputStream::~HTTPHeaderOutputStream() @ 0x000000001538bf1f in /usr/bin/clickhouse\n6. DB::HTTPServerResponse::send() @ 0x0000000012942988 in /usr/bin/clickhouse\n7. DB::HTTPServerConnection::sendErrorResponse(Poco::Net::HTTPServerSession&, Poco::Net::HTTPResponse::HTTPStatus) @ 0x000000001293ecda in /usr/bin/clickhouse\n8. DB::HTTPServerConnection::run() @ 0x000000001293e97b in /usr/bin/clickhouse\n9. Poco::Net::TCPServerConnection::start() @ 0x00000000153a5a72 in /usr/bin/clickhouse\n10. Poco::Net::TCPServerDispatcher::run() @ 0x00000000153a6871 in /usr/bin/clickhouse\n11. Poco::PooledThread::run() @ 0x000000001549f047 in /usr/bin/clickhouse\n12. Poco::ThreadImpl::runnableEntry(void*) @ 0x000000001549d67d in /usr/bin/clickhouse\n13. ? @ 0x00007fd21be01609\n14. ? @ 0x00007fd21bd26353\n (version 24.1.2.5 (official build))",
  "source_file": "src/Common/Exception.cpp; void DB::tryLogCurrentExceptionImpl(Poco::Logger *, const std::string &)",
  "source_line": "222"
}
n
Hey @Nishant Hurnekar, you can ignore the
broken pipe
errors - although, are you facing any issues because of this
n
ok. No issues, even not aware about any impact as of now. just implementation phase. I am trying to push setup in production with critical servers. So curious to know the reason behind the such events.
n
These are generated by query-service when the queries are cancelled