-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Dies on too many open files #70
Comments
I've raised the limit to 4096 but now it dies with this message:
|
btw, Marco, if you are using Mininet, try upgrading to the latest version. they added some code to raise these limits automatically (eg, open files to 10,000) back in August: mininet/mininet@b20c947 |
Thanks Andrew. I'm pretty sure I'm stumbling on a fd limit inside async_unix. |
Using On Tue, Jan 14, 2014 at 8:42 PM, Marco Canini [email protected]:
|
easier still, here's how to change the default from the command line: https://ocaml.janestreet.com/ocaml-core/109.58.00/doc/async/#Std.Async_config |
The file descriptor limit seems to be set to 1024 by async. This commit makes katnetic use a different entry point for the scheduler, which allows the user to configure the maximum number of file descriptors. Related to frenetic-lang/ocaml-openflow#70.
The file descriptor limit seems to be set to 1024 by async. This commit makes katnetic use a different entry point for the scheduler, which allows the user to configure the maximum number of file descriptors. Related to frenetic-lang/ocaml-openflow#70.
Hmm, brute force didn't really work. Still dying with "Too many open files" accept "((fd 6))" despite I raised the limit to 4096. |
I think we are leaking file descriptors. See this execution trace:
|
@mcanini, this has been resolved, correct? |
@seliopou: no this is not yet resolved -- with a bigger accept queue, we only moved off the point where we start leaking... |
Running on mininet with 80 switches crashes with the following backtrace:
The text was updated successfully, but these errors were encountered: