nuts-foundation / nuts-foundation/nuts-node
Network notifiers fail to start, causing node to shut down
Open
@reinkrul is already working on this.
Since Apr 9, 2026.
bug
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Lots of network chatter (new transactions from many nodes) in combination with slower disk I/O can cause a Nuts node to fail to start:
network.connectToKnownNodes()causes syncing of the network, which can many transactions from many nodes- this leads to lots of write transactions, which block read transactions
- then the network notifiers are
Run()inStart(), but they fail due to lock time-outs - then the node stops because it couldn't start the network module
"Could not start the server" error="unable to start Network: failed to start notifiers: unable to obtain BBolt read lock: database error: context deadline exceeded
Mitigations:
- don't let
Start()return an error when it can't start a notifier; do it in a goroutine instead, retrying if it failed - limit the number of parallel TransactionList queries
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.