Troubleshoot a node on MacOS#
This guide describes how to troubleshoot a node running on MacOS on the Concordium network.
Node crash or database corruption#
A node crash or database corruption is the problem if:
the node fails to start
the node is in a restart loop with an error message about database corruption
or you get a “too few bytes” message.
The solution is to delete the relevant portion of the database.
The database directory should contain matching pairs of blockstate-$i.dat and treestate-$i files for some number of consecutive i’s starting at 0. The number of the files differs depending on which protocol version is current.
accountmap
blockstate-0.dat
blockstate-1.dat
blockstate-2.dat
treestate-0
treestate-1
treestate-2
To resolve a crash or non-starting node, delete files, starting at the largest i, until the node starts or until there are no more files in the directory.
If only one of
treestate-iorblockstate-$i.datfiles exists, delete the other and try starting the node.Otherwise delete both files of the
treestate-$iandblockstate-$i.datpair and try starting the node.
Service cannot run after editing service (config) file#
When configuring your node to be a validator on Mac, you need to edit the service file (which is owned by root). One way to edit it is to change the ownership to your user and then edit it. But then you cannot run the service.
To see if this is your problem, try to load the service manually:
$sudo launchctl load "/Library/Concordium Node/LaunchDaemons/software.concordium.mainnet.node.plist"
If your file ownership has changed, you will see the following:
/Library/Concordium Node/LaunchDaemons/software.concordium.mainnet.node.plist: Path had bad ownership/permissions
Load failed: 122: Path had bad ownership/permissions
To resolve the issue, change the file ownership back to root.
$sudo chown root "/Library/Concordium Node/LaunchDaemons/software.concordium.mainnet.node.plist"
