Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server log filled with errors #95

Closed
binary-joe opened this issue Jul 26, 2022 · 2 comments
Closed

Server log filled with errors #95

binary-joe opened this issue Jul 26, 2022 · 2 comments

Comments

@binary-joe
Copy link

Hi,
In a k8s environment, we have a batch processing that heavily reads and writes data into the server. During that this error gets logged many times

2022.07.26 08:42:18.673005 [ 36 ] {} <Error> ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below):

0. Poco::Net::NetException::NetException(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int) @ 0x1649742c in /usr/bin/clickhouse
1. Poco::Net::SocketImpl::error(int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x164aaf24 in /usr/bin/clickhouse
2. Poco::Net::SocketImpl::peerAddress() @ 0x164ad616 in /usr/bin/clickhouse
3. DB::HTTPServerRequest::HTTPServerRequest(std::__1::shared_ptr<DB::Context const>, DB::HTTPServerResponse&, Poco::Net::HTTPServerSession&) @ 0x1545a918 in /usr/bin/clickhouse
4. DB::HTTPServerConnection::run() @ 0x15459482 in /usr/bin/clickhouse
5. Poco::Net::TCPServerConnection::start() @ 0x164b264f in /usr/bin/clickhouse
6. Poco::Net::TCPServerDispatcher::run() @ 0x164b4aa1 in /usr/bin/clickhouse
7. Poco::PooledThread::run() @ 0x16671e49 in /usr/bin/clickhouse
8. Poco::ThreadImpl::runnableEntry(void*) @ 0x1666f1a0 in /usr/bin/clickhouse
9. ? @ 0x7f4c8af4e609 in ?
10. clone @ 0x7f4c8ae73163 in ?
 (version 22.3.2.1)

we tried setting ssl, changing/removing the livness & readiness probes but nothing worked. Do you have any idea what could be the cause for this?

BR

@doom369
Copy link
Collaborator

doom369 commented Jul 26, 2022

@binary-joe that's most likely clickhouse bug:

ClickHouse/ClickHouse#27297
ClickHouse/ClickHouse#34218
ClickHouse/ClickHouse#24879

We have this issue as well. The only observation - updating to the latest CH version reduces the number of these errors.

@binary-joe
Copy link
Author

The error doesn't occur at all with the official ClickHouse driver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants