Generator-Gunbot - Setup GUNBOT v3.3.2 in less than 5 minutes (linux)

[lossbit]

ERROR! - There was an error starting GUNBOT for BTC_EXP:
1


I have this error everytime I want to run it. Any Idea?

get the same problem here.
trying use 1pair, the generator gunbot is ver 1.13, when i do update (npm generator-gunbot) still have same version rather than 1.8.

please advice me

thanks in advance

[beer-k0in]

ERROR! - There was an error starting GUNBOT for BTC_EXP:
1

get the same problem here.
please advice me

There are 2 possible issues.

The easy one

Type 'gl' and check if the pair you want to start is already running. Would look like this:


If it is in that list and its state is online, type 'gstop BTC_XXX' to stop it before you run 'ginit'.

The nasty one

Sometimes the PM2 God Deamon got detached from your (root-)user and you will see an empty list if you enter 'gl' BUT if you run 'pgrep -f BTC_XXX' you will see a id a result.

So the Gunbot is running but pm2 does not want to see it.

You need to kill the PM2 God Deamon, and remove the content in ~/.pm2/:

Code: [Select]

pgrep -f PM2 | xargs kill -9
Wait like 2 to 5 min till all Gunbots also stopped.
Check if there are running Gunbots

Code: [Select]

pgrep -f gunthyIf the dont stop, also kill them

Code: [Select]

pgrep -f gunthy | xargs kill -9
Now remove the content of ~/.pm2/

Code: [Select]

rm -r ~/.pm2/*
And run run 'ginit' again.


Please tell my if it was the easy or the nasty one.

BK

[Nael]

Any chance of a Bittrex version coming up soon?

[beer-k0in]

Any chance of a Bittrex version coming up soon?

Not so likely, sorry. I'm very busy this week. I hope I'll finish it by end of next week - but don't relay on that.

BK

[lossbit]

ERROR! - There was an error starting GUNBOT for BTC_EXP:
1

get the same problem here.
please advice me

There are 2 possible issues.

The easy one

Type 'gl' and check if the pair you want to start is already running. Would look like this:


If it is in that list and its state is online, type 'gstop BTC_XXX' to stop it before you run 'ginit'.

The nasty one

Sometimes the PM2 God Deamon got detached from your (root-)user and you will see an empty list if you enter 'gl' BUT if you run 'pgrep -f BTC_XXX' you will see a id a result.

So the Gunbot is running but pm2 does not want to see it.

You need to kill the PM2 God Deamon, and remove the content in ~/.pm2/:

Code: [Select]

pgrep -f PM2 | xargs kill -9
Wait like 2 to 5 min till all Gunbots also stopped.
Check if there are running Gunbots

Code: [Select]

pgrep -f gunIf the dont stop, also kill them

Code: [Select]

pgrep -f gun | xargs kill -9
Now remove the content of ~/.pm2/

Code: [Select]

rm -r ~/.pm2/*
And run run 'ginit' again.


Please tell my if it was the easy or the nasty one.

BK

thanks for fast respond bro. but you know i just deploy new server then install generator via putty and its work like charm!! haha. good job bro.keep it on
you deserve a beeer buddy!! hehehe

[teeftoof]

Is this common or have I done something wrong?  I keep getting 422 errors randomly on all my pairs. 

[beer-k0in]

Is this common or have I done something wrong?  I keep getting 422 errors randomly on all my pairs. 

There is nothing wrong. The GUNBOT handles errors on its own. No need to worry.

BK

[cw]

FYI - since "gstop all" and "gstart all" will likely cause 422 or 429 errors, I wrote a quick couple of scripts that nicely and safely start and stop the bots.

• start_bots.sh will start any stopped bots, but stagger start them with 3 seconds in between.
• stop_bots.sh will stop any online bots, but wait 3 seconds in between.

This should prevent any 429 errors and make it easy to manage the bots without having to make a bunch of custom scripts based on the pairs you're using.  Also note that it will only attempt to stop bots that are status=online, and will only attempt to start bots that are status=stopped.


Just select the code below and paste it in a bash terminal.  It will create the start_bots.sh and make it executable.  Then do the same for stop_bots.sh.

Code: [Select]

cat > start_bots.sh <<"EOF"
#!/bin/sh
#
#
echo "BEFORE:"
pm2 list


for i in `pm2 list | grep stopped | gawk '{print $2}'`
do
  echo "starting pair $i... and waiting 3 seconds"
  pm2 -s start $i
  sleep 3
done

echo "AFTER:"
pm2 list

EOF

chmod +x ./start_bots.sh



Code: [Select]

cat > stop_bots.sh <<"EOF"

#!/bin/sh
#
#
echo "BEFORE:"
pm2 list

for i in `pm2 list | grep online | gawk '{print $2}'`
do
  echo "stopping pair $i... and waiting 3 seconds"
  pm2 -s stop $i
  sleep 3
done

echo "AFTER:"
pm2 list

EOF

chmod +x ./stop_bots.sh



Here's a sample of what it looks like running:

First we stop them....

and then we start it up again.

[botreminer0011]

Great script.

How much memory is used by each pair (process app-name) ?

[CoinKombinat]

nice, thanks wally and so far, thanks alot mister mighty beer

[cw]

Great script.

Thank you!

How much memory is used by each pair (process app-name) ?

I believe that is shown in the "mem" column over on the right.

[botreminer0011]

Great script.

Thank you!

How much memory is used by each pair (process app-name) ?

Ooops, exact .....  100 Mb / pair.  For 20 pairs it's needed to have 2Gb + system memory ...

On Windows, it's 20-50 Mb /pair.

The difference is maybe PM2 environment ...




I believe that is shown in the "mem" column over on the right.

[beer-k0in]

I wrote a quick couple of scripts that nicely and safely start and stop the bots.

Year! Nice one! Thank you.

BK

[someone111]

Either instructions on generator-gunbot script is missing.

sudo apt-get install curl

This was hard to find out since all script output is hidden as well, so the script lacks error handling as well.

Thank you for all your work!

[beer-k0in]

Either instructions on generator-gunbot script is missing.

sudo apt-get install curl

This was hard to find out since all script output is hidden as well, so the script lacks error handling as well.

Thank you for all your work!

What OS are you using?

BK

[dcb942]

This looks fantastic. When will bittrex support be available?

[orthanc]

ERROR! - There was an error starting GUNBOT for BTC_EXP:
1

get the same problem here.
please advice me

There are 2 possible issues.

The easy one

Type 'gl' and check if the pair you want to start is already running. Would look like this:


If it is in that list and its state is online, type 'gstop BTC_XXX' to stop it before you run 'ginit'.

The nasty one

Sometimes the PM2 God Deamon got detached from your (root-)user and you will see an empty list if you enter 'gl' BUT if you run 'pgrep -f BTC_XXX' you will see a id a result.

So the Gunbot is running but pm2 does not want to see it.

You need to kill the PM2 God Deamon, and remove the content in ~/.pm2/:

Code: [Select]

pgrep -f PM2 | xargs kill -9
Wait like 2 to 5 min till all Gunbots also stopped.
Check if there are running Gunbots

Code: [Select]

pgrep -f gunIf the dont stop, also kill them

Code: [Select]

pgrep -f gun | xargs kill -9
Now remove the content of ~/.pm2/

Code: [Select]

rm -r ~/.pm2/*
And run run 'ginit' again.


Please tell my if it was the easy or the nasty one.

BK

I got the same error, and it was the nasty one that solved

[beer-k0in]

This looks fantastic. When will bittrex support be available?

2 or 3 weeks from now.

I got the same error, and it was the nasty one that solved

Glad you could fix it. For v2 I will try to be able to handle those pm2 issues automatically.


Thank you all for reporting bugs!

BK

[imwmi]

Hello everyone,

Looking for documentation on how to update the individual config files (per coin), if possible.

Can't seem to find what I need to clarify the steps on that.

[beer-k0in]

Looking for documentation on how to update the individual config files (per coin), if possible.

Not possible with the current version of the generator. You need to manually edit the config files. But keep in mind: the config in ALLPAIRS overwrites the config in the specific PAIR config. So you need to delete the parameter you want to be different among your pairs from ALLPAIRS and set it in every PAIR config.

BK