<3>WSL (13) ERROR: UtilAcceptVsock:250: accept4 failed 110

[remco-pc]

Contact Details

No response

What happened?

<3>WSL (13) ERROR: UtilAcceptVsock:250: accept4 failed 110

Version

./llava-v1.5-7b-q4.llamafile

What operating system are you seeing the problem on?

Linux, Windows

Relevant log output

wsl2 debian version, just trying it out

[jart]

This is an upstream issue with WSL. See microsoft/WSL#8677 It happens I think when you SSH into your WSL instance rather than using the Microsoft provided command prompt. Doing that is janky.

Another thing you want to do, to get WSL working properly is this:

[Unit]
Description=cosmopolitan APE binfmt service
After=wsl-binfmt.service

[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo ':APE:M::MZqFpD::/usr/bin/ape:' >/proc/sys/fs/binfmt_misc/register"

[Install]
WantedBy=multi-user.target

Put that in /etc/systemd/system/cosmo-binfmt.service.

Then run sudo systemctl enable cosmo-binfmt.

[remco-pc]

I dont ssh into the machine, i am using the debian console, i will try that config, @jart i dont need to install anything ?

[remco-pc]

@jart it didn't work, i still receive <3>WSL (560179) ERROR: UtilAcceptVsock:250: accept4 failed 110 after enabling sudo systemctl enable cosmo-binfmt.

I even restarted my machine, to see if it needed a reboot

[adailey-sw]

I ran into this error when trying to limit the memory used by WSL. I had created a .wslconfig file in my windows user home directory with these contents in an effort to limit the memory:

[wsl2]
memory=500MB

But I suspect that wasn't enough memory for what I needed, and I started running into the error. With that file removed, the error went away. So if you're seeing this issue, it might be that you don't have enough free memory.