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

"Net Exception: Socket is not connected" after upgrade CH from 19.11.11.57 to 21.3.4.25 #23059

Closed
SpecialK118 opened this issue Apr 14, 2021 · 7 comments
Labels
question Question?

Comments

@SpecialK118
Copy link

After upgrading clickhouse, I see in the error log many messages like blow.
I run clickhouse on Ubuntu 18.04.
It seems to be functioning ok.
Should I be worried? What's the root cause?

`2021.04.13 09:31:08.897973 [ 20117 ] {} ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below):

  1. Poco::Net::SocketImpl::error(int, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&) @ 0x11f7dc4e in /usr/bin/clickhouse
  2. Poco::Net::SocketImpl::peerAddress() @ 0x11f7fec6 in /usr/bin/clickhouse
  3. DB::HTTPServerRequest::HTTPServerRequest(DB::Context const&, DB::HTTPServerResponse&, Poco::Net::HTTPServerSession&) @ 0xf8db914 in /usr/bin/clickhouse
  4. DB::HTTPServerConnection::run() @ 0xf8da784 in /usr/bin/clickhouse
  5. Poco::Net::TCPServerConnection::start() @ 0x11f84caf in /usr/bin/clickhouse
  6. Poco::Net::TCPServerDispatcher::run() @ 0x11f866c1 in /usr/bin/clickhouse
  7. Poco::PooledThread::run() @ 0x120bcde9 in /usr/bin/clickhouse
  8. Poco::ThreadImpl::runnableEntry(void*) @ 0x120b8c4a in /usr/bin/clickhouse
  9. start_thread @ 0x76db in /lib/x86_64-linux-gnu/libpthread-2.27.so
  10. __clone @ 0x12171f in /lib/x86_64-linux-gnu/libc-2.27.so
    (version 21.3.4.25 (official build))`
@SpecialK118 SpecialK118 added the question Question? label Apr 14, 2021
@millin
Copy link
Contributor

millin commented Apr 15, 2021

The same issue with 21.3.6.55

@filimonov
Copy link
Contributor

/cc @abyss7

@filimonov filimonov added v21.3-affected comp-http http protocol related labels Apr 15, 2021
@alexey-milovidov alexey-milovidov removed the comp-http http protocol related label Apr 20, 2021
@alexey-milovidov
Copy link
Member

@sinmaker No, you should not be worried about this exception message.
It happens when a client connects to ClickHouse and closes connection immediately.

It may possibly indicate some minor issues with your infrastructure, but it is not an issue of ClickHouse itself.

@filimonov
Copy link
Contributor

Then log spamming is the issue #10935 (comment)

@abyss7
Copy link
Contributor

abyss7 commented Apr 22, 2021

I.e. I've encountered the same situation recently when client specified an unknown setting.

@andvary
Copy link

andvary commented May 26, 2024

I encountered this message because of a bug in my HTTP client (in go you must read the entire response body in order to persist connections, otherwise your client sets "RST" flag, the connection drops and has to be re-established every time a new request is being made). So I'm actually grateful to the ClickHouse developers for this useful warning.

@liubo-it
Copy link

me too

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

No branches or pull requests

7 participants