Common Errors - Sjakil/gunthy-gui GitHub Wiki

Failed to connect to PM2 daemon

The GUI requires an instance of PM2 running in the background. PM2 requires NodeJS. If you get this error, make sure you have both of them installed.

Please follow the instructions on this wiki entry: "Install PM2".

Server port **** already in use

This means that the server port you've configured is already in use by another process. Either stop this other process or change your port in the configuration file.

Failed to validate licenses, please check your API keys

Your license could not be validated by the license server, please make sure you've entered your API key correctly. If you cannot solve the issue and are convinced this is wrong, please contact Sjakil.

Could not find configuration file "./gui-config.json" (, it most likely contains invalid JSON)

There was a problem loading the configuration file. It is either missing or contains a character that interferes with the JSON structure. You can use JSONLint to verify your JSON configuration.

Couldn't find gunbot executable ("./gunthy-xxxxxx")

The GUI requires the Gunbot executables to be presented in your Gunbot directory. It does not work with the NodeJS (.js) version. You can configure the location of this executable in the GUI configuration.

Couldn't load web server directory ("./gui")

This means the directory containing the web server files could not be located in your current working directory. Please make sure it is in place. You can always download the files again.

Error getting chart data / trade history / exchange balances (for kraken, poloniex, bittrex)

An error occured retrieving data from an exchange API. Most of the time these cannot be avoided. Keep an eye out for error number "403", this means something went wrong during authentication with the exchange, indicating there might be a problem with your key / secret.

If you get a lot of 422 errors, please make sure that you are not using the same API key as for the Gunbot. It is usually best practice to use different API keys for each application. This is because they might otherwise interfere with eachother.

*/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./gunthy-gui-linux-x64)

== Ubuntu ==

Basically, just execute the following commands:

sudo apt-get install libstdc++6

This should already be installed by default, but try it anyway. If it doesn't solve it, just do the following:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test 
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

As taken from: https://askubuntu.com/questions/575505/glibcxx-3-4-20-not-found-how-to-fix-this-error

== CentOS ==

You can confirm that you are not on version 3.4.20 of GLIBCXX, by using this command:

strings /usr/lib/gcc/x86_64-amazon-linux/4.8.3/libstdc++.so | grep GLIBCXX

You should not see version 3.4.20 here. In order to install it on your system, execute the commands below.

rpm --import https://www.centos.org/keys/RPM-GPG-KEY-CentOS-7
yum install libmpc-devel mpfr-devel gmp-devel zlib-devel* -y
curl ftp://ftp.gnu.org/pub/gnu/gcc/gcc-5.4.0/gcc-5.4.0.tar.bz2 -O
tar -xf gcc-5.4.0.tar.bz2
cd gcc-5.4.0
./configure --with-system-zlib --disable-multilib --enable-languages=c,c++
make -j 4
make install
gcc -v

Using the same command as before, you should now be able to see version 3.4.20.

strings /usr/lib/gcc/x86_64-amazon-linux/4.8.3/libstdc++.so | grep GLIBCXX

Thanks to thatcalifire!