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.

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

Error: EMFILE: too many open files, open #643

Open
masukomi opened this issue Mar 4, 2019 · 3 comments
Open

Error: EMFILE: too many open files, open #643

masukomi opened this issue Mar 4, 2019 · 3 comments

Comments

@masukomi
Copy link

masukomi commented Mar 4, 2019

I'm pounding on my local sbot with the following command

sbot links --dest "<id here>" --rel vote --values

I'm using a different id on each request. Somewhere after 10,000 requests (don't have enough scrollback in my terminal to tell you exactly where) I get this with every request. To me this suggests that something is not being cleaned up after each request.

{ Error: EMFILE: too many open files, open '/Users/masukomi/.ssb/gossip.json~'
  errno: -24,
  code: 'EMFILE',
  syscall: 'open',
  path: '/Users/masukomi/.ssb/gossip.json~' }
@christianbundy christianbundy self-assigned this Mar 5, 2019
@christianbundy
Copy link
Contributor

Thanks for reporting this! I think gossip.json~ is being created by atomic-file when modifications are done, but I'm unsure why that's happening on every request. Hmm.

@masukomi
Copy link
Author

masukomi commented Mar 6, 2019

update. reran with better logging and checking of exit codes. This happened again a little after 13700 requests. I have 74 copies of that error in the console output BEFORE it returned a non-zero exit code to the requesting process.

So, I think there are actually 2 errors.

  1. leaving stuff open
  2. failing to return a non-zero exit code on some requests that produce this result.

cc @christianbundy

@christianbundy christianbundy removed their assignment Jan 31, 2021
@stale
Copy link

stale bot commented Jun 2, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale stale bot added the stale label Jun 2, 2021
@staltz staltz removed the stale label Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants