Running the binary
Run an Aleph node on the testnet for validating transactions with these instructions.
File descriptor limit
Since you are not running the node in a docker, there is one additional OS level configuration you have to take care of. The node uses a lot of file descriptors, both for network connections as well as database handling. To check the limit run:
If the returned value is at least 10000 you are set. Otherwise increase the limit to the recommended value by running:
Relogin and check the limit again to ensure the change took effect.
Run!
First, source the script you created two chapters back and set the config variables:
Once all of the variables mentioned in the previous chapters are set, you can start the node with the following command:
Further improvements
We recommend restarting the node automatically whenever it crashes. This is a rare occurrence, but were the node to crash you might miss the performance targets for a session and receive lower rewards. You should also set up some monitoring to check whether the node operates correctly – the prometheus endpoint is likely to be useful – including checking for crashloops. The details of such setups are beyond the scope of this guide.
Last updated
Was this helpful?