microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.4k stars 819 forks source link

MSYS SOCAT gets interrupted system call on WSL virtual device #7859

Closed glebovitz closed 8 months ago

glebovitz commented 2 years ago

Version

Microsoft Windows [Version 10.0.22000.376]

WSL Version

Kernel Version

5.10.60.1

Distro Version

Ubuntu 21.04

Other Software

MSYS base 2020.12-1 MSYS socat 1.7.4.1-1 WSJT-X running in windows cqrlog running in WSL 2 Ubuntu 21.04

Repro Steps

Set up a client that sends UDP traffic to 127.0.0.1. I am using WSJT-X to receive FT8 digital signals and send received data to 127.0.0.1:2237 Set up a service in WSL Ubuntu to receive data from udp port 2237. I am using CQRLOG to receive CQ messages from WSJT-X. note: if you have a ham operator they should be able to set this up.

Run MSYS SOCAT with the command socat udp4-recvfrom:2237,fork udp4-sendto::2237

Note socat -dddd udp4-recvfrom:2237,fork udp4-sendto:2237 will give additional debug information.

Expected Behavior

socat will forward udp packages from the WSJT-X on the windows host to the cqrlog in wsl guest and messages will appear in the cqrlog wsjt-x CQ monitor

Actual Behavior

socat forwards udp messages for a few minutes and then exits with an interrupted system call.

Diagnostic Logs

2021/12/22 10:06:43 socat[2265] D select -> (, 0x20, 0x0, 0x0, NULL/0.000000), 1 2021/12/22 10:06:43 socat[2265] D recvmsg(5, 0xffffbcb0{0xffffbce0,112,0xffffbc30,1,0xffffc2c0,1024,0}, 258) 2021/12/22 10:06:43 socat[2265] D xiosigaction_hasread(30, {30,0,0,2293}, ) 2021/12/22 10:06:43 socat[2265] D xiosigaction_hasread() -> 2021/12/22 10:06:43 socat[2265] D recvmsg(, {AF=2 0.0.0.0:0,112,,1,,1024,}, ) -> -1 2021/12/22 10:06:43 socat[2265] W recvmsg(): Interrupted system call 2021/12/22 10:06:43 socat[2265] N exiting with status -1 2021/12/22 10:06:43 socat[2265] D exit(-1) 2021/12/22 10:06:43 socat[2265] D starting xioexit() 2021/12/22 10:06:43 socat[2265] D finished xioexit()

microsoft-github-policy-service[bot] commented 8 months ago

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!