Make sure that the user under which you are running your Oasis Node has a high-enough file descriptor limit as the databases can have many files open and running out of file descriptors can lead to the node stopping unexpectedly.
You can check the file descriptor limit by running the following as the same user that will run Oasis Node:
If this number is lower than 102400 you should consider increasing it by updating your system configuration. You can configure temporary limits by running:
ulimit -n 102400
Note that this limit only applies to any processes started from the same shell after the command was executed. If you want to make the change permanent, you have the following options.
root, create a file in
/etc/security/limits.d/99-oasis-node.conf with content similar to the following example:
* soft nofile 102400* hard nofile 1048576
You can replace
* with the name of the user that is running the Oasis Node in case you only want to change the limits for that particular user.
In case you are running your Oasis Node process via systemd, you can add the following directive under the
If you are running Oasis Node via Docker you can pass the following option to
docker run in order to increase the limit to desired values: