Troubleshooting Common Bitum Problems¶
Before starting any attempt at fixing a broken wallet, ensure you have your correct 33 word seed written down (preferably physically, on a piece of paper) and accessible.
If you have lost your seed, you are in serious danger of losing access to your funds permanently. See the “I have lost my seed” section of the seed FAQ for instructions in that situation.
Location of data and log files¶
The main directory for Bitum data files is OS-dependent:
|OS||Bitum data directory|
There are different log files which may be reviewed when troubleshooting a problem:
|Main app log||
And finally, the blockchain (bitumd) log is located in:
|OS||Bitum data directory|
Running in debug mode¶
To ease debugging of problems, you can run in debug mode in a terminal (command line console window). You need to open a terminal (
cmd.exe in Windows), navigate to the directory where Bitum is installed and then execute it:
# Linux/macOS: $ ./bitum --debug # Windows: c:\[...]> bitum.exe --debug
Cannot see all my coins after restoring from seed¶
Check if the blockchain is synchronized to the latest block. Look at the block height at the lower left corner of the screen and the latest block from explorer.bitum.io
Import all voting service provider (“stakepool”) API keys that you previously used with this wallet. If you do not perform this step for all pools, your balance will be incorrect.
Rebroadcast any pending transactions (access the transaction and click the “Rebroadcast” button) and verify in the block explorer if it has been published and mined.
Perform a full rescan of the transactions (click on the small refresh button besides the “Latest Block” label).
Bitum will not start (bitumd closed due to an error)¶
bitumd closed due to an error. Check bitumd logs and contact support if the issue persists.
There are generally three situations in which this error occurs:
- There’s already an instance of
bitumdrunning in your computer
bitumdprocess or the blockchain data is corrupt
- Something (like an antivirus or protection software) is preventing the
bitumdprocess from running correctly
Check the following:
Look at your OS task manager if there is any process named
bitumd, and terminate it.
Look at the bitumd logs for any
ERRtype of messages (start at the bottom of the file for the most recent messages).
If the blockchain has been corrupted, remove the bitumd data folder and restart the sync.
Disable any antivirus or protection software and try running again.
Run Bitum’s bitumd version in the terminal and look for any fatal messages or panics.
Error “Already Have Transaction…”¶
If you receive a message similar to the one above, it means your bitumd node already has the transaction you’re trying to publish. This is harmless, but if the transaction is left pending for a long time, you could try:
- Rebroadcast the transaction using the button in the Transactions tab
- Check if your transaction has been broadcast by using the block explorer
- Perform a rescan
Cannot Purchase Tickets¶
This is usually caused by shutting down Bitum before a ticket has been mined.
Perform the same steps as described in “Cannot see all my coins”
Debugging Other Errors¶
If you can start the wallet but get error messages when performing an operation, then the first thing is to verify the wallet logs from within Bitum. Access the Help -> Logs page and look for any ERR messages: