-
Notifications
You must be signed in to change notification settings - Fork 129
Common problems
- Did you use active private key, not wallet password, when creating Worker
- Did you use a separate account for each Worker
- Did you write the whole asset name with prefix (BRIDGE.LTC, OPEN.ETH, BTS, USD, STEALTH, etc)
- Did you make sure the account holds both the assets to be traded
- Did you toggle the TURN WORKER ON/OFF button to make the Worker actually work
- Is your computer clock synchronized
If you get the following message at the end of an error message:
bitsharesapi.exceptions.UnhandledRPCError: Assert Exception: now <= trx.expiration
Sync your computer's clock. It should fix the error.
base58CheckDecode
- Try upgrading the Python cryptography package with:
pip3 install --upgrade cryptography
and running again - If you see errors about several private keys for the same account, you need to empty the wallet from keys. First delete all workers. Then run
uptick wipewallet
. Now there should be no wallet and no keys. Start from zero.
Graphenelib problem:
AttributeError: can't set attribute
Fix by specifying graphenelib version: pip3 install graphenelib==0.6.2
** Ubuntu 18.04, 18.10 Linux - AES problem on make install-user** Error on install:
scrypt-1.2.1/libcperciva/crypto/crypto_aes.c:6:10: fatal error: openssl/aes.h: No such file or directory #include <openssl/aes.h> ^~~~~~~~~~~~~~~
This is mainly due to the Ubuntu system was not able to find the scrypt package which can be easily fixed by
sudo apt-get install libssl-dev
Also see similar resolutions from steemit install issues
Uninstall and install scrypt with pip3 uninstall scrypt
and pip3 --user install scrypt
Possible error messages:
socket is already closed
Change the node defined in config.yml. See file location below. See what node gives you the lowest latency in the DEX, and copy it into the config file.
Restart bot
In BTS:MPA (Market Pegged Assets such as BitUSD and BitCNY) markets, if a force settlement fills your order, the bot doesn't yet recognize it and consequently disables itself because it isn't sure what happened. This will be fixed eventually but for time being just pause->play or restart the whole DEXBot-gui.