-
Notifications
You must be signed in to change notification settings - Fork 45
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
The testnet runs for a long time and dfuseeos exits #215
Comments
error is "too many open files". Increase the number of files you allow open with the "ulimit" command. |
|
Will this "open files" be continuously accumulatively occupied or consumed? I am currently modifying it to 655350. After observing for a period of time, the test transfer pressure during my test chain is constant. I don't know if this "open files" keeps occupying more and more, will there be a problem. If the default value of the system is not enough to support the operation of dfuseeos, should you give a default value check prompt, or open the order of magnitude at the lower limit of the given parameter? |
The last part of the log of dfuse.log.json
After restarting, the log is as follows, observe that the synchronization is normal
But after continuing to synchronize for a period of time, the dfuseeos node exits again, the log is as follows
The text was updated successfully, but these errors were encountered: