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.

Sign up for GitHub

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

Jump to bottom

Intermittently losing network connectivity - "Exception 0xc0000006" and "cannot read size from socket: EOF" #234

Open
mendhak opened this issue Aug 22, 2023 · 0 comments
Open

Intermittently losing network connectivity - "Exception 0xc0000006" and "cannot read size from socket: EOF" #234

mendhak opened this issue Aug 22, 2023 · 0 comments

Comments

@mendhak
Copy link

mendhak commented Aug 22, 2023

WSL2 intermittently keeps losing its connection on one of my dev's laptop.
Connectivity will work both on and off the VPN but suddenly, network connectivity gets lost. Can't dig domains or curl URLs.
Do these logs provide any clue as to what might be happening, or what could be done to help fix the issue?

-- Boot ab69e1e3b21f49cfa3429eeef010c974 --
Aug 22 15:39:09 machinename systemd[1]: Started wsl-vpnkit.
░░ Subject: A start job for unit wsl-vpnkit.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit wsl-vpnkit.service has finished successfully.
░░
░░ The job identifier is 85.
Aug 22 15:39:10 machinename wsl.exe[215]: + VPNKIT_GATEWAY_IP=192.168.127.1
Aug 22 15:39:10 machinename wsl.exe[215]: + VPNKIT_HOST_IP=192.168.127.254
Aug 22 15:39:10 machinename wsl.exe[215]: + VPNKIT_LOCAL_IP=192.168.127.2
Aug 22 15:39:10 machinename wsl.exe[215]: + TAP_MAC_ADDR=5a:94:ef:e4:0c:ee
Aug 22 15:39:10 machinename wsl.exe[215]: + VMEXEC_PATH=/app/wsl-vm
Aug 22 15:39:10 machinename wsl.exe[215]: + GVPROXY_PATH=/app/wsl-gvproxy.exe
Aug 22 15:39:10 machinename wsl.exe[215]: + TAP_NAME=wsltap
Aug 22 15:39:10 machinename wsl.exe[215]: + CHECK_HOST=example.com
Aug 22 15:39:10 machinename wsl.exe[215]: + CHECK_DNS=1.1.1.1
Aug 22 15:39:10 machinename wsl.exe[215]: + DEBUG=0
Aug 22 15:39:10 machinename wsl.exe[215]: + set +x
Aug 22 15:39:10 machinename wsl.exe[215]: + WSL2_TAP_NAME=eth0
Aug 22 15:39:10 machinename wsl.exe[215]: + WSL2_GATEWAY_IP=172.22.144.1
Aug 22 15:39:10 machinename wsl.exe[215]: + '[' 0 -eq 0 ]
Aug 22 15:39:10 machinename wsl.exe[215]: + set +x
Aug 22 15:39:19 machinename wsl.exe[215]: starting vm and gvproxy...
Aug 22 15:39:19 machinename wsl.exe[215]: time="2023-08-22T14:39:19Z" level=info msg="waiting for packets..."
Aug 22 15:39:19 machinename wsl.exe[215]: time="2023-08-22T15:39:19+01:00" level=info msg="waiting for clients..."
Aug 22 15:39:19 machinename wsl.exe[215]: time="2023-08-22T15:39:19+01:00" level=info msg="new connection from remote to 35636"
Aug 22 15:39:20 machinename wsl.exe[215]: started vm and gvproxy
Aug 22 15:39:20 machinename wsl.exe[215]: check: ✔️ ping success to IPv4 WSL 2 gateway / Windows host (172.22.144.1)
Aug 22 15:39:20 machinename wsl.exe[215]: check: ✔️ ping success to IPv4 Windows host (192.168.127.254)
Aug 22 15:39:20 machinename wsl.exe[215]: check: ✔️ ping success to IPv4 gateway (192.168.127.1)
Aug 22 15:39:21 machinename wsl.exe[215]: check: ✔️ nslookup success for example.com A using 192.168.127.1
Aug 22 15:39:21 machinename wsl.exe[215]: check: ✔️ nslookup success for example.com A using 172.22.144.1
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ nslookup success for example.com A using 1.1.1.1
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ ping success to IPv4 external host domain (example.com)
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ ping success to IPv4 external host IP (1.1.1.1)
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ nslookup success for example.com AAAA using 192.168.127.1
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ nslookup success for example.com AAAA using 172.22.144.1
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ nslookup success for example.com AAAA using 1.1.1.1
Aug 22 15:39:22 machinename wsl.exe[215]: ping: bad address 'example.com'
Aug 22 15:39:22 machinename wsl.exe[215]: check: ➖ ping fail to IPv6 external host (example.com)
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ wget success for http://example.com
Aug 22 15:39:22 machinename wsl.exe[215]: check: ✔️ wget success for https://example.com
Aug 22 15:50:35 machinename wsl.exe[215]: Exception 0xc0000006 0x0 0xc3c9d6 0x6bcc7c
Aug 22 15:50:35 machinename wsl.exe[215]: PC=0x6bcc7c
Aug 22 15:50:55 machinename wsl.exe[215]: time="2023-08-22T14:50:55Z" level=error msg="cannot read size from socket: EOF"
Aug 22 15:50:56 machinename wsl.exe[215]: time="2023-08-22T14:50:56Z" level=info msg="waiting for packets..."
Aug 22 15:50:57 machinename wsl.exe[215]: time="2023-08-22T15:50:57+01:00" level=info msg="waiting for clients..."
Aug 22 15:50:57 machinename wsl.exe[215]: time="2023-08-22T15:50:57+01:00" level=info msg="new connection from remote to 12248"

Nothing appears after those last lines you see, we currently "work around" the issue by doing a wsl --shutdown and starting the distros again.
Would appreciate any pointers, thanks!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mendhak