Messages

1

Technical Support & Development / Re: Important! Need EVERYONE to do this!

« on: September 06, 2017, 06:11:43 AM »

Done.  Better to request it now, ahead of time.

2

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT v3.3.2 in less than 5 minutes (linux)

« on: July 17, 2017, 04:50:50 PM »

UPDATE:  NOTE: some people reported that the following does not work for them, and I re-tested it on another one of my boxes and it did not work on my 2nd box.  So, I'm not sure why it worked on one box and not another.  Please take that into account.

I keep getting the nasty error where the root user unattaches and i'm trying to use the gunbot proxy as I had a lot of issues with 422s.  Is there any way to secure the root user in a better way to try to prevent that?

Also is there any way you can add a helpful section to your initial post about installing gproxy (https://github.com/taniman/gunbotproxycommunity) as it really helps when you are running multiple pairs.  Currently i'm at a point where I have the bot working on it's own and the proxy working but then at some point the whole setup crashes and I have to restart leading to errors.  Any idea why?

One tip is - the community proxy instructions say to edit the ALLPAIRS to add the snippet for the TLS environment variable at the bottom of the file there:

Code: [Select]

process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

However, ginit may overwrite that file, because generator-gunbot doesn't know what changes you're making to the file.  And you may use other tools in the future that aren't aware of the modifications you're making.

So, all you need is an environment variable.

You can add "export NODE_TLS_REJECT_UNAUTHORIZED=0" to your shell startup scripts (~/.bashrc for most people if linux), exit all your bash shells and screen sessions once, and then start them over and it will all work fine from then on.

Code: [Select]

echo "export NODE_TLS_REJECT_UNAUTHORIZED=0" >> ~/.bashrc

This adds that variable to your environment, so that when node runs, it knows to be ok with the man-in-the-middle TLS attack that the proxy does in order to intercept the SSL connection between gunbot and poloniex.

Now you don't have to edit the ALLPAIRS file and generator-gunbot can happily change it and not break your proxy.

3

Technical Support & Development / Re: EOS is launched on Kraken, but "unknown asset pair" on gunbot

« on: July 02, 2017, 05:39:44 AM »

Update: I have posted a support ticket at Kraken asking for further clarification. 
----

4

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT v3.3.2 in less than 5 minutes (linux)

« on: July 02, 2017, 05:27:45 AM »

Can somebody tell me the code to stop all pairs/stop the bot?

I only know how to stop single pairs.

I wrote a couple start/stop scripts detailed here on the forums that does this safely and without generating issues with the exchanges.    That way, you can just do start_bots.sh and stop_bots.sh.

You could use commands like "gstop all" and "gstart all" and "pm2 stop all" and "pm2 start all" but unless they've been modified since I last looked at them, they just start and stop them quickly, which makes places like polo and kraken run into API limits.  So that's why I wrote the scripts.

5

Technical Support & Development / EOS is launched on Kraken, but "unknown asset pair" on gunbot

« on: July 01, 2017, 09:20:23 PM »

Kraken launched a new coin - EOS and there surely will be a lot of profitable trading that I want to get on top of ASAP.  Read more on their blog post.

Launching kraken with "./gunthy-linuxx64 BTC_EOS kraken" just like my other kraken pairs but I get

Code: [Select]

2017/07/01 15:12:45 Error: Kraken API returned error: Query:Unknown asset pair.
Generally I have all the Kraken bots using ALLPAIRS and nothing in the per-pair... just a blank file.

So I tried different Kraken_asset_pair values in the kraken-BTC_EOS-config.js based on what Kraken publishes in their Asset Pairs Documentation.

Code: [Select]

   KRAKEN_ASSET_PAIR:'XXBTEOS'
   KRAKEN_ASSET_PAIR:'XXBTXEOS'
   KRAKEN_ASSET_PAIR:'EOSXBT'

Does gunbot itself need to be updated to support this?  Or is it possible that Kraken's API just isn't updated?

6

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT v3.3.2 in less than 5 minutes (linux)

« on: June 09, 2017, 06:22:18 PM »

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.

7

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT v3.3.2 in less than 5 minutes (linux)

« on: June 09, 2017, 05:16:10 PM »

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.

8

Beginners & Help / Re: Cryptowally's gunbot linux console, Part I

« on: May 26, 2017, 07:59:57 PM »

by the way, here are my latest versions... it helps colorize some of the items and clean up better.  Also, it alerts you of issues like Waiting for orders: 0 and things you need to fix.

Oooh, and a script that shows the latest trades of buys and sells... straight from the trades file.. in the local timezone

2017/05/26 10:00:34 buy 86.5056903114187 PIVX for 0.000578 BTC
2017/05/26 10:20:20 buy 602.4101385542169 SNGLS for 0.000083 BTC
2017/05/26 10:27:24 sell 86.50569031 BTC-PIVX for 0.00061245
2017/05/26 12:11:29 sell 39.95670799 BTC-STRAT for 0.00133799
2017/05/26 13:35:20 buy 82.64512809917356 PIVX for 0.000605 BTC
2017/05/26 13:41:24 buy 38.217157876835365 STRAT for 0.00130833 BTC

Here are the files you need

put the following into a file named "latesttrades-gb.sh"

Code: [Select]

#!/bin/sh

cat *trades.txt | sort | sed 's/\*\*\* MARKET CALLBACK | //' | tail -10


Here's the updated multitail.conf file:

Code: [Select]

#include:/etc/multitail.conf
#check_mail:0
colorscheme:gunbot
cs_re:red,magenta:< prBuy
cs_re:red,white:<= prBuy
cs_re:red,white:>= prSell
cs_re:red,yellow:> prSell
cs_re:yellow:.*< prSell.*
cs_re:red,yellow:Sell order placed
cs_re:red,yellow:.*ORDER INFORMATION.*
cs_re:red,yellow:.*profit.*
cs_re:white:.*MinPriceToSell.*
cs_re:white:.*MaxPriceToBuy.*
cs_re:white:.*MaxPriceToSell.*
cs_re:white:.*MinPriceToBuy.*
cs_re:yellow:^Direction:\s+\d+
cs_re:white,red:Rate limit exceeded
cs_re:white,red:Not enough BTC
cs_re:white,red:Waiting for orders: 0
cs_re:cyan:Waiting for orders: (\S+) (\S+)
cs_re:red:iInvalid nonce\!*
cs_re:red:ESOCKETTIMEDOUT\!*
cs_re:red:returned error\!*
cs_re:red:Error\!*
cs_re:red:.*failed.*
cs_re:red:.*no altcoins.*
cs_re:red:statusCode (.*)
cs_re:magenta:.*buy.*
cs_re:cyan:Open orders
cs_re:cyan:.*sell.*
cs_re:red:falls\syes
cs_re:green:grows\syes
cs_re:green:falls\sno
cs_re:yellow:Has order:.*
cs_re:yellow:.*have altcoins.*
cs_re:white:\:\:.*

And here's the updated stat.sh:

Code: [Select]

#!/bin/sh


multitail -Z red,black,inverse --config multitail.conf -CS gunbot -x "%m %u@%h %f (%t) [%l]" -b 4 -s 2 -m 0 -n 100 \
   --mark-interval 200 \
        -Ev "before to buy" \
        -Ev "Cannot sell" \
        -Ev "price to buy" \
        -Ev "MaxPriceToBuy" \
        -Ev "Open orders" \
        -Ev "have altcoins" \
        -Ev "Last price <=" \
        -Ev "Last price >=" \
        -Ev "Last price >" \
        -Ev "Last price >" \
        -Ev "price  grows \(" \
        -Ev "price  falls \(" \
        -Ev "^need " \
        -Ev "^Callback:" \
        -Ev "no altcoins" \
        -Ev "Altcoin Balance" \
        -Ev "\+\+\+"\
        -Ev "\[\]"\
        -Ev "-------" \
        -Ev "is too high" \
        -Ev "price is too low" \
        -Ev "price too high" \
        -Ev "waiting to sell" \
        -Ev "Creating market client" \
        -Ev "Loading config" \
        -Ev "Not supergun:" \
        -Ev "Supergun: " \
        -Ev "avCoins" \
        -Ev "CANCEL sell orders" \
        -Ev "CANCEL buy orders" \
        -Ev "SEll on start" \
        -Ev "^$" \
        -Ev "^\s+\d+\.\d+$" \
        -Ev "No order" \
        -Ev ":::" \
        -Ev "Error\!\!\! statusCode 422" \
        -Ev "Will repeat" \
        -Ev "cycle" \
        -Ev "No basePrice" \
        -Ev "need_" \
        -Ev "Response:" \
        -Ev "Bot responsed" \
        -Ev "next delay" \
        -Ev "^\*" \
        -Ev "\*\*" \
        .*/*-console.log \
   -ts -c- -Rc 10 -l "./latesttrades-gb.sh "

As before, just run it with "./stat.sh" to get a colorful status page of the status files.  Note that it might take a couple seconds for the trades to show up.

9

Technical Support & Development / Re: Bugs/Issues tracker v3.2

« on: May 26, 2017, 07:44:23 PM »

Not sure if it's worth reporting with a new version about to come out, but I did the following (I realize probably not supported... just posting in case someone else did or noticed the same)

• Was running build 2022 with bittrex on many pairs
• kept getting the Waiting for orders: 0 problem
• Stopped the bot and downgraded to build 2021
• restarted bot
• bot immediately fixed some of those orders and sold off some coins (YAY!)
• I still had some bags and I watched the bot for a while, and in this market I figured maybe I didn't want BB 25/25 any more
• I stopped the bot again and changed my configs from BB 25/25 and switched to buy:BB sell:STEPGAIN, and changed the 25 to 27
• now even though the orders have a boughtPrice, prSell is "NaN" so I don't konw if it will sell...

Did I do a "bad thing" by making the change while orders existed?  It knows the bought price, but I did change the sell strategy, so maybe the bot sets the sell price at time of purchase, and doesn't know to re-calculate that when the bot starts... and I screwed things.

So, essentially, here's the before config:

Code: [Select]

   BUY_STRATEGY: "BB",
   SELL_STRATEGY: "BB",
   LOW_BB: 25,
   HIGH_BB: 25,

and the before console output:

Code: [Select]

[ --2017/05/26 13:20:59--Bittrex--BTC_XRP  --  Gunbot v3.2 cycle #105 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00012557 - High BB:0.00012954
***************************************************
++++
LP 0.0001261  Bal.BTC 0.23618463  Bal.XRP 401.54242097(0)
Open orders
boughtPrice 0.00012452
price  falls (-2)
PriceToBuy 1.2373 priceToSell 1.3075
we have altcoins: 401.54242097
LP 1.2610000000000001 < prSell 1.3074600000000003  secMargin 0.0000061864827884615404  falls yes
price is too low to sell
Gunbot callback at 2017/05/26 13:21:01 cycle # 105
Callback:
---------
waiting to sell
need faster: no
need slower: no

next delay will be 38.208228131542924s


and here's the after config:

Code: [Select]

   BUY_STRATEGY: "BB",
   SELL_STRATEGY: "STEPGAIN",
   LOW_BB: 27,
   HIGH_BB: 27,

and the after console output:

Code: [Select]

zcash@zcash1:~/bit1$ ./gunthy-linuxx64 BTC_XRP bittrex | tee -a btc_xrp-console.log
Loading config...
Loading config...
Creating market client for BTC_XRP pair
Activating hot reconfig...
[ --2017/05/26 13:25:17--Bittrex--BTC_XRP  --  Gunbot v3.2 cycle #1 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00000000 - High BB:0.00000000
***************************************************
++++
LP 0.00012603  Bal.BTC 0.23618463  Bal.XRP 401.54242097(0)
Open orders
boughtPrice 0.00012452
price  steady (0)
PriceToBuy 0.0000 priceToSell --not set--
we have altcoins: 401.54242097
LP 1.2603000000000002 < prSell NaN  secMargin 0  falls no
price is too low to sell
Gunbot callback at 2017/05/26 13:25:19 cycle # 1
Callback:
---------
waiting to sell
need faster: no
need slower: no

next delay will be 45.88604473171423s


10

Technical Support & Development / Insufficient funds on 3.2 patch 2022 Kraken BTC_EUR

« on: May 25, 2017, 10:32:18 PM »

I read the Post about Re: Error Insuficient ZEUR funds on kraken and the Other post about "Re: EUR_BTC" but those posts are buying bitcoin with euro.

One of the users on telegram chat was asking about buying euro with bitcoin (going the other way) so I thought I'd try it.  I set up my config file and gunbot happily started running just fine.  It ran for a day or so, but when it came time to buy, when the buy order happened, the API returned "insufficient funds".

Here's the log from the file...

Code: [Select]

2017/05/24 18:15:34  [ --2017/05/24 18:15:34--kraken--BTC_EUR  --  Gunbot v3.2 cycle #134 --------------- ]
2017/05/24 18:15:34  ::::: collecting market data...
2017/05/24 18:15:38  LP 2094.88  Bal.XXBT 0.072567835  Bal.ZEUR 0
2017/05/24 18:15:38  Open orders
2017/05/24 18:15:38  boughtPrice undefined
2017/05/24 18:15:38  price  falls (-7)
2017/05/24 18:15:38  PriceToBuy,21008872.3234,priceToSell,--not set--
2017/05/24 18:15:38  LP 20948800.0000000,<=,prBuy 21008872.0000000  secMargin 210.0887232342344  grows yes
2017/05/24 18:15:38  no altcoins: 0
2017/05/24 18:15:38  price to buy: 2100.887232342344
2017/05/24 18:15:38  price is sweet to buy
2017/05/24 18:15:38  price is growing
2017/05/24 18:15:38  Buying on kraken 0.000523867715573207 of ZEUR for 2094.88
2017/05/24 18:15:38  ***************************************************
2017/05/24 18:15:38  [object Object]
2017/05/24 18:15:38  ***************************************************
2017/05/24 18:15:41  2017/05/24 18:15:41 Error: Kraken API returned error: Order:Insufficient funds
2017/05/24 18:15:41  !!! Cycle 135 failed. Will repeat in 92.38413441348112s
2017/05/24 18:17:13  [ --2017/05/24 18:17:13--kraken--BTC_EUR  --  Gunbot v3.2 cycle #135 --------------- ]


and here's the log from the console...

Code: [Select]

[ --2017/05/24 18:15:34--kraken--BTC_EUR  --  Gunbot v3.2 cycle #134 --------------- ]
::::: collecting market data...
++++
LP 2094.88  Bal.XXBT 0.072567835  Bal.ZEUR 0
Open orders
boughtPrice undefined
price  falls (-7)
PriceToBuy 21008872.3234 priceToSell --not set--
LP 20948800.0000000 <= prBuy 21008872.0000000  secMargin 210.0887232342344  grows yes
no altcoins: 0
price to buy: 2100.887232342344
price is sweet to buy
price is growing
Buying on kraken 0.000523867715573207 of ZEUR for 2094.88
***************************************************
{ pair: 'XXBTZEUR',
  type: 'buy',
  ordertype: 'limit',
  volume: 0.000523867715573207,
  price: 2094.88 }
***************************************************
2017/05/24 18:15:41 Error: Kraken API returned error: Order:Insufficient funds
!!! Cycle 135 failed. Will repeat in 92.38413441348112s
[ --2017/05/24 18:17:13--kraken--BTC_EUR  --  Gunbot v3.2 cycle #135 --------------- ]

I have bitcoin balance, as shown in the log... so I'm not certain why it's complaining.  I'm trying to buy Euro.

Did I do the asset pair wrong?  Or is this just not supported, and this asset pair only will ever go the primary way which is buying bitcoin with euro, and not buying euro with bitcoin?

If it matters, here's the relevant config and how it's launched

Code: [Select]

   DEFAULT_MARKET_NAME:"kraken",
   DEFAULT_CURRENCY_PAIR:"BTC_EUR",   //  single pair format for all markets !
   BTC_TRADING_LIMIT: 0.05,// max amount of BTC balance to use for each pair
   KRAKEN_ASSET_PAIR:'XXBTXEUR',

./gunthy-linuxx64 BTC_EUR kraken

Seems that it should still work, and treat EUR like any other "coin" to buy and sell.  I figured it would buy 0.05 bitcoin worth of Euro.

11

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT in less than 5 minutes (linux)

« on: May 22, 2017, 10:26:20 PM »

Can you please check again? I'm running the same droplet (2GB) with 16 pairs and my load is at 2% (Stepgain) to 4% (BB).

I checked my CPU again and sure enough, it quieted down a lot.  it's between 1-2%

12

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT in less than 5 minutes (linux)

« on: May 21, 2017, 07:35:55 PM »

Dude.   I love your new monitor.  We should probably team up somehow on our ideas. Did you see the mock up I posted in my link of the gunbot console I'm working on from last month?  Mine parses the logs as well (but is dependent on v203 console logs which is why I use "tee"). It looks like pm2 fixes this problem for me so I'm super happy to have found your post.  I never would have dove into pm2 without being curious about your amazing generator-gunbot script. 

I think we're on the same track, don't you?

I want a per-pair latest snapshot of useful info.  I do NOT want a log I have to scan. Logs don't help me see what is current.  Logs help me trouble what happened in the past.  Most of the time I want to see a snapshot of the NOW with a hint of the past.  I like a lot of what you put in there.  I'd add something like trades: x/x/x and that would be 1hr/6hr/12hr/24hr/ etc so we could see

Also gnuplot and other Linux CLI plotting tools have some powerful capabilities where I wanted to have some easy ANSI one liner visual tools to show activity per pair for trades, prices,  directions, profit (relative to all pairs in table) and all that stuff. 

For a while I thought the json would have what I wanted but in previous versions Gunthar only saved it when he made a trade.  I needed it updated every cycle and I asked that as a feature.  We'll see.  Because if we get that info not only could we do a CLI interface but we could do a PHP web interface as well if we wanted.  (With buttons and an API to tweak settings).

 

13

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT in less than 5 minutes (linux)

« on: May 20, 2017, 09:30:58 AM »

This is very nice - my hat's off to you.  I decided to give this a try, even though I have my own servers, equipment and typically do everything by hand, and I'm a big fan of GNU screen, so didn't know what could be better than it.  Besides, why would I pay for something in the cloud for something I have "for free" at home?

However, I'm always looking to learn new things, and I've seen people talking about "pm2" and wondered what it was all about.  Plus, even though what I have at home is "free", $10/mo isn't too bad given what I make with gunbot, and there is the convenience factor of better 24x7 uptime.  Then again, on one server at home, I'm able to run 50 pairs and the box is still only at 5% CPU (against three exchanges)... so we'll have to see and compare later about the costs... but that's a different story.

So I went through the installation instructions and they were perfect.  I'm extremely impressed by your startup script.  Easy to use, easy to understand, and fast response.  Good job.

I now understand better what pm2 does - it obviates the need for screen.  While I see the benefits that has... I also see that I lose some control that screen gives me. For one, I no longer see the console output I had, and I see to lose the direct interaction with the STDIN/STDOUT (but I may just be missing that - or maybe that's what "glog" does....)

Once I realized how incredibly valuable your startup scripts were, I had to add in my multitail pieces.... since pm2 takes care of the "tee" and "screen" parts! (written up in this post: https://gunthy.org/index.php?topic=261.msg1164#msg1164)

So, if you install multitail:

Code: [Select]

root@gunny:/opt/gunbot# sudo apt install multitail
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  multitail
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 121 kB of archives.
After this operation, 322 kB of additional disk space will be used.
Get:1 http://mirrors.digitalocean.com/ubuntu xenial/universe amd64 multitail amd64 6.4.2-1build1 [121 kB]
Fetched 121 kB in 0s (1,258 kB/s)
Selecting previously unselected package multitail.
(Reading database ... 62956 files and directories currently installed.)
Preparing to unpack .../multitail_6.4.2-1build1_amd64.deb ...
Unpacking multitail (6.4.2-1build1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up multitail (6.4.2-1build1) ...

Create a file called "multitail.conf" in the /opt/gunbot directory:

Code: [Select]

#include:/etc/multitail.conf
#check_mail:0
colorscheme:gunbot
cs_re:red,magenta:< prBuy
cs_re:red,white:<= prBuy
cs_re:red,white:>= prSell
cs_re:red,yellow:> prSell
cs_re:red,yellow:Sell order placed
cs_re:red,yellow:.*ORDER INFORMATION.*
cs_re:red,yellow:.*profit.*
cs_re:white:.*MinPriceToSell.*
cs_re:white:.*MaxPriceToBuy.*
cs_re:white:.*MaxPriceToSell.*
cs_re:white:.*MinPriceToBuy.*
cs_re:yellow:^Direction:\s+\d+
cs_re:white,blue:Activating hot reconfig...
cs_re:white,red:INVALID LICENSE
cs_re:white,red:Rate limit exceeded
cs_re:white,red:Not enough BTC
cs_re:red:iInvalid nonce\!*
cs_re:red:ESOCKETTIMEDOUT\!*
cs_re:red:returned error\!*
cs_re:red:Error\!*
cs_re:red:.*failed.*
cs_re:red:.*no altcoins.*
cs_re:red:statusCode (.*)
cs_re:magenta:.*buy.*
cs_re:cyan:Open orders
cs_re:cyan:.*sell.*
cs_re:red:falls\syes
cs_re:green:grows\syes
cs_re:green:falls\sno
cs_re:yellow:Has order:.*
cs_re:yellow:.*have altcoins.*
cs_re:white:\:\:.*

Create a file called "stat.sh" in same directory:

Code: [Select]

#!/bin/sh
multitail -Z red,black,inverse --config multitail.conf -CS gunbot -x "%m %u@%h %f (%t) [%l]" -b 4 -s 2 -m 0 -n 100 \
   --mark-interval 200 \
        -Ev "before to buy" \
        -Ev "Cannot sell" \
        -Ev "price to buy" \
        -Ev "MaxPriceToBuy" \
        -Ev "Last price <=" \
        -Ev "Last price >=" \
        -Ev "Last price >" \
        -Ev "Last price >" \
        -Ev "price  grows \(" \
        -Ev "price  falls \(" \
        -Ev "^need " \
        -Ev "^Callback:" \
        -Ev "no altcoins" \
        -Ev "Altcoin Balance" \
        -Ev "\+\+\+"\
        -Ev "\[\]"\
        -Ev "-------" \
        -Ev "is too high" \
        -Ev "price is too low" \
        -Ev "price too high" \
        -Ev "waiting to sell" \
        -Ev "Creating market client" \
        -Ev "Loading config" \
        -Ev "Not supergun:" \
        -Ev "Supergun: " \
        -Ev "avCoins" \
        -Ev "CANCEL sell orders" \
        -Ev "CANCEL buy orders" \
        -Ev "SEll on start" \
        -Ev "^$" \
        -Ev "^\s+\d+\.\d+$" \
        -Ev "No order" \
        -Ev ":::" \
        -Ev "Error\!\!\! statusCode 422" \
        -Ev "Will repeat" \
        -Ev "cycle" \
        -Ev "No basePrice" \
        -Ev "need_" \
        -Ev "Response:" \
        -Ev "Bot responsed" \
        -Ev "next delay" \
        -Ev "^\*" \
        -Ev "\*\*" \
        /root/.pm2/logs/*-out*.log

Make the file executable:

Code: [Select]

root@gunny:/opt/gunbot# chmod +x ./stat.sh

and run the stats page...

Code: [Select]

./stat.sh

Then you can get a single page viewer of all the log files ... BUT FILTERED AND COLORED so you can watch them, but only the interesting parts.  I can't see them very easily right now because evidently I have an invalid license... so the screenshot isn't very useful.  Also, I'm composing this on my laptop right now, so the monitor isn't very large, so each window is a bit smaller than normal.  Typically you'd see a few more lines of each bot instance.



If there's a multitail-like console built-in to pm2, and I missed it, let me know.  If you read the link to my post above, I go into great detail about why I put together my multitail console and the ideas I have for the next one.

All in all, I have to say - great work!


Also, FYI - I started 16 pairs on a 2GB memory / 40GB / SFO2 Ubuntu 16.04.2 x64 unit and CPU is pegged at 100% - just wanted to pass that along to others.

14

Technical Support & Development / Re: Bugs/Issues tracker v3.2

« on: May 19, 2017, 04:24:02 AM »

Kraken, 3.2, linux, BTC_XMR "unhandled rejection error"

First time to see this error - also first time to see "canceling buy orders" as well.  I scrolled back and saw 8 of them for this bot instance.

Code: [Select]

[ --2017/05/18 21:43:30--kraken--BTC_XMR  --  Gunbot v3.2 cycle #823 --------------- ]
::::: collecting market data...
++++
--canceling buy orders
LP 0.01608  Bal.XXBT 0.761572648  Bal.XXMR 0
Open orders
boughtPrice undefined
price  falls (-3)
PriceToBuy 157.0707 priceToSell --not set--
LP 160.8000000 > prBuy 157.0706800  secMargin 0.0015707067733333347  grows no
no altcoins: 0
price to buy: 0.015707067733333347
last price is too high
Gunbot callback at 2017/05/18 21:43:34 cycle # 823
Callback:
---------
price too high
need faster: no
need slower: no

next delay will be 73.40860242239326s


Error: Kraken API returned error: API:Invalid nonce
Unhandled rejection Error: Error: Kraken API returned error: API:Invalid nonce
    at KrakenClient.console./snapshot/Users/Enrico/Desktop/xBot_v2.9.3/kraken.js.module.exports.Market.getOpenOrders.Promise.kraken.api (evalmachine.<anonymous>:0:0)
    at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/kraken-api/kraken.js:155:23)
    at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:192:7)
    at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:186:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

[ --2017/05/18 21:44:47--kraken--BTC_XMR  --  Gunbot v3.2 cycle #824 --------------- ]
::::: collecting market data...
+++2017/05/18 21:44:49 Error: Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 825 failed. Will repeat in 107.50140008436689s


Note that the message in red showed up to STDERR and not STDOUT - so it doesn't show up in my "tee -a console.log" nor does it show up in the -err.log.... only actually in the terminal output.  Maybe this kind of error happens every time there's an invalid nonce error... and maybe not.  I thought it better than I report it.

15

Beginners & Help / Re: Cryptowally's gunbot linux console, Part I

« on: May 18, 2017, 09:39:11 PM »

I installed 3.2 and started working with Kraken exchange.  I've modified a stats.sh launcher and the multitail.conf file to change how things display, but the new console has so much on it, that it's difficult to fit it all into a window if running too many pairs.  So I've had to cut out a number of lines...

Also, I've noticed a few discrepancies in this version, like the console eventually will report "Open orders" whether or not there are open orders.

Anyway, here's how it looks so far:

And here are the changes to the files:

(for my new 3.2, I started to lump all the bots into one directory instead of each into it's own directory.  Now that it supports ALLPAIRS, it seems better to have them together. So you'll see that I changed it to be .*/*-console.log for example)

Code: [Select]

#!/bin/sh

multitail -Z red,black,inverse --config multitail.conf -CS gunbot -x "%m %u@%h %f (%t) [%l]" -b 4 -s 2 -m 0 -n 100 \
   --mark-interval 200 \
   -Ev "before to buy" \
   -Ev "Cannot sell" \
   -Ev "price to buy" \
   -Ev "MaxPriceToBuy" \
   -Ev "Last price <=" \
   -Ev "Last price >=" \
   -Ev "Last price >" \
   -Ev "Last price >" \
   -Ev "price  grows \(" \
   -Ev "price  falls \(" \
   -Ev "^need " \
   -Ev "^Callback:" \
   -Ev "no altcoins" \
   -Ev "Altcoin Balance" \
   -Ev "\+\+\+"\
   -Ev "\[\]"\
   -Ev "-------" \
   -Ev "is too high" \
   -Ev "price is too low" \
   -Ev "price too high" \
   -Ev "waiting to sell" \
   -Ev "Creating market client" \
   -Ev "Loading config" \
   -Ev "Not supergun:" \
   -Ev "Supergun: " \
   -Ev "avCoins" \
   -Ev "CANCEL sell orders" \
   -Ev "CANCEL buy orders" \
   -Ev "SEll on start" \
   -Ev "^$" \
   -Ev "^\s+\d+\.\d+$" \
   -Ev "No order" \
   -Ev ":::" \
   -Ev "Error\!\!\! statusCode 422" \
   -Ev "Will repeat" \
   -Ev "cycle" \
   -Ev "No basePrice" \
   -Ev "need_" \
   -Ev "Response:" \
   -Ev "Bot responsed" \
   -Ev "next delay" \
   -Ev "^\*" \
   -Ev "\*\*" \
   .*/*-console.log \
   -ts -c- -Rc 10 -l "./latesttrades.sh "


Code: [Select]

#include:/etc/multitail.conf
#check_mail:0
colorscheme:gunbot
cs_re:red,magenta:< prBuy
cs_re:red,white:<= prBuy
cs_re:red,white:>= prSell
cs_re:red,yellow:> prSell
cs_re:red,yellow:Sell order placed
cs_re:red,yellow:.*ORDER INFORMATION.*
cs_re:red,yellow:.*profit.*
cs_re:white:.*MinPriceToSell.*
cs_re:white:.*MaxPriceToBuy.*
cs_re:white:.*MaxPriceToSell.*
cs_re:white:.*MinPriceToBuy.*
cs_re:yellow:^Direction:\s+\d+
cs_re:white,red:Rate limit exceeded
cs_re:white,red:Not enough BTC
cs_re:red:iInvalid nonce\!*
cs_re:red:ESOCKETTIMEDOUT\!*
cs_re:red:returned error\!*
cs_re:red:Error\!*
cs_re:red:.*failed.*
cs_re:red:.*no altcoins.*
cs_re:red:statusCode (.*)
cs_re:magenta:.*buy.*
cs_re:cyan:Open orders
cs_re:cyan:.*sell.*
cs_re:red:falls\syes
cs_re:green:grows\syes
cs_re:green:falls\sno
cs_re:yellow:Has order:.*
cs_re:yellow:.*have altcoins.*
cs_re:white:\:\:.*


16

Technical Support & Development / Re: Bugs/Issues tracker v3.2

« on: May 18, 2017, 05:06:26 PM »

My first time running 3.2 and just got the bot running on Kraken.  This is the first buy.  It's missing bought price on LTC
I've stopped gunbot and restarted but still, boughtPRice undefined and priceToSell not set.  Although, we know the price was 0.01393514.
Is it the nonce errors?  Did I do something wrong with the API?

Now that the bot has run a while, there have been more purchases.  Looks like all the other orders have boughtPrice set once an order was set.

Working:

• BTC_DASH
• BTC_ETC
• BTC_ETH
• BTC_XLM
• BTC_XRP
• BTC_ZEC
• BTC_GNO

I notice that for the ones that have the boughtprice, there are entries in the *-trades.txt files.  Notice the one not working... BTC_LTC... does NOT have anything in it's kraken-BTC_LTC-trades.txt file. It's still empty.

Code: [Select]

zcash@zcash1:~/kraken-set2$ grep CALLBACK  *trades.txt
kraken-BTC_DASH-trades.txt:2017/05/18 10:11:06 *** MARKET CALLBACK | buy 1.09629434 DASHXBT @ limit 0.045629
kraken-BTC_DASH-trades.txt:2017/05/18 10:14:21 *** MARKET CALLBACK | buy 1.09629434 DASHXBT @ limit 0.045629
kraken-BTC_DASH-trades.txt:2017/05/18 10:20:08 *** MARKET CALLBACK | buy 1.09629434 DASHXBT @ limit 0.045629
kraken-BTC_DASH-trades.txt:2017/05/18 10:26:47 *** MARKET CALLBACK | buy 1.09624631 DASHXBT @ limit 0.045631
kraken-BTC_DASH-trades.txt:2017/05/18 10:28:17 *** MARKET CALLBACK | buy 1.09624631 DASHXBT @ limit 0.045631
kraken-BTC_ETC-trades.txt:2017/05/18 09:50:11 *** MARKET CALLBACK | buy 15.34611391 ETCXBT @ limit 0.00325826
kraken-BTC_ETC-trades.txt:2017/05/18 09:51:19 *** MARKET CALLBACK | buy 15.18980429 ETCXBT @ limit 0.00329179
kraken-BTC_ETH-trades.txt:2017/05/18 09:56:09 *** MARKET CALLBACK | buy 1.01676016 ETHXBT @ limit 0.049200
kraken-BTC_GNO-trades.txt:2017/05/18 10:32:29 *** MARKET CALLBACK | buy 0.72464442 GNOXBT @ limit 0.069047
kraken-BTC_GNO-trades.txt:2017/05/18 10:33:46 *** MARKET CALLBACK | buy 0.72464442 GNOXBT @ limit 0.069047
kraken-BTC_GNO-trades.txt:2017/05/18 10:35:06 *** MARKET CALLBACK | buy 0.72464442 GNOXBT @ limit 0.069047
kraken-BTC_XLM-trades.txt:2017/05/18 09:36:29 *** MARKET CALLBACK | buy 2067.82514846 XLMXBT @ limit 0.00002418
kraken-BTC_XRP-trades.txt:2017/05/18 09:40:02 *** MARKET CALLBACK | buy 270.27077027 XRPXBT @ limit 0.00018500
kraken-BTC_ZEC-trades.txt:2017/05/18 10:01:00 *** MARKET CALLBACK | buy 1.01443141 ZECXBT @ limit 0.049313

The error file looks like this around that time:

Code: [Select]

::::2017/05/18 04:41:10 Error Kraken API returned error: API:Invalid nonce
::::2017/05/18 04:43:54 Error Error: Error in server response: {"code":"ESOCKETTIMEDOUT","connect":false}
::::2017/05/18 04:45:56 Error Error in server response: {"code":"ESOCKETTIMEDOUT","connect":false}
::::2017/05/18 04:47:48 Error Error: Kraken API returned error: API:Invalid nonce
::::2017/05/18 04:49:40 Error Error: Kraken API returned error: API:Invalid nonce
::::2017/05/18 04:51:33 Error Missing boughtPrice
::::2017/05/18 04:53:25 Error Missing boughtPrice
::::2017/05/18 04:55:17 Error Missing boughtPrice
::::2017/05/18 04:57:09 Error Error: Kraken API returned error: API:Invalid nonce
::::2017/05/18 04:59:00 Error Missing boughtPrice
::::2017/05/18 05:00:51 Error Kraken API returned error: API:Invalid nonce

and that's where it first starts with the "missing boughtPrice" errors

By the way, I have the following settings:

Code: [Select]

        BUYLVL1: 3,
        BUYLVL2: 5,
        SELLLVL1: 3,
        SELLLVL2: 7,
        BUYLVL: 1,
        SELLLVL: 1,
        BUY_STRATEGY: "GAIN", // accepted values BB or STEPGAIN or GAIN or PINGPONG
        SELL_STRATEGY: "STEPGAIN", // accepted values BB or STEPGAIN or GAIN or PINGPONG
        LOW_BB: 25,
        HIGH_BB: 25,
        PINGPONG_BUY: 0.001,
        PINGPONG_SELL: 0.002,
        BUY_LEVEL: 3, // If GAIN buy strategy is used, buy at this percentual below lower ema value
        GAIN: 5, // If GAIN sell strategy is used, sell at this percentual above bought price
        BTC_TRADING_LIMIT: 0.05,// max amount of BTC balance to use for each pair

But it sure looks like it made multiple orders.  I see two ETC orders there for 0.05 BTC.  Also, I see 5 open orders for dash and 3 open GNO orders (see below).  Is this expected?

If it helps, here are the closed orders in Kraken:


And interestingly, here are the "new and open orders" which lists GNO and DASH orders.

17

Technical Support & Development / Re: Bugs/Issues tracker v3.2

« on: May 18, 2017, 01:39:41 PM »

Looks like on 3.2, at least on Kraken (the only 3.2 I'm running at the moment), when it gets a 502 error, the bot is dumping the HTML response to the console instead of catching it and just reporting the 502.

Code: [Select]

[ --2017/05/18 07:33:33--kraken--BTC_DASH  --  Gunbot v3.2 cycle #213 --------------- ]
::::: collecting market data...
2017/05/18 07:33:35 Error: Could not understand response from server: <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]>    <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>
<meta http-equiv="set-cookie" content="cf_use_ob=0; expires=Thu, 18-May-17 12:34:05 GMT; path=/">
<title>api.kraken.com | 502: Bad gateway</title>
<meta charset="UTF-8"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1"/>
<meta name="robots" content="noindex, nofollow"/>
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1"/>
<link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" type="text/css" media="screen,projection"/>
<!--[if lt IE 9]><link rel="stylesheet" id='cf_styles-ie-css' href="/cdn-cgi/styles/cf.errors.ie.css" type="text/css" media="screen,projection" /><![endif]-->
<style type="text/css">body{margin:0;padding:0}</style>
<!--[if lte IE 9]><script type="text/javascript" src="/cdn-cgi/scripts/jquery.min.js"></script><![endif]-->
<!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/zepto.min.js"></script><!--<![endif]-->
<script type="text/javascript" src="/cdn-cgi/scripts/cf.common.js"></script>
</head>
<body>
<div id="cf-wrapper">
<div id="cf-error-details" class="cf-error-details-wrapper">
<div class="cf-wrapper cf-error-overview">
<h1>
<span class="cf-error-type" data-translate="error">Error</span>
<span class="cf-error-code">502</span>
<small class="heading-ray-id">Ray ID: 360ed87d7f50583d &bull; 2017-05-18 12:33:35 UTC</small>
</h1>
<h2 class="cf-subheadline" data-translate="error_desc">Bad gateway</h2>
</div>
<div class="cf-section cf-highlight cf-status-display">
<div class="cf-wrapper">
<div class="cf-columns cols-3">
<div id="cf-browser-status" class="cf-column cf-status-item cf-browser-status ">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-browser"></i>
<i class="cf-icon-status cf-icon-ok"></i>
</div>
<span class="cf-status-desc" data-translate="browser_desc">You</span>
<h3 class="cf-status-name" data-translate="browser_label">Browser</h3>
<span class="cf-status-label" data-translate="browser_status_label">Working</span>
</div>
<div id="cf-cloudflare-status" class="cf-column cf-status-item cf-cloudflare-status ">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-cloud"></i>
<i class="cf-icon-status cf-icon-ok"></i>
</div>
<span class="cf-status-desc" data-translate="cloud_desc">Location</span>
<h3 class="cf-status-name" data-translate="cloud_label">Cloudflare</h3>
<span class="cf-status-label" data-translate="cloud_status_label">Working</span>
</div>
<div id="cf-host-status" class="cf-column cf-status-item cf-host-status cf-error-source">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-server"></i>
<i class="cf-icon-status cf-icon-error"></i>
</div>
<span class="cf-status-desc" data-translate="server_desc">api.kraken.com</span>
<h3 class="cf-status-name" data-translate="server_label">Host</h3>
<span class="cf-status-label" data-translate="server_status_label">Error</span>
</div>
</div>
</div>
</div>
<div class="cf-section cf-wrapper">
<div class="cf-columns two">
<div class="cf-column">
<h2 data-translate="what_happened">What happened?</h2>
<p>The web server reported a bad gateway error.</p>
</div>
<div class="cf-column">
<h2 data-translate="what_can_i_do">What can I do?</h2>
<p data-translate="try_again_in_a_few">Please try again in a few minutes.</p>
</div>
</div>
</div>
<div class="cf-error-footer cf-wrapper">
<p>
<span class="cf-footer-item">Cloudflare Ray ID: <strong>360ed87d7f50583d</strong></span>
<span class="cf-footer-separator">&bull;</span>
<span class="cf-footer-item"><span data-translate="your_ip">Your IP</span>: x.x.x.x</span>
<span class="cf-footer-separator">&bull;</span>
<span class="cf-footer-item"><span data-translate="performance_security_by">Performance &amp; security by</span> <a data-orig-proto="https" data-orig-ref="www.cloudflare.com/5xx-error-landing?utm_source=error_footer" id="brand_link" target="_blank">Cloudflare</a></span>
</p>
</div>
</div>
</div>

!!! Cycle 214 failed. Will repeat in 102.9763402239914s


Seems that maybe this should be caught by gunbot and just reported as a 502 or whatever.

18

Technical Support & Development / Re: Bugs/Issues tracker v3.2

« on: May 18, 2017, 01:30:58 PM »

Kraken, 3.2, looks like low value coins uses wrong price in the API call.  Yes, I know it's DOGE and yes, I know it's a memecoin.  I have my settings for high percentage pumps and I like to play around with them.

2017/05/18 05:43:08 Error: Kraken API returned error: General:Invalid arguments:price

Notice the price is in the 7.7e-7 format instead of a real number format.

Code: [Select]

[ --2017/05/18 05:43:03--kraken--BTC_XDG  --  Gunbot v3.2 cycle #193 --------------- ]
::::: collecting market data...
++++
LP 7.7e-7  Bal.XXBT 0.94946381  Bal.XXDG 0
No open orders
boughtPrice undefined
price  grows (1)
PriceToBuy 0.0077 priceToSell --not set--
LP 0.0077000 <= prBuy 0.0077052  secMargin 7.70521296296296e-8  grows yes
no altcoins: 0
price to buy: 7.70521296296296e-7
price is sweet to buy
price is growing
Buying on kraken 64935.065435064935 of XXDG for 7.7e-7
***************************************************
{ pair: 'XXDGXXBT',
  type: 'buy',
  ordertype: 'limit',
  volume: 64935.065435064935,
  price: 7.7e-7 }
***************************************************
2017/05/18 05:43:08 Error: Kraken API returned error: General:Invalid arguments:price
!!! Cycle 194 failed. Will repeat in 91.57627247026898s
[ --2017/05/18 05:44:40--kraken--BTC_XDG  --  Gunbot v3.2 cycle #194 --------------- ]
::::: collecting market data...
++++
LP 7.8e-7  Bal.XXBT 0.94946381  Bal.XXDG 0
No open orders
boughtPrice undefined
price  grows (2)
PriceToBuy 0.0077 priceToSell --not set--
LP 0.0078000 > prBuy 0.0077030  secMargin 7.703045871559632e-8  grows yes
no altcoins: 0
price to buy: 7.703045871559631e-7
last price is too high
Gunbot callback at 2017/05/18 05:44:46 cycle # 194
Callback:
---------
price too high
need faster: yes
need slower: no

next delay will be 37.32549462607416s



I'll turn off this pair for the time being.

19

Technical Support & Development / Re: Bugs/Issues tracker v3.2

« on: May 18, 2017, 12:52:03 PM »

My first time running 3.2 and just got the bot running on Kraken.  This is the first buy.  It's missing bought price on LTC

Code: [Select]

[ --2017/05/18 04:42:57--kraken--BTC_LTC  --  Gunbot v3.2 cycle #104 --------------- ]
::::: collecting market data...
++++
LP 0.014014  Bal.XXBT 0.9995  Bal.XLTC 0
No open orders
boughtPrice undefined
price  falls (-6)
PriceToBuy 139.3456 priceToSell --not set--
LP 140.1400000 > prBuy 139.3455700  secMargin 0.0013934557384615387  grows yes
no altcoins: 0
price to buy: 0.013934557384615387
last price is too high
Gunbot callback at 2017/05/18 04:43:03 cycle # 104
Callback:
---------
price too high
need faster: yes
need slower: no

next delay will be 44.91294049568045s


[ --2017/05/18 04:43:48--kraken--BTC_LTC  --  Gunbot v3.2 cycle #105 --------------- ]
::::: collecting market data...
+++2017/05/18 04:43:54 Error: Error: Error in server response: {"code":"ESOCKETTIMEDOUT","connect":false}
!!! Cycle 106 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:45:41--kraken--BTC_LTC  --  Gunbot v3.2 cycle #106 --------------- ]
::::: collecting market data...
++++
LP 0.013927  Bal.XXBT 0.9995  Bal.XLTC 0
No open orders
boughtPrice undefined
price  falls (-8)
PriceToBuy 139.2939 priceToSell --not set--
LP 139.2700000 <= prBuy 139.2939100  secMargin 0.0013929391060606058  grows yes
no altcoins: 0
price to buy: 0.013929391060606058
price is sweet to buy
price is growing
Buying on kraken 3.5906486321533713 of XLTC for 0.013927
***************************************************
{ pair: 'XLTCXXBT',
  type: 'buy',
  ordertype: 'limit',
  volume: 3.5906486321533713,
  price: 0.013927 }
***************************************************
2017/05/18 04:45:56 Error: Error in server response: {"code":"ESOCKETTIMEDOUT","connect":false}
!!! Cycle 107 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:47:43--kraken--BTC_LTC  --  Gunbot v3.2 cycle #107 --------------- ]
::::: collecting market data...
++2017/05/18 04:47:48 Error: Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 108 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:49:35--kraken--BTC_LTC  --  Gunbot v3.2 cycle #108 --------------- ]
::::: collecting market data...
++2017/05/18 04:49:40 Error: Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 109 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:51:28--kraken--BTC_LTC  --  Gunbot v3.2 cycle #109 --------------- ]
::::: collecting market data...
++++
LP 0.013973  Bal.XXBT 0.94946381  Bal.XLTC 3.59064863
No open orders
boughtPrice undefined
price  falls (-8)
PriceToBuy 139.2312 priceToSell --not set--
we have altcoins: 3.59064863
2017/05/18 04:51:33 Error: Missing boughtPrice
!!! Cycle 110 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:53:20--kraken--BTC_LTC  --  Gunbot v3.2 cycle #110 --------------- ]
::::: collecting market data...
++++
LP 0.013881  Bal.XXBT 0.94946381  Bal.XLTC 3.59064863
No open orders
boughtPrice undefined
price  falls (-8)
PriceToBuy 139.1769 priceToSell --not set--
we have altcoins: 3.59064863
2017/05/18 04:53:25 Error: Missing boughtPrice
!!! Cycle 111 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:55:13--kraken--BTC_LTC  --  Gunbot v3.2 cycle #111 --------------- ]
::::: collecting market data...
++++
LP 0.013929  Bal.XXBT 0.94946381  Bal.XLTC 3.59064863
No open orders
boughtPrice undefined
price  falls (-7)
PriceToBuy 139.1112 priceToSell --not set--
we have altcoins: 3.59064863
2017/05/18 04:55:17 Error: Missing boughtPrice
!!! Cycle 112 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:57:04--kraken--BTC_LTC  --  Gunbot v3.2 cycle #112 --------------- ]
::::: collecting market data...
++2017/05/18 04:57:09 Error: Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 113 failed. Will repeat in 107.52132489760052s
[ --2017/05/18 04:58:57--kraken--BTC_LTC  --  Gunbot v3.2 cycle #113 --------------- ]
::::: collecting market data...
++++
LP 0.013875  Bal.XXBT 0.94946381  Bal.XLTC 3.59064863
No open orders
boughtPrice undefined
price  falls (-7)
PriceToBuy 139.0541 priceToSell --not set--
we have altcoins: 3.59064863
2017/05/18 04:59:00 Error: Missing boughtPrice
!!! Cycle 114 failed. Will repeat in 107.52132489760052s

I've stopped gunbot and restarted but still, boughtPRice undefined and priceToSell not set.  Although, we know the price was 0.01393514.

Is it the nonce errors?  Did I do something wrong with the API?

20

Technical Support & Development / Re: Error: Kraken API returned error: API:Invalid nonce (Patch Fixes #2021 - v3.2 )

« on: May 18, 2017, 07:44:58 AM »

I just started my Kraken bot.  I'm running 11 pairs.  With a sleep delay of 30/35 (randomized), I hit an API rate limit after a while. ALo get a few invalid nonce. I raised the delay to 60/65 and stopped getting the API rate limit but get both the socket timed out and the invalid nonce.

Code: [Select]

++2017/05/18 01:41:42 Error: Kraken API returned error: API:Invalid nonce


Code: [Select]

[ --2017/05/18 01:39:25--kraken--BTC_DASH  --  Gunbot v3.2 cycle #4 --------------- ]
::::: collecting market data...
++2017/05/18 01:39:31 Error: Error in server response: {"code":"ESOCKETTIMEDOUT","connect":false}
!!! Cycle 5 failed. Will repeat in 77.5974041783731s


Code: [Select]


[ --2017/05/18 01:39:55--kraken--BTC_REP  --  Gunbot v3.2 cycle #4 --------------- ]
::::: collecting market data...
+++2017/05/18 01:40:01 Error: Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 5 failed. Will repeat in 83.44198344883314s
[ --2017/05/18 01:41:24--kraken--BTC_REP  --  Gunbot v3.2 cycle #5 --------------- ]
::::: collecting market data...
++++
LP 0.008461  Bal.XXBT 0.4995  Bal.XREP 0
No open orders
boughtPrice undefined
price  grows (1)
PriceToBuy 81.3345 priceToSell --not set--
LP 84.6100000 > prBuy 81.3345000  secMargin 0.000813345  grows yes
no altcoins: 0
price to buy: 0.00813345
last price is too high
Gunbot callback at 2017/05/18 01:41:29 cycle # 5
Callback:
---------
price too high
need faster: no
need slower: no

next delay will be 59.90952002802223s

[ --2017/05/18 01:42:28--kraken--BTC_REP  --  Gunbot v3.2 cycle #6 --------------- ]
::::: collecting market data...
+++2017/05/18 01:42:37 Error: Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 7 failed. Will repeat in 83.44198344883314s

And then here is a string of nonce, then working, then nonce, then rate limit exceeded

[code]
[ --2017/05/18 01:39:25--kraken--BTC_XLM  --  Gunbot v3.2 cycle #4 --------------- ]
::::: collecting market data...
++2017/05/18 01:39:30 Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 5 failed. Will repeat in 76.51786052340645s
[ --2017/05/18 01:40:47--kraken--BTC_XLM  --  Gunbot v3.2 cycle #5 --------------- ]
::::: collecting market data...
++++
LP 0.00002376  Bal.XXBT 0.4995  Bal.XXLM 0
No open orders
boughtPrice undefined
price  steady (0)
PriceToBuy 0.2339 priceToSell --not set--
LP 0.2376000 > prBuy 0.2339317  secMargin 0.0000023393166666666665  grows yes
no altcoins: 0
price to buy: 0.000023393166666666665
last price is too high
Gunbot callback at 2017/05/18 01:40:50 cycle # 5
Callback:
---------
price too high
need faster: no
need slower: no

next delay will be 48.752599041955065s


[ --2017/05/18 01:41:39--kraken--BTC_XLM  --  Gunbot v3.2 cycle #6 --------------- ]
::::: collecting market data...
++2017/05/18 01:41:42 Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 7 failed. Will repeat in 76.51786052340645s
[ --2017/05/18 01:42:59--kraken--BTC_XLM  --  Gunbot v3.2 cycle #7 --------------- ]
::::: collecting market data...
++2017/05/18 01:43:03 Error: Error: Kraken API returned error: API:Rate limit exceeded
!!! Cycle 8 failed. Will repeat in 76.51786052340645s
[ --2017/05/18 01:44:20--kraken--BTC_XLM  --  Gunbot v3.2 cycle #8 --------------- ]
::::: collecting market data...
++2017/05/18 01:44:25 Error: Kraken API returned error: API:Invalid nonce
!!! Cycle 9 failed. Will repeat in 76.51786052340645s


Looks like I need to increase my delays further.  On this one, I don't have the tier 3 validation yet.  My other kraken account has Tier 3 validation (higher API limits) but that account has balances in all the coins already, so it's not good for gunbot trading.
[/code]