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

500 Internal Sever Error: Error: EMFILE: Too many open files, scandir 'directory' at Error (Native) #354

Closed
potatowave opened this issue Apr 2, 2017 · 8 comments

Comments

@potatowave
Copy link

potatowave commented Apr 2, 2017

Hi,

After about three days of uptime I've run into this error. http-server is serving some videos to one client instance of Google Chrome.

A quick Google shows people have fixed by using graceful-fs.

Also worth noting, I am serving about 10-15 video files here and that's it.

Any ideas?

@BigBlueHat
Copy link
Member

Any chance you can think of a way to test this that doesn't amount to running the server for 3+ days to see if it happens again? 😄 Also, what operating system and/or hosting are you using for running http-server?

@potatowave
Copy link
Author

It happens consistently after 3 days uptime. Currently I'm squashing it with a scheduled reboot. Running on Ubuntu 16.04, no hosting, local OS.

@BigBlueHat
Copy link
Member

Glad it's consistent at least! However, I'm not in a place to run the script for 3 days to see if it happens. 😃

We need to find a way to "force" it to break. Is it load? Is it memory? Is it time?

Just need help narrowing it down to something fixable.

@potatowave
Copy link
Author

I'll see if I can get any more diagnosis info if I encounter it again. Need to isolate a unit for testing.

@bigcat8886
Copy link

I'm running into this same issue too. Host OS - Win10, Client - Chrome. I'm serving several mp4 video. It doesn't take me 3 days to get into error, only takes several hours of streaming.

@potatowave
Copy link
Author

I never solved this with http-server.

I'd suggest running a dedicated Node.js server for your purpose. That's what I ended up doing.

@github-actions
Copy link

This issue has been inactive for 180 days

@github-actions github-actions bot added the stale label Oct 12, 2021
@thornjad
Copy link
Member

Without reasonable reproducibility, and since there's been no activity for years, I'm going to close this. Please do re-open if a way to reproduce (ideally within a test) is found!

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