Ray: Protocol not available on linux subsystem in Windows 10

[drozzy]

When I try to run tune from a linux subsystem on Windows 10 I get this error:

E0118 15:27:51.422986300    7451 socket_utils_common_posix.cc:208] check for SO_REUSEPORT: {"created":"@1579379271.422971700","description":"Protocol not available","errno":92,"file":"external/com_github_grpc_grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":185,"os_error":"Protocol not available","syscall":"getsockopt(SO_REUSEPORT)"}
E0118 15:27:51.424577800    7451 socket_utils_common_posix.cc:313] setsockopt(TCP_USER_TIMEOUT) Protocol not available

[drozzy]

Nevermind, the error was raise ValueError("Called resume when no checkpoint exists " when setting resume="PROMPT".

[linjohn]

I get a similar message on WSL. Ray continues the processing though but in the dashboard all information are displayed with "0". Not sure if clusters would work.

• Windows 10 Pro Version 1909
• Ubuntu 18.04 LTS
• Python 3.6.9
• ray==0.8.1
• psutil==4.3.1
• setproctitle==1.1.10

E0201 19:17:26.289452900   14605 socket_utils_common_posix.cc:208] check for SO_REUSEPORT: {"created":"@1580581046.289390800","description":"Protocol not available","errno":92,"file":"external/com_github_grpc_grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":185,"os_error":"Protocol not available","syscall":"getsockopt(SO_REUSEPORT)"}
E0201 19:17:26.289603700   14605 socket_utils_common_posix.cc:313] setsockopt(TCP_USER_TIMEOUT) Protocol not available

[OscarVanL]

Getting the same errors in WSL, including the dashboard displaying "0" for all information.

[jsuarez5341]

Same error -- this is still an issue. Default WSL Ubuntu setup, latest ray build

[mehrdadn]

I've encountered this message too; I think the issue is because there's no Windows support for SO_REUSEPORT. I think if the error message is benign, we should probably find a way to get rid of it. If it's indicating an actual problem, though, we should try to address it, and/or it may warrant reporting to GRPC, since it relates to their WSL support. I'm not sure which is the case though. Does anyone know if it is a symptom of an actual problem, or if everything works fine regardless?

Note that this warning can be suppressed at build-time in .bazelrc via

build:linux --per_file_copt="-\\.(asm|S)$,external/com_github_grpc_grpc/.*@-DGPR_MANYLINUX1"

[LucaCappelletti94]

I have encountered this issue as well.

[anton-malakhov]

+1

[xiaocaio]

+1

[BrandonEscamilla]

+1

[mehrdadn]

7972 was now merged. The warning should be gone in the release _after_ the upcoming one.