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

"too many open files" #263

Open
elouanKeryell-Even opened this issue Jun 14, 2024 · 1 comment
Open

"too many open files" #263

elouanKeryell-Even opened this issue Jun 14, 2024 · 1 comment

Comments

@elouanKeryell-Even
Copy link

elouanKeryell-Even commented Jun 14, 2024 •
edited
Loading

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
@bax137
Copy link

bax137 commented Jun 21, 2024

Same here

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
2 participants
@elouanKeryell-Even @bax137