-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Comments
The same issue with 21.3.6.55 |
/cc @abyss7 |
@sinmaker No, you should not be worried about this exception message. It may possibly indicate some minor issues with your infrastructure, but it is not an issue of ClickHouse itself. |
Then log spamming is the issue #10935 (comment) |
I.e. I've encountered the same situation recently when client specified an unknown setting. |
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. |
me too |
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):
(version 21.3.4.25 (official build))`
The text was updated successfully, but these errors were encountered: