You can get the total count of open file descriptors with:ĬOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME The WebSocket connection stays open for much longer than the HTTP request/response connection, so the network connections (and open file descriptors) accumulate. However, if you open and maintain a WebSocket connection for each user who stays on the site, you’ll find the count of file descriptors going up and up when visitors stay on your site.
You might never reach the limit and see this error. They are open from the time the server receives the request until it finishes responding and closes the connection to the client. If you are serving HTTP requests with HTTP responses, these file descriptors open and close quickly. A file descriptor can be a lot of things, including a handle to an input or output resource, such as a network connection. The problem really is that there are too many ‘file descriptors’ open.
But my app doesn’t read or write files to the file system! Here’s what I learned when I ran into this error hosting a Node.js app using WebSockets on Ubuntu.
0 kommentar(er)
