Skip to content

"too many open files" #263

@elouanKeryell-Even

Description

@elouanKeryell-Even

From time to time the logs output is filled with this error:

time="2024-06-14T09:42:10Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:11Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:12Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:13Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:14Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:15Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:16Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:17Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:18Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"
time="2024-06-14T09:42:19Z" level=error msg="cannot connect to host: fork/exec /app/wsl-gvproxy.exe: too many open files"

It doesn't prevent it from working:

$ curl -I google.com
HTTP/1.1 301 Moved Permanently

... but still I figured I would open an issue

I tried upgrading the limit on open files, from 1024 (default) to 65535, and then restarting the vpnkit, but to no avail:

ulimit -n 65535

EDIT: this might be caused by trying to start a second instance of wsl-vpnkit, not sure

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions