confidential-computing-zoo icon indicating copy to clipboard operation
confidential-computing-zoo copied to clipboard

ra-tls-grpc

Open reclock opened this issue 1 year ago • 2 comments

When I start the GRPC server, the following error occurs:

E0104 11:17:52.048905000 1 socket_utils_common_posix.cc:223] check for SO_REUSEPORT: {"created":"@1704367072.048218000","description":"Protocol not available","errno":92,"file":"src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":202,"os_error":"Protocol not available","syscall":"getsockopt(SO_REUSEPORT)"} [P1:T1:python3.8] error: bind: invalid handle returned

Do you know if this error will affect the establishment of the GRPC network

reclock avatar Jan 04 '24 11:01 reclock

I am an example running within a Docker container

reclock avatar Jan 04 '24 11:01 reclock

When I start the GRPC server, the following error occurs:

E0104 11:17:52.048905000 1 socket_utils_common_posix.cc:223] check for SO_REUSEPORT: {"created":"@1704367072.048218000","description":"Protocol not available","errno":92,"file":"src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":202,"os_error":"Protocol not available","syscall":"getsockopt(SO_REUSEPORT)"} [P1:T1:python3.8] error: bind: invalid handle returned

Do you know if this error will affect the establishment of the GRPC network

Run with gramine? Perhaps the server is running twice on the same port, and gramine does not support "SO_REUSEPORT".

Check this https://github.com/gramineproject/gramine/issues/763 for detail.

BuJianlin avatar Jan 26 '24 02:01 BuJianlin

No comment.

RodgerZhu avatar Jun 24 '24 23:06 RodgerZhu