docs: Mention limit of file descriptors in Troubleshooting

propitech · May 29, 2021 · 3236f58 · 3236f58
1 parent 2ef832c
commit 3236f58
Showing 1 changed file with 10 additions and 1 deletion.
diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.md
@@ -15,6 +15,7 @@
 [windi]: /guide/plugins.html#windi-css
 [@vitejs/plugin-react-refresh]: https://www.npmjs.com/package/@vitejs/plugin-react-refresh
 [tag helpers]: /guide/development.html#tag-helpers-🏷
+[ulimit]: https://wilsonmar.github.io/maximum-limits/
 
 # Troubleshooting
 
@@ -68,10 +69,18 @@ In systems with constrained resources the [default timeout][devServerConnectTime
 
 If that doesn't work, verify that the [host] and [port] configuration is correct.
 
-### Requests to vite sporadically return a 404
+### Requests to vite sporadically return a 404 error response
 
 [See above](/guide/troubleshooting.html#build-is-triggered-when-the-dev-server-is-running), it could be related to the <kbd>[devServerConnectTimeout]</kbd>.
 
+### Requests to vite sporadically return a 500 error response
+
+Check your `ulimit -n` to make sure the limit of file descriptors is not [too low][ulimit].
+
+This is probably the case if you are seeing errors such as `#<Errno::EMFILE: Too many open files` along with `#<SocketError: Failed to open TCP connection`.
+
+Follow [this article][ulimit] for information on how to increase the limit of file descriptors in your OS.
+
 ### Changes are not taken into account, build is skipped
 
 Usually happens when importing code outside the <kbd>[sourceCodeDir]</kbd>.