Errors and Troubleshooting
This document presents helpful hints to troubleshoot the errors you may get while working in the Bittensor ecosystem.
Priority is too low
Running a btcli command sometimes gives me the below error:
{'code': 1014, 'message': 'Priority is too low: (18446744073709551615 vs 18446744073709551615)', 'data': 'The transaction has too low priority to replace another transaction already in the pool.'}
Likely cause and remedy: This means that you are submitting the same, duplicate transaction that you have already submitted. For example, if you are running a script, it is trying to submit transactions too quickly, most likely. You just have to wait for a few minutes before you run the command again.
SSLCertVerificationError
Running any btcli command gives the following error, on macOS:
SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer
certificate (_ssl.c:1000)
Likely cause and remedy: The certifi version used in the openssl on your machine is incompatible with the Bittensor requirement. You can solve this issue by any one of the below ways:
Remedy 1: Follow this below exact method, as described in this StackOverflow page: https://stackoverflow.com/a/43855394:
Go to the folder where Python is installed, e.g., in my case (Mac OS) it is installed in the Applications folder with the folder name 'Python 3.6'. Now double click on 'Install Certificates.command'. You will no longer face this error.
Remedy 2: Run the below commands:
- On macOS when not using any Python virtual environment:
brew reinstall openssl - On macOS when using a virtual environment:
pip install urllib3 --force-reinstall
KeyFileError
KeyFileError: Keyfile at: /path/to/.bittensor/wallets/some-coldkey/hotkeys/somehotkey does not exist
Likely cause and remedy: A key you are passing as a parameter in a btcli command is not registered in the network. Make sure you first register the keys in your desired network before using the keys. See Register, Validate and Mine
.
Balances.transfer not found
ValueError: Call function 'Balances.transfer' not found
Likely cause and remedy: You are working with an older version of Bittensor. Update your Bittensor to the latest version. See Install Bittensor.
Genesis mismatch
Reason: Genesis mismatch. Banned, disconnecting.
These messages are mostly harmless and you can ignore them. Your lite node will sync properly. See the "best" block numbers in the terminal log. If these block numbers are closer or approaching the current block as seen on either https://bittensor.com/scan or Polkadot JS, then your local node is syncing properly.
You get these error messages very often because one or the other Bittensor blockchain validator nodes is running an older version of Polkadot SDK. When it says, "Banned, disconnecting", it is saying the mismatched blockchain validator node is being disconnected. This usually is fine because you don't need to be connected to all the blockchain validator nodes.