If you happen to simply need your node to make progress synchronizing towards the chaintip, it’s pointless to run the binary with the graphical person interface (bitcoin-qt). You possibly can simply run the headless program (bitcoind) as an alternative.
Bitcoin Core will solely allow a single occasion to make use of an information listing on the similar time, so calling bitcoind once more is not going to begin one other occasion if one is already working. You possibly can due to this fact have a cronjob that simply tries to begin bitcoind each 5 minutes, e.g., you may put into your crontab:
*/5 * * * * bitcoind -daemon
That mentioned, it’s completely surprising that your Bitcoin Core is crashing each hour. As talked about within the feedback in your different query, you would possibly wish to run some system checks to check for {hardware} failures. As you talked about there that your node has 8 GB of RAM, chances are you’ll wish to contemplate growing your DBCache from the default worth to synchronize extra rapidly after you determine the underlying concern for the crashes.
If you happen to simply need your node to make progress synchronizing towards the chaintip, it’s pointless to run the binary with the graphical person interface (bitcoin-qt). You possibly can simply run the headless program (bitcoind) as an alternative.
Bitcoin Core will solely allow a single occasion to make use of an information listing on the similar time, so calling bitcoind once more is not going to begin one other occasion if one is already working. You possibly can due to this fact have a cronjob that simply tries to begin bitcoind each 5 minutes, e.g., you may put into your crontab:
*/5 * * * * bitcoind -daemon
That mentioned, it’s completely surprising that your Bitcoin Core is crashing each hour. As talked about within the feedback in your different query, you would possibly wish to run some system checks to check for {hardware} failures. As you talked about there that your node has 8 GB of RAM, chances are you’ll wish to contemplate growing your DBCache from the default worth to synchronize extra rapidly after you determine the underlying concern for the crashes.
