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

ClickHouse error: Net Exception: Socket is not connected #3141

Closed
makhomed opened this issue Jun 18, 2024 · 4 comments
Closed

ClickHouse error: Net Exception: Socket is not connected #3141

makhomed opened this issue Jun 18, 2024 · 4 comments

Comments

@makhomed
Copy link

makhomed commented Jun 18, 2024

Self-Hosted Version

24.6.0

CPU Architecture

x86_64

Docker Version

26.1.3

Docker Compose Version

2.27.0

Steps to Reproduce

  1. update sentry self-hosted to 24.6.0
  2. run docker logs sentry-self-hosted-clickhouse-1
  3. see many stack traces in the output of previous command

Expected Result

expected not to have any errors in the clickhouse logs

Actual Result

2024.06.18 21:06:24.390441 [ 489 ] {} <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::SocketImpl::error(int, String const&) @ 0x0000000015b3dbf2 in /usr/bin/clickhouse
1. Poco::Net::SocketImpl::peerAddress() @ 0x0000000015b40376 in /usr/bin/clickhouse
2. DB::ReadBufferFromPocoSocket::ReadBufferFromPocoSocket(Poco::Net::Socket&, unsigned long) @ 0x000000000c896cc6 in /usr/bin/clickhouse
3. DB::HTTPServerRequest::HTTPServerRequest(std::shared_ptr<DB::IHTTPContext>, DB::HTTPServerResponse&, Poco::Net::HTTPServerSession&) @ 0x000000001315451b in /usr/bin/clickhouse
4. DB::HTTPServerConnection::run() @ 0x0000000013152ba4 in /usr/bin/clickhouse
5. Poco::Net::TCPServerConnection::start() @ 0x0000000015b42834 in /usr/bin/clickhouse
6. Poco::Net::TCPServerDispatcher::run() @ 0x0000000015b43a31 in /usr/bin/clickhouse
7. Poco::PooledThread::run() @ 0x0000000015c7a667 in /usr/bin/clickhouse
8. Poco::ThreadImpl::runnableEntry(void*) @ 0x0000000015c7893c in /usr/bin/clickhouse
9. ? @ 0x00007f9d85c49609 in ?
10. ? @ 0x00007f9d85b6e353 in ?
 (version 23.8.11.29.altinitystable (altinity build))

2024.06.18 21:06:25.385189 [ 489 ] {} <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::SocketImpl::error(int, String const&) @ 0x0000000015b3dbf2 in /usr/bin/clickhouse
1. Poco::Net::SocketImpl::peerAddress() @ 0x0000000015b40376 in /usr/bin/clickhouse
2. DB::HTTPServerRequest::HTTPServerRequest(std::shared_ptr<DB::IHTTPContext>, DB::HTTPServerResponse&, Poco::Net::HTTPServerSession&) @ 0x0000000013154417 in /usr/bin/clickhouse
3. DB::HTTPServerConnection::run() @ 0x0000000013152ba4 in /usr/bin/clickhouse
4. Poco::Net::TCPServerConnection::start() @ 0x0000000015b42834 in /usr/bin/clickhouse
5. Poco::Net::TCPServerDispatcher::run() @ 0x0000000015b43a31 in /usr/bin/clickhouse
6. Poco::PooledThread::run() @ 0x0000000015c7a667 in /usr/bin/clickhouse
7. Poco::ThreadImpl::runnableEntry(void*) @ 0x0000000015c7893c in /usr/bin/clickhouse
8. ? @ 0x00007f9d85c49609 in ?
9. ? @ 0x00007f9d85b6e353 in ?
 (version 23.8.11.29.altinitystable (altinity build))

Event ID

No response

@gmisiolek-sbm
Copy link

It's 3rd major release when this error occurres... Will someone do something with this issue?

@baskinsy
Copy link

I have the same issue after upgrading to 24.6.0.

@mbovingfred
Copy link

mbovingfred commented Jun 20, 2024

i have the same issue upgrading to 24.6.0 and multiple pages are broken, saying "The organization you were looking for was not found"

@aldy505
Copy link
Collaborator

aldy505 commented Jun 20, 2024

I'll close this issue in favor of getsentry/snuba#5707 (comment), we'll get this fixed there. There's an effort from the employee to fix it on that issue.

i have the same issue upgrading to 24.6.0 and multiple pages are broken, saying "The organization you were looking for was not found"

@mbovingfred I believe this is a totally separate issue. Can you open a dedicated issue for this?

@aldy505 aldy505 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 20, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
Archived in project
Development

No branches or pull requests

5 participants