-
Notifications
You must be signed in to change notification settings - Fork 129
Common problems
- 3.1.1 Did you use active private key, not wallet password, when creating Worker
- 3.1.2 Did you use a separate account for each Worker
- 3.1.3 Did you write the whole asset name with prefix (BRIDGE.LTC, OPEN.ETH, BTS, USD, STEALTH, etc)
- 3.1.4 Did you make sure the account holds both the assets to be traded
- 3.1.5 Did you toggle the TURN WORKER ON/OFF button to make the Worker actually work
- 3.1.6 Is your computer clock synchronized
- 3.1.7 Are you running at least python 3.6?
- 3.1.8 To prevent disturbance to your Environment, consider using a virtualenv
3.2.1 If you get the following message at the end of an error message:
bitsharesapi.exceptions.UnhandledRPCError: Assert Exception: now <= trx.expiration
3.2.2 Sync your computer's clock. It should fix the error. Guide for reference
base58CheckDecode
-
3.3.1 Try upgrading the Python cryptography package with:
pip3 install --upgrade cryptographyand running again -
3.3.2 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. For details see here
AttributeError: can't set attribute
3.4.1.1 Fix by specifying graphenelib version: pip3 install graphenelib==0.6.2
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>
^~~~~~~~~~~~~~~
3.5.1. 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
3.5.2 Also see similar resolutions from steemit install issues
Best match: PyYAML 4.2b4
Processing PyYAML-4.2b4.tar.gz
Writing /tmp/easy_install-fccfyzzf/PyYAML-4.2b4/setup.cfg
Running PyYAML-4.2b4/setup.py -q bdist_egg --dist-dir /tmp/easy_install-fccfyzzf/PyYAML-4.2b4/egg-dist-tmp-bunv4mwn
In file included from ext/_yaml.c:565:0:
ext/_yaml.h:2:10: fatal error: yaml.h: No such file or directory
#include <yaml.h>
^~~~~~~~
compilation terminated.
Error compiling module, falling back to pure Python
3.6.1 To fix: pip3 install pyyaml to
install pyyaml-3.13
3.7.1 This means that 'pyuic5' is not in your PATH for some reason. Solution: find where 'pyuic5' is and add it into PATH:
export PATH=~/.local/bin:$PATH
3.8.1 Uninstall and install scrypt with pip3 uninstall scrypt and pip3 --user install scrypt
Possible error messages:
socket is already closed
3.9.1 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. Automatically changing nodes feature is available for the CLI version, soon to be on the GUI too.
3.10.1 Restart bot
3.11.1 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.
DEXBot is currently running on a minimum version of python3.6. If you have trouble upgrading your system to this version, please see this guide for help https://realpython.com/installing-python/
3.13.1 When using OSX or linux, consider installing dexbot in a virtual env so that it does not collide with other existing settings on your platform. Windows Users should try the Install Wizard but alternatively can install DEXBot on a Virtual Machine; using software like VirtualBox Also available for use with MacOS. This also enables experimentation with different versions. See this guide for how to use a virtualenv: