Protocol not available on linux subsystem in Windows 10
See original GitHub issueWhen 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
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Troubleshooting Windows Subsystem for Linux | Microsoft Learn
I'm on Windows 10 version 1903 and I still do not see options for WSL 2 ... This is likely because your machine...
Read more >The Ultimate Guide to Windows Subsystem for Linux ...
Learn how to natively work within Linux on Windows 10 with Windows Subsystem for Linux (WSL in Windows) in this HUGE guide!
Read more >Ubuntu Terminal (Windows App) Traceroute protocol not ...
i found a solution for your problem. Works like a charm ! Log on Ubuntu as root typing on terminal 'sudo --login' and...
Read more >Connect to your Linux instance using WSL
Connect to your Linux instances from Windows using the Windows Subsystem for ... the WSL and a Linux distribution using the instructions in...
Read more >Using the Linux Subsystem (WSL) in Windows 10
Once you're updated, Run the 'appwiz.cpl' command from the Run dialog box (Windows Key + R) which will open up your 'Programs and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
#7972 was now merged. The warning should be gone in the release after the upcoming one.
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.