-
Notifications
You must be signed in to change notification settings - Fork 170
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
Increase FD size by default #207
Comments
BTW: the server has no file leaks at all, it’s just phar files and level db files that must be opened for basic functionality |
The --enable-fd-setsize flag is not available cross platform and so is not reasonable to modify by default. On linux systems, the FD size limit is overridden anyway, so changing the compile time limit won't make much difference. You can resolve this issue on your linux system by increasing the It should still be noted that hitting this limit is a very strong indicator that your server is leaking file handles instead of closing them and that the limit will not be hit under normal circumstances. |
I said there were no leaks. I debugged it and ONLY level db files were the main cause of the error. Servers with a big map and a lot of players suffer from this. |
leveldb has file handle limits precisely to avoid running into this limit. Whatever issue you're having, it's not leveldb's fault. |
I have 3 dimension worlds |
Your point being what exactly? |
@portfolec by any chance, are you loading every world in your server simultaneously? |
It should be compiled by default with increased size because 1024 isn’t enough for a big survival server with large map, a lot of active plugins and 200 online players!
Error: You MUST recompile PHP with a larger value of FD_SETSIZE. It is set to 1024, but you have descriptors numbered at least as high as 1038. --enable-fd-setsize=2048 is recommended, but you may want to set it to equal the maximum number of open files supported by your system, in order to avoid seeing this error again at a later date.
The text was updated successfully, but these errors were encountered: