Gunthy

GUNBOT: The automatic profit generator => Technical Support & Development => Topic started by: Gunthar on May 11, 2017, 11:01:31 PM

Title: Bugs/Issues tracker v3.2
Post by: Gunthar on May 11, 2017, 11:01:31 PM
This post is for your reports about bugs/issues to be fixed in the actual 3.2 version for all strategies. Please report any bug here, possibly with console screenshots or detailed description of the bug/issue. I will not answer here but i will answer with improved/fixed code: i'll use this post as a list of "to-do" things and reminder and i will tag [SOLVED] any fixed report of yours once i found the solution. I'll delete posts that are reporting "not reproducible" bugs, such as user's errors/misconfigurations and such: if you see your post deleted, please post it again in Beginners and Help, you will receive answers there.
Thanks!
~Gun

EDIT: please notice that this post is highly moderated to keep it cleaned up from off topics. This is a bug tracker, post your help/support requests on other boards or in PM.
Title: Re: Bugs/Issues tracker v3.2
Post by: beer-k0in on May 12, 2017, 10:41:16 AM
Priority ALLPAIRS-params.js vs poloniex-BTC_XXX-config.js changes after starting GUNBOT.

Tested: gunthy-linuxx64 - only with poloniex

ALLPAIRS-params.js:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 22
BOT_ON_FAIL_DELAY:(1000) * 55
...

poloniex-BTC_XXX-config.js:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 44
BOT_ON_FAIL_DELAY:(1000) * 55
...


>>> STARTING

When starting the bot (./gunthy-linuxx64 BTC_XXX poloniex) it prioritizes ALLPAIRS-params.js over poloniex-BTC_XXX-config.js.
Output:
Code: [Select]
next delay will be 22s

>>> RUNNING

Changing the ALLPAIRS-params.js while the bot is running will have no effect. Looks like the file is not watched.
But changing poloniex-BTC_XXX-config.js while the bot is running, triggers the reconfiguration and now it prioritizes poloniex-BTC_XXX-config.js over ALLPAIRS-params.js.

Changing poloniex-BTC_XXX-config.js to:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 44
BOT_ON_FAIL_DELAY:(1000) * 99 // <-- changed
...

Output:
Code: [Select]
next delay will be 44s
Suggestions:
- Watch both configs (ALLPAIRS-params.js and market-BTC_XXX-config.js) for changes.
- In any case (starting and running) prioritize the specific config (market-BTC_XXX-config.js) over the general config (ALLPAIRS-params.js).
Title: Re: Bugs/Issues tracker v3.2
Post by: dobcrypto on May 12, 2017, 02:34:08 PM
Double buy on
Code: [Select]
BUY_STRATEGY: "BB",
SELL_STRATEGY: "GAIN",
BTC_TRADING_LIMIT: 0.01

(http://image.prntscr.com/image/7dc53e8cd6254443a05d99c97fe8bc3a.png)

Title: Market Buy/Sell Orders lead to losses
Post by: IvanStoycho on May 12, 2017, 05:47:34 PM
When the time to buy has come, gunbot puts market order to buy to a price that is in reality incorrect.

Settings:
gunbot v3.2, buy strategy: BB, 25%; sell strategy: GAIN 3% 5%, bot delay time: 60s

Description:
Having lower 'bought price' leads to inappropriate calculations of the GAIN % (sell strategy is GAIN). Afterwards, because sell orders are also market the result is unpredictable and at least in my case all trades lead to losses.
Title: Re: Market Buy/Sell Orders lead to losses
Post by: Gunthar on May 12, 2017, 05:57:38 PM
When the time to buy has come, gunbot puts market order to buy to a price that is in reality incorrect.

Settings:
gunbot v3.2, buy strategy: BB, 25%; sell strategy: GAIN 3% 5%, bot delay time: 60s

Description:
Having lower 'bought price' leads to inappropriate calculations of the GAIN % (sell strategy is GAIN). Afterwards, because sell orders are also market the result is unpredictable and at least in my case all trades lead to losses.

The problem is fixed in patch 2019: moved to limit. Apparently the issue is that we dont get "market" price from their api, we get "average" price. Reference: https://support.kraken.com/hc/en-us/articles/203325783-Market-and-Limit-Orders
Title: GUnbot or Kraken issue
Post by: IvanStoycho on May 12, 2017, 06:12:48 PM
UPDATE :  Issue not reproducible anymore after patch 2019 is applied. Thanks!


I don't even know how to summarize this  - crazy things are happening

Description:
Gunbot is placing market orders and Kraken says they are cancelled (for some reason), but at the end Gunbot is selling less amount that it purchased and Kraken accepts. But because those are market orders.... this game is not funny for me.
Please check attached log files and screenshots.

Additional details:
I used an old -save.json file in order to reuse the BB calculation, and had some leftover amounts I did not see in Kraken (0.00000036). i bought some volume to reach 16 ICNs. Gunbot spit an error for unknown bought price, so I immediately sold the 16 ICN.
Title: Other pairs on hold while one pair has a pending (untouched) order
Post by: IvanStoycho on May 12, 2017, 06:30:10 PM
When one Pair places an order that is not yet executed, all the rest of the pairs pretend to have the same order for their currency.
This holds all the other pairs to proceed normally

Settings:
Gunbot v3.2, win headless, Buy strategy: BB, 25%; sell strategy: GAIN 3%, bot delay: 60s

Details:
Gunbot placed a buy order for LTC that was processed with a delay of some minutes by Kraken.
Meanwhile, all the rest of the pairs that were about to proceeed with a buy/sell had the same message:
2017/05/12 00:40:10   Waiting for orders: 370.248 XLTC    , for LTC
2017/05/12 00:26:33   Waiting for orders: 370.248 XXLM   , for XLM
2017/05/12 00:26:07   Waiting for orders: 370.248 XETC   , for ETC

etc. etc.

Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 12, 2017, 06:40:15 PM
~snip
~snip

Please apply patch #1029_ i moved kraken to limit market
Title: Re: Bugs/Issues tracker v3.2
Post by: IvanStoycho on May 12, 2017, 07:18:19 PM


Please apply patch #1029_ i moved kraken to limit market
[/quote]

Great, thanks! Just restarting with the patch
Title: Process out of memory
Post by: strshtr on May 12, 2017, 09:16:23 PM
Across all 3 exchanges using v3.2 on linux mint64 vm gunthy-linuxx64 I'm periodically seeing the following error



Process out of memory. I have to restart the pair to get it working again.

Title: Re: Bugs/Issues tracker v3.2
Post by: zardos on May 13, 2017, 12:16:01 AM
Priority ALLPAIRS-params.js vs poloniex-BTC_XXX-config.js changes after starting GUNBOT.

Tested: gunthy-linuxx64 - only with poloniex

ALLPAIRS-params.js:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 22
BOT_ON_FAIL_DELAY:(1000) * 55
...

poloniex-BTC_XXX-config.js:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 44
BOT_ON_FAIL_DELAY:(1000) * 55
...


>>> STARTING

When starting the bot (./gunthy-linuxx64 BTC_XXX poloniex) it prioritizes ALLPAIRS-params.js over poloniex-BTC_XXX-config.js.
Output:
Code: [Select]
next delay will be 22s

>>> RUNNING

Changing the ALLPAIRS-params.js while the bot is running will have no effect. Looks like the file is not watched.
But changing poloniex-BTC_XXX-config.js while the bot is running, triggers the reconfiguration and now it prioritizes poloniex-BTC_XXX-config.js over ALLPAIRS-params.js.

Changing poloniex-BTC_XXX-config.js to:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 44
BOT_ON_FAIL_DELAY:(1000) * 99 // <-- changed
...

Output:
Code: [Select]
next delay will be 44s
Suggestions:
- Watch both configs (ALLPAIRS-params.js and market-BTC_XXX-config.js) for changes.
- In any case (starting and running) prioritize the specific config (market-BTC_XXX-config.js) over the general config (ALLPAIRS-params.js).
I think this is what I am talking about too... here's what I wrote in Telegram & Gun asked me to post here:

1) set refresh time to 20 secs in Allpairs
2) set refresh time to 120 in Dash pair
3) start bot — it will use the 20 sec time
4) make a change and resave the Dash pair
5) Bot will reconfigure and use the 120 time
6) stop the bot and restart the bot — it will switch to the 20 sec time from AllPairs again

The problem here is, it breaks the reconfig totally.   I suggest it always use the AllPairs as the override regardless of which is saved last.        Of course, I also am an advocate of switching this, to make the coin's config the override, and All Pairs just a default (opposite of the way it works now)... but that's another issue for down the road.   I think the "quick fix" is to do what I said in second sentence.

PS - I always feel bad reporting/suggesting...     I wanted to compliment Gunthar on an awesome job on the bot!  Really good work!
Title: Re: Process out of memory
Post by: Beachguy on May 13, 2017, 11:57:05 AM
Across all 3 exchanges using v3.2 on linux mint64 vm gunthy-linuxx64 I'm periodically seeing the following error

Process out of memory. I have to restart the pair to get it working again.

This first appeared for me back in v2.03 when polo was so laggy. It's not the bot it's polo.
Just close and restart the pair.
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 13, 2017, 01:24:24 PM
2 issues to report:

1) "Altcoin on orders" is reported incorrectly in kraken market (did not check other markets):

Situation: I have some ETH that I manually placed a selling order for. Now I started a different pair in kraken from scratch with brand new config and no save file. The ETH on orders is now reported as "balance on order" for the newly started pair and the bot is confused because it thinks we have altcoins but no boughtPrice. This could be mitigated if the "balance on order" is reported correctly for the pair the bot is running.

2) I cannot find the Low BB and High BB values in the "-save.json" file.

Saving these important values would make it easy to write a GUI that reports them over time. I am thinking along the lines of an InfluxDB database with Grafana dashboard tracking all parameters. Would be really nice to tweak the bot.

Thanks Gunthar for an awesome update!
Title: Re: Process out of memory
Post by: strshtr on May 13, 2017, 07:29:00 PM
Across all 3 exchanges using v3.2 on linux mint64 vm gunthy-linuxx64 I'm periodically seeing the following error

Process out of memory. I have to restart the pair to get it working again.

This first appeared for me back in v2.03 when polo was so laggy. It's not the bot it's polo.
Just close and restart the pair.

This resolved the issue temporarily but it keeps coming up on different pairs and exchanges (not just poloniex) runnings 3.2. I'm also running v2.04 and it doesn't appear to be affected.
Title: Re: Market Buy/Sell Orders lead to losses
Post by: IvanStoycho on May 14, 2017, 06:56:44 AM

The problem is fixed in patch 2019: moved to limit. Apparently the issue is that we dont get "market" price from their api, we get "average" price. Reference: https://support.kraken.com/hc/en-us/articles/203325783-Market-and-Limit-Orders

I confirm problem solved with patch 2019
Title: Re: Bugs/Issues tracker v3.2
Post by: nixxda on May 14, 2017, 08:35:31 AM
Tripple an quadruple buys on Patch 2019!

"BB" strategy, poloniex!

All pairs are set to "BTC_TRADING_LIMIT: 0.035"

(http://i.imgur.com/Q3hM6O9.jpg)
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 14, 2017, 08:00:13 PM
2 issues to report:

1) "Altcoin on orders" is reported incorrectly in kraken market (did not check other markets):

Situation: I have some ETH that I manually placed a selling order for. Now I started a different pair in kraken from scratch with brand new config and no save file. The ETH on orders is now reported as "balance on order" for the newly started pair and the bot is confused because it thinks we have altcoins but no boughtPrice. This could be mitigated if the "balance on order" is reported correctly for the pair the bot is running.

2) I cannot find the Low BB and High BB values in the "-save.json" file.

Saving these important values would make it easy to write a GUI that reports them over time. I am thinking along the lines of an InfluxDB database with Grafana dashboard tracking all parameters. Would be really nice to tweak the bot.

Thanks Gunthar for an awesome update!

Solved both in patch 2020
Thanks for reporting!
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 14, 2017, 08:01:14 PM
Tripple an quadruple buys on Patch 2019!

"BB" strategy, poloniex!

All pairs are set to "BTC_TRADING_LIMIT: 0.035"


statuscode 502, 429, 422 from poloniex caused this. Please apply patch 2020 to mitigate about 99% of these issues.
Title: Re: Other pairs on hold while one pair has a pending (untouched) order
Post by: Gunthar on May 14, 2017, 08:02:34 PM
When one Pair places an order that is not yet executed, all the rest of the pairs pretend to have the same order for their currency.
This holds all the other pairs to proceed normally

Settings:
Gunbot v3.2, win headless, Buy strategy: BB, 25%; sell strategy: GAIN 3%, bot delay: 60s

Details:
Gunbot placed a buy order for LTC that was processed with a delay of some minutes by Kraken.
Meanwhile, all the rest of the pairs that were about to proceeed with a buy/sell had the same message:
2017/05/12 00:40:10   Waiting for orders: 370.248 XLTC    , for LTC
2017/05/12 00:26:33   Waiting for orders: 370.248 XXLM   , for XLM
2017/05/12 00:26:07   Waiting for orders: 370.248 XETC   , for ETC

etc. etc.
fixed in patch 2020
Thanks for reporting!
Title: Re: Bugs/Issues tracker v3.2
Post by: ARosie on May 14, 2017, 09:19:06 PM
This might have been fixed in 2020 patch (I just updated so not sure yet), but I've noticed the bot leaves older BUY orders hanging, even after the price has increased significantly and it was since purchased the same coin at a higher price. This makes less BTC available for other buy orders.
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 14, 2017, 10:38:01 PM
2 issues to report:

1) "Altcoin on orders" is reported incorrectly in kraken market (did not check other markets):

Situation: I have some ETH that I manually placed a selling order for. Now I started a different pair in kraken from scratch with brand new config and no save file. The ETH on orders is now reported as "balance on order" for the newly started pair and the bot is confused because it thinks we have altcoins but no boughtPrice. This could be mitigated if the "balance on order" is reported correctly for the pair the bot is running.

2) I cannot find the Low BB and High BB values in the "-save.json" file.

Saving these important values would make it easy to write a GUI that reports them over time. I am thinking along the lines of an InfluxDB database with Grafana dashboard tracking all parameters. Would be really nice to tweak the bot.

Thanks Gunthar for an awesome update!

Solved both in patch 2020
Thanks for reporting!

Thanks for including the BB values, this will be really helpful! I was wondering if you can also include the mean value, I think I can calculate this from the latestPrices array but it would just be nice to show lowBB, highBB and mean.

Regarding the "onOrder" issue:
Unfortunately the issue persists, the ETH now shows as alt balance although it still is on selling order ("On Orders" is not shown anymore). gbot complains about "Missing boughtPrice" since it cannot find a record of this altcoin balance. I think in this situation the altcoin balance should be reported as zero and not as the alt coin balance which is on selling order.

Nasty problem, but thanks for taking care of the bugs!
Title: Kraken Insufficient funds error
Post by: strshtr on May 15, 2017, 07:16:12 AM
Linux mint
Getting insufficient funds error in kraken for MLN pair when the bot is trying to sell.
(https://i.gyazo.com/0d671c3336311460a57059b9684cc767.png)
Title: Re: Bugs/Issues tracker v3.2
Post by: nixxda on May 15, 2017, 11:26:26 AM
I still get quadruple buys on "patch 2020"!

poloniex-BTC_LBC-trades.txt

2017/05/15 11:57:06 *** MARKET CALLBACK | buy 376.9525732364028 LBC for 0.00009285 BTC
2017/05/15 11:57:52 *** MARKET CALLBACK | buy 376.9525732364028 LBC for 0.00009285 BTC
2017/05/15 11:58:09 *** MARKET CALLBACK | buy 376.9525732364028 LBC for 0.00009285 BTC
2017/05/15 11:58:27 *** MARKET CALLBACK | buy 376.5875454056381 LBC for 0.00009294 BTC
Title: Re: Bugs/Issues tracker v3.2
Post by: beer-k0in on May 15, 2017, 12:58:17 PM
I still get quadruple buys on "patch 2020"!

Same here, except it's triple buys:

poloniex-BTC_MAID-trades.txt

2017/05/15 02:34:16 *** MARKET CALLBACK | buy 216.2167162162162 MAID for 0.000185 BTC
2017/05/15 02:38:34 *** MARKET CALLBACK | buy 216.20502948489272 MAID for 0.00018501 BTC
2017/05/15 02:40:17 *** MARKET CALLBACK | buy 216.08823161903732 MAID for 0.00018511 BTC
Title: Re: Bugs/Issues tracker v3.2
Post by: nixxda on May 15, 2017, 04:45:37 PM
another one:

"BB" Strategy on Linux (only one tested) will suddenly fail and loose its "PriceToBuy" and stay this way!

Code: [Select]
2017/05/15 11:58:55 Open buy orders: ,0
2017/05/15 11:58:55
2017/05/15 11:59:10 [ --2017/05/15 11:59:10--poloniex--BTC_STR  --  Gunbot v3.2 cycle #341 --------------- ]
2017/05/15 11:59:10 ::::: collecting market data...
2017/05/15 11:59:10 ***************************************************
2017/05/15 11:59:10 Low BB:0.00002226 - High BB:0.00002296
2017/05/15 11:59:10 ***************************************************
2017/05/15 11:59:12 LP 0.0000225  Bal.BTC 0.20009402  Bal.STR 0(0)
2017/05/15 11:59:12 No open orders
2017/05/15 11:59:12 boughtPrice 0.0000222
2017/05/15 11:59:12 price  falls (-2)
2017/05/15 11:59:12 PriceToBuy,0.2193,priceToSell,0.2242
2017/05/15 11:59:12 LP 0.2250000,>,prBuy 0.2192976  secMargin 0.000008771903999999996  grows yes
2017/05/15 11:59:12 no altcoins: 0
2017/05/15 11:59:12 price to buy: 0.00002192975999999999
2017/05/15 11:59:12 last price is too high
2017/05/15 11:59:12 Gunbot callback at 2017/05/15 11:59:12 cycle # 341
2017/05/15 11:59:12 Callback:
2017/05/15 11:59:12 ---------
2017/05/15 11:59:12 price too high
need faster: no
need slower: no

2017/05/15 11:59:12 next delay will be 15s


2017/05/15 11:59:27 [ --2017/05/15 11:59:27--poloniex--BTC_STR  --  Gunbot v3.2 cycle #342 --------------- ]
2017/05/15 11:59:27 ::::: collecting market data...
2017/05/15 11:59:27 ***************************************************
2017/05/15 11:59:27 Low BB:0.00002226 - High BB:0.00002296
2017/05/15 11:59:27 ***************************************************
2017/05/15 11:59:29 LP 0.0000225  Bal.BTC 0.20009402  Bal.STR 0(0)
2017/05/15 11:59:29 No open orders
2017/05/15 11:59:29 boughtPrice 0.0000222
2017/05/15 11:59:29 price  falls (-2)
2017/05/15 11:59:29 PriceToBuy,0.0000,priceToSell,0.2242
2017/05/15 11:59:29 LP 0.2250000,>,prBuy 0.0000000  secMargin 0  grows yes
2017/05/15 11:59:29 no altcoins: 0
2017/05/15 11:59:29 price to buy: 0
2017/05/15 11:59:29 last price is too high
2017/05/15 11:59:29 Gunbot callback at 2017/05/15 11:59:29 cycle # 342
2017/05/15 11:59:29 Callback:
2017/05/15 11:59:29 ---------
2017/05/15 11:59:29 price too high
need faster: no
need slower: no
(yaehh! found the code button!-)

the same in XMR. this time after a sale:
Code: [Select]
017/05/15 11:24:10 [ --2017/05/15 11:24:10--poloniex--BTC_XMR  --  Gunbot v3.2 cycle #724 --------------- ]
2017/05/15 11:24:10 ::::: collecting market data...
2017/05/15 11:24:11 ***************************************************
2017/05/15 11:24:11 Low BB:0.01572059 - High BB:0.01613443
2017/05/15 11:24:11 ***************************************************
2017/05/15 11:24:12 LP 0.01621756  Bal.BTC 0.12437192  Bal.XMR 13.32393662(0)
2017/05/15 11:24:12 No open orders
2017/05/15 11:24:12 boughtPrice 0.01574101
2017/05/15 11:24:12 price  grows (11)
2017/05/15 11:24:12 PriceToBuy,0.0000,priceToSell,162.1324
2017/05/15 11:24:12 we have altcoins: 13.32393662
2017/05/15 11:24:12 LP 162.1756,>=,prSell 162.132403  secMargin 0  falls yes
2017/05/15 11:24:12 price to sell: ,0.0162132403
2017/05/15 11:24:12 price is sweet
2017/05/15 11:24:12 price fall -> sell
2017/05/15 11:24:13 [object Object]
2017/05/15 11:24:13 [object Object]
2017/05/15 11:24:13
2017/05/15 11:24:13 *** MARKET CALLBACK | sell 13.32393662 XMR for 0.01621756 BTC
2017/05/15 11:24:13 Profit 0.006349521996260989
2017/05/15 11:24:13 Gunbot callback at 2017/05/15 11:24:13 cycle # 724
2017/05/15 11:24:13 Callback:
2017/05/15 11:24:13 ---------
2017/05/15 11:24:13 sell 13.32393662 XMR for 0.01621756 BTC
need faster: no
need slower: no

2017/05/15 11:24:13 next delay will be 30s


2017/05/15 11:24:43 [ --2017/05/15 11:24:43--poloniex--BTC_XMR  --  Gunbot v3.2 cycle #725 --------------- ]
2017/05/15 11:24:43 ::::: collecting market data...
2017/05/15 11:24:43 ***************************************************
2017/05/15 11:24:43 Low BB:0.01571932 - High BB:0.01613815
2017/05/15 11:24:43 ***************************************************
2017/05/15 11:24:45 LP 0.01621756  Bal.BTC 0.34009418  Bal.XMR 0(0)
2017/05/15 11:24:45 No open orders
2017/05/15 11:24:45 boughtPrice 0.01574101
2017/05/15 11:24:45 price  grows (11)
2017/05/15 11:24:45 PriceToBuy,0.0000,priceToSell,162.1324
2017/05/15 11:24:45 LP 162.1756000,>,prBuy 0.0000000  secMargin 0  grows no
2017/05/15 11:24:45 no altcoins: 0
2017/05/15 11:24:45 price to buy: 0
2017/05/15 11:24:45 last price is too high
2017/05/15 11:24:45 Gunbot callback at 2017/05/15 11:24:45 cycle # 725
2017/05/15 11:24:45 Callback:
2017/05/15 11:24:45 ---------
2017/05/15 11:24:45 price too high
need faster: no
need slower: no

2017/05/15 11:24:45 next delay will be 30s


2017/05/15 11:25:15 [ --2017/05/15 11:25:15--poloniex--BTC_XMR  --  Gunbot v3.2 cycle #726 --------------- ]
2017/05/15 11:25:15 ::::: collecting market data...
2017/05/15 11:25:16 ***************************************************
2017/05/15 11:25:16 Low BB:0.01571807 - High BB:0.01614182
2017/05/15 11:25:16 ***************************************************
2017/05/15 11:25:17 LP 0.01618  Bal.BTC 0.34009418  Bal.XMR 0(0)
2017/05/15 11:25:17 No open orders
2017/05/15 11:25:17 boughtPrice 0.01574101
2017/05/15 11:25:17 price  grows (11)
2017/05/15 11:25:17 PriceToBuy,0.0000,priceToSell,162.1324
2017/05/15 11:25:17 LP 161.8000000,>,prBuy 0.0000000  secMargin 0  grows yes
2017/05/15 11:25:17 no altcoins: 0
2017/05/15 11:25:17 price to buy: 0
2017/05/15 11:25:17 last price is too high
2017/05/15 11:25:17 Gunbot callback at 2017/05/15 11:25:17 cycle # 726
2017/05/15 11:25:17 Callback:
2017/05/15 11:25:17 ---------
2017/05/15 11:25:17 price too high
need faster: no
need slower: no

and btw. Thanks for the Timestamps in the logs!-)
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 15, 2017, 05:26:39 PM
~snip
aknowledged and fixed in a patch #2021 i'm pushing in a few.
Thanks for reporting this!
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 15, 2017, 09:21:05 PM
~snip

this isnt from 3.2
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 15, 2017, 09:24:29 PM
gbot complains about "Missing boughtPrice" since it cannot find a record of this altcoin balance.

MissingBoughtPrice comes because you didnt port the save.json file: basically wasnt the bot to place that sell order.
Please do not use manual orders, they are nto implemented nor they help.
Title: Re: Bugs/Issues tracker v3.2
Post by: chimj on May 15, 2017, 09:41:54 PM

I understand manual trades don't work, but I have 0 balance BTC when I log into kraken, yet GB thinks I have a tiny amount of BTC (6e-9). I bought 0.001 BTC added boughtprice to json, GB sold but then came back with the same error.

 

this is 3.2 with patch 2021 applied (had debug on).

root@vmi116019:~/gb32# file gunthy-linuxx64
gunthy-linuxx64: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=bfc575652f6dcc5ba1920e786c4102954056a46f, not stripped
chim@vmi116019:~/gb32#
chim@vmi116019:~/gb32#
chim@vmi116019:~/gb32#
chim@vmi116019:~/gb32#
chim@vmi116019:~/gb32# ./gunthy-linuxx64 EUR_BTC kraken
Loading config...
Loading config...
Creating market client for EUR_BTC pair
Activating hot reconfig...
[ --2017/05/15 22:38:42--kraken--EUR_BTC  --  Gunbot v3.2 cycle #1 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00000000 - High BB:0.00000000
***************************************************
++++
LP 1583.795  Bal.ZEUR 420.7453  Bal.XXBT 6e-9
No open orders
boughtPrice undefined
price  steady (0)
PriceToBuy 0.0000 priceToSell --not set--
we have altcoins: 6e-9
2017/05/15 22:38:45 Error: Missing boughtPrice
Error: Missing boughtPrice
!!! Cycle 2 failed. Will repeat in 60s
^C
chim@vmi116019:~/gb32#


Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 15, 2017, 10:05:30 PM

~snip

You "think" the bot doesnt: 6e-9 are 0.000000006 BTC on your balance at Kraken which are 0.00000 BTC displayed on kraken balances (roundings is worse than polo at kraken: 5 digits only)
Title: Re: Bugs/Issues tracker v3.2
Post by: Dest on May 16, 2017, 07:21:45 AM
Hi.
In 3.2 with patch 2020
9 pairs were started
On all pairs security margin disappears.
After rebooting the pair all ok

(http://art-sign.ru/images/16-05.jpg)
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 16, 2017, 08:39:47 AM
~snip

patch 2021 fixed this
Title: Re: Bugs/Issues tracker v3.2
Post by: Doesnt Matter on May 16, 2017, 06:35:56 PM
Gun,
Some days ago you changed SECURITY_MARGIN that way that it is working like a real stop-loss at a certain percentage of the bought price. I think this is exactly what people expect when they set this parameter.

But you changed it only for BB, not for the other strategies. When you provided the 'fix' (it isn't, I understand that you had another intention with the original way it was programmed) it was only the BB.js.

Do you mind to change it for every strategy? Otherwise the bot is not acting predictable for people who don't know that the same parameter does work different across the different strategies...

Thanks!
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 17, 2017, 08:13:47 AM
Hi Gun,

thanks again for ironing out all the bugs and patiently explaining things! Would it be possible to change v3.2 so that lastestPrices are reloaded when we restart the bot? I think you added this to v3.1 at some point and it was really useful for setting up the BB. I hate it when the bot needs to recalculate stats for hours. I understand that this might be dangerous when the bot was switched off for some time because the values are too old and not accurate anymore. Could this be an optional setting in the config? Something like "LOAD_LATEST_PRICES_ON_START: false" as default but so that we can change it if we are aware of the associated risks? That would be awesome!

Thanks again!
Title: Re: Bugs/Issues tracker v3.2
Post by: nixxda on May 17, 2017, 05:55:34 PM
@OutOfSync to me it looks like 3.2 BB needs 3 cycles to calculate its values!? but I might be wrong and the values showing up are ...?.. something else!

@Gunthar "Patch 2022" seems to have fixed my spastic quadruple buy order problem! ;) and all my to-big positions sold already with a profit!  ;D
and on the certain eventuality that I haven't said so already, Thanks  for cleaning up all the config files in 3.2! Its really nice to work with now :-* 
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 17, 2017, 09:16:19 PM
@OutOfSync to me it looks like 3.2 BB needs 3 cycles to calculate its values!? but I might be wrong and the values showing up are ...?.. something else!

It shows BB values after 3 cycles because you need at least 3 values to calculate standard deviation. However, until stats are calculated (300 cycles with default settings) the bot does not use BB strategy but the GAIN value (2% as default). 300 cycles with default delay of 120 s is 10 hours untils BB stats are done. This is just quite long if you have to e.g. update the binary and hotconfig is therefore not possible...
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 17, 2017, 09:29:15 PM
@OutOfSync to me it looks like 3.2 BB needs 3 cycles to calculate its values!? but I might be wrong and the values showing up are ...?.. something else!

It shows BB values after 3 cycles because you need at least 3 values to calculate standard deviation. However, until stats are calculated (300 cycles with default settings) the bot does not use BB strategy but the GAIN value (2% as default). 300 cycles with default delay of 120 s is 10 hours untils BB stats are done. This is just quite long if you have to e.g. update the binary and hotconfig is therefore not possible...

A trick if you know you are going to do a quick restart: save your save.json file in another folder > start yor bot > copy/paste yoru old save.json file while the bot is already running. Dont do that if you stop yrou bot for long time tho: you will get weird standard deviation
Title: Re: Bugs/Issues tracker v3.2
Post by: liquid on May 18, 2017, 05:20:41 AM
v3.2 Patch 2022 on Linux
Sell price is NaN because some calculation failed. This can be prevented by checking lodash: https://lodash.com/docs/4.17.4#isNaN
Buy BB 35 Sell Stepgain
(http://i.imgur.com/Egim7Gd.png)
Title: Re: Bugs/Issues tracker v3.2
Post by: cw 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?


Title: Re: Bugs/Issues tracker v3.2
Post by: cw 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.

Title: Re: Bugs/Issues tracker v3.2
Post by: cw 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.
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 18, 2017, 03:03:48 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.

Yes, since the last weeks mitigation of ddos attacks on multiple exchanges i added (err, data) to the err. I'll move that to err logs: i needed to see wtf was going on...
Title: Re: Bugs/Issues tracker v3.2
Post by: rsalan on May 18, 2017, 03:18:27 PM
This might have been fixed in 2020 patch (I just updated so not sure yet), but I've noticed the bot leaves older BUY orders hanging, even after the price has increased significantly and it was since purchased the same coin at a higher price. This makes less BTC available for other buy orders.

+1 on Polo
Title: Re: Bugs/Issues tracker v3.2
Post by: cw 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:

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:
(http://i.imgur.com/V1XWxrq.jpg)

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

(http://i.imgur.com/F1HMgs6.jpg)
Title: Re: Bugs/Issues tracker v3.2
Post by: cw 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.

(http://i.imgur.com/SVM3jaA.jpg)

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.
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 20, 2017, 10:06:10 AM
@OutOfSync to me it looks like 3.2 BB needs 3 cycles to calculate its values!? but I might be wrong and the values showing up are ...?.. something else!

It shows BB values after 3 cycles because you need at least 3 values to calculate standard deviation. However, until stats are calculated (300 cycles with default settings) the bot does not use BB strategy but the GAIN value (2% as default). 300 cycles with default delay of 120 s is 10 hours untils BB stats are done. This is just quite long if you have to e.g. update the binary and hotconfig is therefore not possible...

A trick if you know you are going to do a quick restart: save your save.json file in another folder > start yor bot > copy/paste yoru old save.json file while the bot is already running. Dont do that if you stop yrou bot for long time tho: you will get weird standard deviation

Thanks for the suggestion, I tried it but it doesn't seem to work. Seems like the bot saves the current status before loading the -save.json file. I always end up with the empty lastPrices array in the save file. Also no luck with setting readonly permission to prevent saving the current (empty) array over the previous fully filled one.
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 20, 2017, 12:17:23 PM
Another observation:

I have been running lots of pairs with TRADING_VOLUME 0 at lower cycle time to have full BB stats. Then when I decide the pair should be active I just set it to 0.02 BTC for trading. This way I thought I can avoid having to wait for 10h to have complete BB stats. Since TRADING_VOLUME is zero no buy/sell action should happen. Then I noticed that the bots gets into limbo after a 0 BTC buy happens (which results in an error message). The bot is "waiting for orders 0 DGB" indefinetely although no altcoin balance/on orders. I attached the corresponding part of the log below. I will now run the TRADING_VOLUME with higher BTC (perhaps 0.001 BTC) instead. However, this could probably be fixed - if you have any hints what in the savefile I have to look for I would be grateful. This is running 3.2_core (22 update, not the GUI one). It was cycle 81, so stats were not completed yet and GAIN was used.

Code: [Select]
2017/05/18 10:58:35 [ --2017/05/18 10:58:35--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #81 --------------- ]
2017/05/18 10:58:35 ::::: collecting market data...
2017/05/18 10:58:35 ***************************************************
2017/05/18 10:58:35 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 10:58:35 ***************************************************
2017/05/18 10:58:38 LP 0.0000034  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 10:58:38 No open orders
2017/05/18 10:58:38 boughtPrice undefined
2017/05/18 10:58:38 price  grows (2)
2017/05/18 10:58:38 PriceToBuy,0.0338,priceToSell,--not set--
2017/05/18 10:58:38 LP 0.0340000,>,prBuy 0.0337905  secMargin 0.0000013516219178082197  grows yes
2017/05/18 10:58:38 no altcoins: 0
2017/05/18 10:58:38 price to buy: 0.000003379054794520549
2017/05/18 10:58:38 last price is too high
2017/05/18 10:58:38 Gunbot callback at 2017/05/18 10:58:38 cycle # 81
2017/05/18 10:58:38 Callback:
2017/05/18 10:58:38 ---------
2017/05/18 10:58:38 price too high
need faster: yes
need slower: no

2017/05/18 10:58:38 next delay will be 60s


2017/05/18 10:59:38 [ --2017/05/18 10:59:38--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #82 --------------- ]
2017/05/18 10:59:38 ::::: collecting market data...
2017/05/18 10:59:38 ***************************************************
2017/05/18 10:59:38 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 10:59:38 ***************************************************
2017/05/18 10:59:40 LP 0.00000335  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 10:59:40 No open orders
2017/05/18 10:59:40 boughtPrice undefined
2017/05/18 10:59:40 price  steady (0)
2017/05/18 10:59:40 PriceToBuy,0.0338,priceToSell,--not set--
2017/05/18 10:59:40 LP 0.0335000,<=,prBuy 0.0337796  secMargin 0.0000013511837837837842  grows yes
2017/05/18 10:59:40 no altcoins: 0
2017/05/18 10:59:40 price to buy: 0.00000337795945945946
2017/05/18 10:59:40 price is sweet to buy
2017/05/18 10:59:40 price is growing
2017/05/18 10:59:40 Buying on poloniex 0.0005 of DGB for 0.00000335
2017/05/18 10:59:40 2017/05/18 10:59:40 Error: Amount (0.0005) too low. Increase BTC_TRADING_LIMIT
2017/05/18 10:59:40 !!! Cycle 83 failed. Will repeat in 61s
2017/05/18 11:00:41 [ --2017/05/18 11:00:41--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #83 --------------- ]
2017/05/18 11:00:41 ::::: collecting market data...
2017/05/18 11:00:41 ***************************************************
2017/05/18 11:00:41 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 11:00:41 ***************************************************
2017/05/18 11:00:43 LP 0.00000336  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 11:00:43 No open orders
2017/05/18 11:00:43 boughtPrice undefined
2017/05/18 11:00:43 price  grows (1)
2017/05/18 11:00:43 PriceToBuy,0.0338,priceToSell,--not set--
2017/05/18 11:00:43 Gunbot callback at 2017/05/18 11:00:43 cycle # 83
2017/05/18 11:00:43 Callback:
2017/05/18 11:00:43 ---------
2017/05/18 11:00:43 Waiting for orders: 0 DGB
need faster: yes
need slower: no

2017/05/18 11:00:43 next delay will be 60s


2017/05/18 11:01:43 [ --2017/05/18 11:01:43--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #84 --------------- ]
2017/05/18 11:01:43 ::::: collecting market data...
2017/05/18 11:01:44 ***************************************************
2017/05/18 11:01:44 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 11:01:44 ***************************************************
2017/05/18 11:01:45 LP 0.00000339  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 11:01:45 No open orders
2017/05/18 11:01:45 boughtPrice undefined
2017/05/18 11:01:45 price  grows (1)
2017/05/18 11:01:45 PriceToBuy,0.0337,priceToSell,--not set--
2017/05/18 11:01:45 Gunbot callback at 2017/05/18 11:01:45 cycle # 84
2017/05/18 11:01:45 Callback:
2017/05/18 11:01:45 ---------
2017/05/18 11:01:45 Waiting for orders: 0 DGB
need faster: yes
need slower: no

2017/05/18 11:01:45 next delay will be 60s


2017/05/18 11:02:45 [ --2017/05/18 11:02:45--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #85 --------------- ]
2017/05/18 11:02:45 ::::: collecting market data...
2017/05/18 11:02:46 ***************************************************
2017/05/18 11:02:46 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 11:02:46 ***************************************************
2017/05/18 11:02:48 LP 0.0000034  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 11:02:48 No open orders
2017/05/18 11:02:48 boughtPrice undefined
2017/05/18 11:02:48 price  grows (1)
2017/05/18 11:02:48 PriceToBuy,0.0337,priceToSell,--not set--
2017/05/18 11:02:48 Gunbot callback at 2017/05/18 11:02:48 cycle # 85
2017/05/18 11:02:48 Callback:
2017/05/18 11:02:48 ---------
2017/05/18 11:02:48 Waiting for orders: 0 DGB
need faster: yes
need slower: no

2017/05/18 11:02:48 next delay will be 60s
Title: Re: Bugs/Issues tracker v3.2
Post by: opedroadami on May 20, 2017, 12:20:07 PM
I am having some troubles with the 3.2GUI.

It all started normal, but the circles in RED don't update (shouldn't the CALLBACK be updated every bot cycle?) and the prices in YELLOW don't change (even after a while).

(https://preview.ibb.co/cZkekv/3_2gui.png) (https://ibb.co/hoNQQv)

Also, having problems with 522 error. In the 3.2GUI it freezes the bot, so I have to start over.

Then, I tried using the 3.1GUI until this is solved. But unfortunately I am also having 522 problems with it:

Quote
Loading config...
2017/05/20 11:06:05 Creating market client for BTC_DASH pair
Activating hot reconfig...
[ ---- poloniex -- 2017/05/20 11:06:05  --  Gunbot v3.1b cycle #1 -------------------------- ]
Loaded  poloniex-BTC_DASH-save.json
::::: collecting market data...
+2017/05/20 11:06:36 Error: statusCode 522
!!! Cycle 2 failed. Will repeat in 10s

But there the bot keeps on repeating the process until 522 is gone and it can cycle normally again.

The new GUI is really better in comparison with the old one, but those bugs kinda spoil the experience.
Title: Re: Bugs/Issues tracker v3.2
Post by: majorlee on May 20, 2017, 12:27:51 PM
having issues connecting

installed node.js

when i try to load a pair i always get this and white blank screen....

 Navigation to the webpage was canceled
   
   What you can try:
     Refresh the page.
 
Title: Re: Bugs/Issues tracker v3.2
Post by: opedroadami on May 20, 2017, 12:34:04 PM
So, there seems to be lots of 522 problems (which weren't happening before).

But the bot with 3.2GUI IS WORKING.

It just bought and sold some XEM with profit, the way it settings told it to do.

The problem is that the stats screen for the pair do not update.

The SESSION TRADES for the pair that traded do not update. It doesn't show the buy or the sell order, neither it updates with the total profit.

Also, between pairs, the BTC Balance is showing different values, which also doesn't update to reflect the new BTC Balance gained with the last trades.
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 20, 2017, 02:28:43 PM
~snip

Unfortunately we cant do anything against error 522: poloniex server issues. Just be patient and let the bot run until it gets good cycles and start to update again
Title: Re: Bugs/Issues tracker v3.2
Post by: magictrade on May 20, 2017, 03:05:43 PM
hi gunther,

parts of that problem are solved...........

but is it possible to trade this at the same time (for example) ?:

BTC/USDT
LTC/USDT
XMR/USDT
BTC/LTC
BTC/XMR
XMR/LTC

if i have my balance split in BTC, USDT and XMR
or will this confuse gunbot ?
Title: Re: Bugs/Issues tracker v3.2
Post by: opedroadami on May 20, 2017, 05:45:35 PM
~snip

Unfortunately we cant do anything against error 522: poloniex server issues. Just be patient and let the bot run until it gets good cycles and start to update again

Yeah, took me a while to notice that. POLO YOLO.

But the status from the pairs not refreshing is still an issue.

As I can see from the pair-log.txt, the bot is working properly but the stats are not refreshed.

Also, I would suggest moving the "STOP TRADING" button elsewhere. And make it bright red. If possible, with confirmation. It is really easy, as it is, to stop trading the pair, and from what I am earning on the last days using the bot that is the last thing I want to do.
Title: Re: Bugs/Issues tracker v3.2
Post by: evgsergej on May 20, 2017, 09:20:27 PM
Будет ли создан Gunbot под виндовс, а то с такими окошками неочень приятно работать?
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 20, 2017, 10:06:15 PM
Another observation:

I have been running lots of pairs with TRADING_VOLUME 0 at lower cycle time to have full BB stats. Then when I decide the pair should be active I just set it to 0.02 BTC for trading. This way I thought I can avoid having to wait for 10h to have complete BB stats. Since TRADING_VOLUME is zero no buy/sell action should happen. Then I noticed that the bots gets into limbo after a 0 BTC buy happens (which results in an error message). The bot is "waiting for orders 0 DGB" indefinetely although no altcoin balance/on orders. I attached the corresponding part of the log below. I will now run the TRADING_VOLUME with higher BTC (perhaps 0.001 BTC) instead. However, this could probably be fixed - if you have any hints what in the savefile I have to look for I would be grateful. This is running 3.2_core (22 update, not the GUI one). It was cycle 81, so stats were not completed yet and GAIN was used.

Code: [Select]
2017/05/18 10:58:35 [ --2017/05/18 10:58:35--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #81 --------------- ]
2017/05/18 10:58:35 ::::: collecting market data...
2017/05/18 10:58:35 ***************************************************
2017/05/18 10:58:35 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 10:58:35 ***************************************************
2017/05/18 10:58:38 LP 0.0000034  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 10:58:38 No open orders
2017/05/18 10:58:38 boughtPrice undefined
2017/05/18 10:58:38 price  grows (2)
2017/05/18 10:58:38 PriceToBuy,0.0338,priceToSell,--not set--
2017/05/18 10:58:38 LP 0.0340000,>,prBuy 0.0337905  secMargin 0.0000013516219178082197  grows yes
2017/05/18 10:58:38 no altcoins: 0
2017/05/18 10:58:38 price to buy: 0.000003379054794520549
2017/05/18 10:58:38 last price is too high
2017/05/18 10:58:38 Gunbot callback at 2017/05/18 10:58:38 cycle # 81
2017/05/18 10:58:38 Callback:
2017/05/18 10:58:38 ---------
2017/05/18 10:58:38 price too high
need faster: yes
need slower: no

2017/05/18 10:58:38 next delay will be 60s


2017/05/18 10:59:38 [ --2017/05/18 10:59:38--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #82 --------------- ]
2017/05/18 10:59:38 ::::: collecting market data...
2017/05/18 10:59:38 ***************************************************
2017/05/18 10:59:38 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 10:59:38 ***************************************************
2017/05/18 10:59:40 LP 0.00000335  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 10:59:40 No open orders
2017/05/18 10:59:40 boughtPrice undefined
2017/05/18 10:59:40 price  steady (0)
2017/05/18 10:59:40 PriceToBuy,0.0338,priceToSell,--not set--
2017/05/18 10:59:40 LP 0.0335000,<=,prBuy 0.0337796  secMargin 0.0000013511837837837842  grows yes
2017/05/18 10:59:40 no altcoins: 0
2017/05/18 10:59:40 price to buy: 0.00000337795945945946
2017/05/18 10:59:40 price is sweet to buy
2017/05/18 10:59:40 price is growing
2017/05/18 10:59:40 Buying on poloniex 0.0005 of DGB for 0.00000335
2017/05/18 10:59:40 2017/05/18 10:59:40 Error: Amount (0.0005) too low. Increase BTC_TRADING_LIMIT
2017/05/18 10:59:40 !!! Cycle 83 failed. Will repeat in 61s
2017/05/18 11:00:41 [ --2017/05/18 11:00:41--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #83 --------------- ]
2017/05/18 11:00:41 ::::: collecting market data...
2017/05/18 11:00:41 ***************************************************
2017/05/18 11:00:41 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 11:00:41 ***************************************************
2017/05/18 11:00:43 LP 0.00000336  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 11:00:43 No open orders
2017/05/18 11:00:43 boughtPrice undefined
2017/05/18 11:00:43 price  grows (1)
2017/05/18 11:00:43 PriceToBuy,0.0338,priceToSell,--not set--
2017/05/18 11:00:43 Gunbot callback at 2017/05/18 11:00:43 cycle # 83
2017/05/18 11:00:43 Callback:
2017/05/18 11:00:43 ---------
2017/05/18 11:00:43 Waiting for orders: 0 DGB
need faster: yes
need slower: no

2017/05/18 11:00:43 next delay will be 60s


2017/05/18 11:01:43 [ --2017/05/18 11:01:43--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #84 --------------- ]
2017/05/18 11:01:43 ::::: collecting market data...
2017/05/18 11:01:44 ***************************************************
2017/05/18 11:01:44 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 11:01:44 ***************************************************
2017/05/18 11:01:45 LP 0.00000339  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 11:01:45 No open orders
2017/05/18 11:01:45 boughtPrice undefined
2017/05/18 11:01:45 price  grows (1)
2017/05/18 11:01:45 PriceToBuy,0.0337,priceToSell,--not set--
2017/05/18 11:01:45 Gunbot callback at 2017/05/18 11:01:45 cycle # 84
2017/05/18 11:01:45 Callback:
2017/05/18 11:01:45 ---------
2017/05/18 11:01:45 Waiting for orders: 0 DGB
need faster: yes
need slower: no

2017/05/18 11:01:45 next delay will be 60s


2017/05/18 11:02:45 [ --2017/05/18 11:02:45--poloniex--BTC_DGB  --  Gunbot v3.2 cycle #85 --------------- ]
2017/05/18 11:02:45 ::::: collecting market data...
2017/05/18 11:02:46 ***************************************************
2017/05/18 11:02:46 Low BB:0.00000330 - High BB:0.00000366
2017/05/18 11:02:46 ***************************************************
2017/05/18 11:02:48 LP 0.0000034  Bal.BTC 0.31016783  Bal.DGB 0(0)
2017/05/18 11:02:48 No open orders
2017/05/18 11:02:48 boughtPrice undefined
2017/05/18 11:02:48 price  grows (1)
2017/05/18 11:02:48 PriceToBuy,0.0337,priceToSell,--not set--
2017/05/18 11:02:48 Gunbot callback at 2017/05/18 11:02:48 cycle # 85
2017/05/18 11:02:48 Callback:
2017/05/18 11:02:48 ---------
2017/05/18 11:02:48 Waiting for orders: 0 DGB
need faster: yes
need slower: no

2017/05/18 11:02:48 next delay will be 60s

Hey Gunthar, another update:

The same problem also happens if the bot places a regular buy order which is not getting filled soon because the price rises. The buy order is stuck and the bot is waiting to receive altcoin balance which never happens. I now have an order thats stuck for hours and who knows when the prices falls below the buy level and if its a good time then to place the buy.

I really think we should have some option that auto-cancels buy orders that are not filled within 1 hour or some other CONFIG variable. Thats the last big problem that I see, otherwise everything is working really well!

EDIT: buying a small amount of altcoin gets the bot going again. After it sells the altcoin, it resumes looking to buy.
Title: Re: Bugs/Issues tracker v3.2
Post by: gionni on May 21, 2017, 12:00:15 AM
Hi,
reporting an issue on poloniex.
I noticed that sometimes BTC_TRADING_LIMIT doesn't get picked up in hot reconfig.
I'm not sure if it's the whole reconfig or just that setting.
In the config file the limit was set at the new price but in the save.json was still the old one.


The FTP client I was using for editing the config files was not updating the date of the file so I believe it was not picked up by the BOT.
Title: Re: Bugs/Issues tracker v3.2
Post by: Swordfish85 on May 21, 2017, 05:26:05 PM
Quote
But the status from the pairs not refreshing is still an issue.

As I can see from the pair-log.txt, the bot is working properly but the stats are not refreshed.

Also, I would suggest moving the "STOP TRADING" button elsewhere. And make it bright red. If possible, with confirmation. It is really easy, as it is, to stop trading the pair, and from what I am earning on the last days using the bot that is the last thing I want to do.

Same issue here - the log is def. saying that the pair is running but i can't see any change in the console values...
any ideas to solve?
Title: Re: Bugs/Issues tracker v3.2
Post by: OutOfSync on May 21, 2017, 06:01:14 PM
Another issue with Kraken, gunbot bought 5x on EUR_XMR market (log is attached below). This is the newest version (3.2 with GUI, linuxx64). Perhaps the error "invalid nonce" came at a bad time @cyle 2781, messing things up?

Code: [Select]
2017/05/21 05:05:41 [ --2017/05/21 05:05:41--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2780 --------------- ]
2017/05/21 05:05:41 ::::: collecting market data...
2017/05/21 05:05:42 ***************************************************
2017/05/21 05:05:42 Low BB:29.54123831 - High BB:32.37372509
2017/05/21 05:05:42 ***************************************************
2017/05/21 05:05:47 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:05:47 Open orders
2017/05/21 05:05:47 boughtPrice 27.3
2017/05/21 05:05:47 price  grows (2)
2017/05/21 05:05:47 PriceToBuy,302493.6000,priceToSell,278460.0000
2017/05/21 05:05:47 LP 300414.0000000,<=,prBuy 302493.6000000  secMargin 12.09974400127787  grows yes
2017/05/21 05:05:47 no altcoins: 0
2017/05/21 05:05:47 price to buy: 30.24936000319467
2017/05/21 05:05:47 price is sweet to buy
2017/05/21 05:05:47 price is growing
2017/05/21 05:05:47 Buying on kraken 1.3319958690340663 of XXMR for 30.0414
2017/05/21 05:05:47 ***************************************************
2017/05/21 05:05:47 [object Object]
2017/05/21 05:05:47 ***************************************************
2017/05/21 05:05:48
2017/05/21 05:05:48 *** MARKET CALLBACK | buy 1.33199586 XMREUR @ limit 30.04140
2017/05/21 05:05:48 Gunbot callback at 2017/05/21 05:05:48 cycle # 2780
2017/05/21 05:05:48 Callback:
2017/05/21 05:05:48 ---------
2017/05/21 05:05:48 buy 1.33199586 XMREUR @ limit 30.04140
need faster: no
need slower: no

2017/05/21 05:05:48 next delay will be 120s


2017/05/21 05:07:48 [ --2017/05/21 05:07:48--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2781 --------------- ]
2017/05/21 05:07:48 ::::: collecting market data...
2017/05/21 05:07:49 ***************************************************
2017/05/21 05:07:49 Low BB:29.54068545 - High BB:32.37396461
2017/05/21 05:07:49 ***************************************************
2017/05/21 05:07:53 2017/05/21 05:07:53 Error: Error: Kraken API returned error: API:Invalid nonce
2017/05/21 05:07:53 !!! Cycle 2782 failed. Will repeat in 61s
2017/05/21 05:08:54 [ --2017/05/21 05:08:54--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2782 --------------- ]
2017/05/21 05:08:54 ::::: collecting market data...
2017/05/21 05:08:55 ***************************************************
2017/05/21 05:08:55 Low BB:29.54068545 - High BB:32.37396461
2017/05/21 05:08:55 ***************************************************
2017/05/21 05:08:59 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:08:59 Open orders
2017/05/21 05:08:59 boughtPrice 30.0414
2017/05/21 05:08:59 price  grows (2)
2017/05/21 05:08:59 PriceToBuy,302490.0524,priceToSell,306422.2800
2017/05/21 05:08:59 LP 300414.0000000,<=,prBuy 302490.0500000  secMargin 12.099602097637286  grows yes
2017/05/21 05:08:59 no altcoins: 0
2017/05/21 05:08:59 price to buy: 30.249005244093212
2017/05/21 05:08:59 price is sweet to buy
2017/05/21 05:08:59 price is growing
2017/05/21 05:08:59 Buying on kraken 1.3319958690340663 of XXMR for 30.0414
2017/05/21 05:08:59 ***************************************************
2017/05/21 05:08:59 [object Object]
2017/05/21 05:08:59 ***************************************************
2017/05/21 05:09:01
2017/05/21 05:09:01 *** MARKET CALLBACK | buy 1.33199586 XMREUR @ limit 30.04140
2017/05/21 05:09:01 Gunbot callback at 2017/05/21 05:09:01 cycle # 2782
2017/05/21 05:09:01 Callback:
2017/05/21 05:09:01 ---------
2017/05/21 05:09:01 buy 1.33199586 XMREUR @ limit 30.04140
need faster: no
need slower: no

2017/05/21 05:09:01 next delay will be 120s


2017/05/21 05:11:01 [ --2017/05/21 05:11:01--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2783 --------------- ]
2017/05/21 05:11:01 ::::: collecting market data...
2017/05/21 05:11:02 ***************************************************
2017/05/21 05:11:02 Low BB:29.53821808 - High BB:32.37492378
2017/05/21 05:11:02 ***************************************************
2017/05/21 05:11:07 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:11:07 Open orders
2017/05/21 05:11:07 boughtPrice 30.0414
2017/05/21 05:11:07 price  grows (2)
2017/05/21 05:11:07 PriceToBuy,302473.9451,priceToSell,306422.2800
2017/05/21 05:11:07 LP 300414.0000000,<=,prBuy 302473.9500000  secMargin 12.09895780359592  grows yes
2017/05/21 05:11:07 no altcoins: 0
2017/05/21 05:11:07 price to buy: 30.2473945089898
2017/05/21 05:11:07 price is sweet to buy
2017/05/21 05:11:07 price is growing
2017/05/21 05:11:07 Buying on kraken 1.3319958690340663 of XXMR for 30.0414
2017/05/21 05:11:07 ***************************************************
2017/05/21 05:11:07 [object Object]
2017/05/21 05:11:07 ***************************************************
2017/05/21 05:11:08
2017/05/21 05:11:08 *** MARKET CALLBACK | buy 1.33199586 XMREUR @ limit 30.04140
2017/05/21 05:11:08 Gunbot callback at 2017/05/21 05:11:08 cycle # 2783
2017/05/21 05:11:08 Callback:
2017/05/21 05:11:08 ---------
2017/05/21 05:11:08 buy 1.33199586 XMREUR @ limit 30.04140
need faster: no
need slower: no

2017/05/21 05:11:08 next delay will be 120s


2017/05/21 05:13:08 [ --2017/05/21 05:13:08--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2784 --------------- ]
2017/05/21 05:13:08 ::::: collecting market data...
2017/05/21 05:13:09 ***************************************************
2017/05/21 05:13:09 Low BB:29.53575331 - High BB:32.37587962
2017/05/21 05:13:09 ***************************************************
2017/05/21 05:13:13 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:13:13 Open orders
2017/05/21 05:13:13 boughtPrice 30.0414
2017/05/21 05:13:13 price  grows (2)
2017/05/21 05:13:13 PriceToBuy,302457.8489,priceToSell,306422.2800
2017/05/21 05:13:13 LP 300414.0000000,<=,prBuy 302457.8500000  secMargin 12.098313955105214  grows yes
2017/05/21 05:13:13 no altcoins: 0
2017/05/21 05:13:13 price to buy: 30.245784887763033
2017/05/21 05:13:13 price is sweet to buy
2017/05/21 05:13:13 price is growing
2017/05/21 05:13:13 Buying on kraken 1.3319958690340663 of XXMR for 30.0414
2017/05/21 05:13:13 ***************************************************
2017/05/21 05:13:13 [object Object]
2017/05/21 05:13:13 ***************************************************
2017/05/21 05:13:15
2017/05/21 05:13:15 *** MARKET CALLBACK | buy 1.33199586 XMREUR @ limit 30.04140
2017/05/21 05:13:15 Gunbot callback at 2017/05/21 05:13:15 cycle # 2784
2017/05/21 05:13:15 Callback:
2017/05/21 05:13:15 ---------
2017/05/21 05:13:15 buy 1.33199586 XMREUR @ limit 30.04140
need faster: no
need slower: no

2017/05/21 05:13:15 next delay will be 120s


2017/05/21 05:15:15 [ --2017/05/21 05:15:15--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2785 --------------- ]
2017/05/21 05:15:15 ::::: collecting market data...
2017/05/21 05:15:16 ***************************************************
2017/05/21 05:15:16 Low BB:29.53317275 - High BB:32.37686951
2017/05/21 05:15:16 ***************************************************
2017/05/21 05:15:20 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:15:20 Open orders
2017/05/21 05:15:20 boughtPrice 30.0414
2017/05/21 05:15:20 price  grows (1)
2017/05/21 05:15:20 PriceToBuy,302440.9694,priceToSell,306422.2800
2017/05/21 05:15:20 LP 300414.0000000,<=,prBuy 302440.9700000  secMargin 12.097638777421574  grows no
2017/05/21 05:15:20 no altcoins: 0
2017/05/21 05:15:20 price to buy: 30.244096943553934
2017/05/21 05:15:20 price is sweet to buy
2017/05/21 05:15:20 price is not growing
2017/05/21 05:15:20 Gunbot callback at 2017/05/21 05:15:20 cycle # 2785
2017/05/21 05:15:20 Callback:
2017/05/21 05:15:20 ---------
2017/05/21 05:15:20 price is not growing
need faster: yes
need slower: no

2017/05/21 05:15:20 next delay will be 60s


2017/05/21 05:16:20 [ --2017/05/21 05:16:20--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2786 --------------- ]
2017/05/21 05:16:20 ::::: collecting market data...
2017/05/21 05:16:21 ***************************************************
2017/05/21 05:16:21 Low BB:29.52818924 - High BB:32.37832889
2017/05/21 05:16:21 ***************************************************
2017/05/21 05:16:29 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:16:29 Open orders
2017/05/21 05:16:29 boughtPrice 30.0414
2017/05/21 05:16:29 price  grows (2)
2017/05/21 05:16:29 PriceToBuy,302407.2415,priceToSell,306422.2800
2017/05/21 05:16:29 LP 300414.0000000,<=,prBuy 302407.2400000  secMargin 12.096289661984457  grows yes
2017/05/21 05:16:29 no altcoins: 0
2017/05/21 05:16:29 price to buy: 30.240724154961143
2017/05/21 05:16:29 price is sweet to buy
2017/05/21 05:16:29 price is growing
2017/05/21 05:16:29 Buying on kraken 1.3319958690340663 of XXMR for 30.0414
2017/05/21 05:16:29 ***************************************************
2017/05/21 05:16:29 [object Object]
2017/05/21 05:16:29 ***************************************************
2017/05/21 05:16:34 2017/05/21 05:16:34 Error: Error in server response: {"code":"ESOCKETTIMEDOUT","connect":false}
2017/05/21 05:16:34 !!! Cycle 2787 failed. Will repeat in 61s
2017/05/21 05:17:35 [ --2017/05/21 05:17:35--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2787 --------------- ]
2017/05/21 05:17:35 ::::: collecting market data...
2017/05/21 05:17:36 ***************************************************
2017/05/21 05:17:36 Low BB:29.52322836 - High BB:32.37977204
2017/05/21 05:17:36 ***************************************************
2017/05/21 05:17:40 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:17:40 Open orders
2017/05/21 05:17:40 boughtPrice 30.0414
2017/05/21 05:17:40 price  grows (2)
2017/05/21 05:17:40 PriceToBuy,302373.6428,priceToSell,306422.2800
2017/05/21 05:17:40 LP 300414.0000000,<=,prBuy 302373.6400000  secMargin 12.094945711520088  grows yes
2017/05/21 05:17:40 no altcoins: 0
2017/05/21 05:17:40 price to buy: 30.237364278800218
2017/05/21 05:17:40 price is sweet to buy
2017/05/21 05:17:40 price is growing
2017/05/21 05:17:40 Buying on kraken 1.3319958690340663 of XXMR for 30.0414
2017/05/21 05:17:40 ***************************************************
2017/05/21 05:17:40 [object Object]
2017/05/21 05:17:40 ***************************************************
2017/05/21 05:17:45 2017/05/21 05:17:45 Error: Kraken API returned error: API:Invalid nonce
2017/05/21 05:17:45 !!! Cycle 2788 failed. Will repeat in 61s
2017/05/21 05:18:46 [ --2017/05/21 05:18:46--kraken--EUR_XMR  --  Gunbot v3.2 cycle #2788 --------------- ]
2017/05/21 05:18:46 ::::: collecting market data...
2017/05/21 05:18:47 ***************************************************
2017/05/21 05:18:47 Low BB:29.51912592 - High BB:32.38111342
2017/05/21 05:18:47 ***************************************************
2017/05/21 05:18:52 LP 30.0414  Bal.ZEUR 278.5751  Bal.XXMR 0
2017/05/21 05:18:52 Open orders
2017/05/21 05:18:52 boughtPrice 30.0414
2017/05/21 05:18:52 price  grows (1)
2017/05/21 05:18:52 PriceToBuy,302346.2279,priceToSell,306422.2800
2017/05/21 05:18:52 LP 300414.0000000,<=,prBuy 302346.2300000  secMargin 12.09384911635022  grows no
2017/05/21 05:18:52 no altcoins: 0
2017/05/21 05:18:52 price to buy: 30.234622790875548
2017/05/21 05:18:52 price is sweet to buy
2017/05/21 05:18:52 price is not growing
2017/05/21 05:18:52 Gunbot callback at 2017/05/21 05:18:52 cycle # 2788
2017/05/21 05:18:52 Callback:
2017/05/21 05:18:52 ---------
2017/05/21 05:18:52 price is not growing
need faster: yes
need slower: no
Title: Re: Bugs/Issues tracker v3.2
Post by: Meta on May 21, 2017, 06:45:30 PM
I am having some troubles with the 3.2GUI.

It all started normal, but the circles in RED don't update (shouldn't the CALLBACK be updated every bot cycle?) and the prices in YELLOW don't change (even after a while).

(https://preview.ibb.co/cZkekv/3_2gui.png) (https://ibb.co/hoNQQv)

Also, having problems with 522 error. In the 3.2GUI it freezes the bot, so I have to start over.

Then, I tried using the 3.1GUI until this is solved. But unfortunately I am also having 522 problems with it:

Quote
Loading config...
2017/05/20 11:06:05 Creating market client for BTC_DASH pair
Activating hot reconfig...
[ ---- poloniex -- 2017/05/20 11:06:05  --  Gunbot v3.1b cycle #1 -------------------------- ]
Loaded  poloniex-BTC_DASH-save.json
::::: collecting market data...
+2017/05/20 11:06:36 Error: statusCode 522
!!! Cycle 2 failed. Will repeat in 10s

But there the bot keeps on repeating the process until 522 is gone and it can cycle normally again.

The new GUI is really better in comparison with the old one, but those bugs kinda spoil the experience.

I have had same problem
This is due to strict internet options
Solution
add http://127.0.0.1 into Trusted Zone
Uncheck Protected Mode
Use custom security level (enable everything that is disabled)
Look video (sorry for bad video)
https://youtu.be/QujDRUUqcQk

Now my GUI 3.2 on Win 2012 updates
Title: Re: Bugs/Issues tracker v3.2
Post by: Swordfish85 on May 22, 2017, 02:35:57 AM
I've also solved the freezing Console/Callback: like it's said ^^above.

My Way:
open your internet explorer
go to Tools
Hover over Safety
Turn Smart Screen Filter OFF
Click:
Internet options
Security
Trusted Sites
Sites
Add: http://127.0.0.1
Add
Close
Go To Internet
Custom Level
Search Miscellaneous
Enable Meta Refresh
OK
OK
restart Bot

or press Windows Button + R and run inetcpl.cpl and do the above...

also i've allowed gunthy.exe and control console sample through firewall via Internet Settings --> Firewall --> Add App through Firewall

Just my two cents....
Title: Re: Bugs/Issues tracker v3.2
Post by: opedroadami on May 22, 2017, 03:02:57 PM
The frozen console GUI was fixed with the steps above. Thank you all!

But now I'm having this "Waiting for orders: 0 ETH" like on the image below.

(https://preview.ibb.co/hrgZ3F/0_order.png) (https://ibb.co/h67Vca)

Not only with ETH but with lots of other pairs too.

I have to stop the pair and start it again for it to be fixed.

EDIT:

Checking the logs for two of the pairs with this problem, there seems to be problems with the callback and also with handling of the Not Enough BTC warning:

Quote
2017/05/22 15:34:07   [ --2017/05/22 15:34:07--poloniex--BTC_DASH  --  Gunbot v3.2 cycle #40 --------------- ]
2017/05/22 15:34:07   ::::: collecting market data...
2017/05/22 15:34:08   ***************************************************
2017/05/22 15:34:08   Low BB:0.05567609 - High BB:0.06609449
2017/05/22 15:34:08   ***************************************************
2017/05/22 15:34:10   LP 0.05896  Bal.BTC 0.01773041  Bal.DASH 0(0)
2017/05/22 15:34:10   No open orders
2017/05/22 15:34:10   boughtPrice undefined
2017/05/22 15:34:10   price  grows (16)
2017/05/22 15:34:10   PriceToBuy,590.5873,priceToSell,--not set--
2017/05/22 15:34:10   LP 589.6000000,<=,prBuy 590.5873100  secMargin 0.02362349237076923  grows yes
2017/05/22 15:34:10   no altcoins: 0
2017/05/22 15:34:10   price to buy: 0.05905873092692308
2017/05/22 15:34:10   price is sweet to buy
2017/05/22 15:34:10   price is growing
2017/05/22 15:34:10   Buying on poloniex 0.30121930122116686 of DASH for 0.05896
2017/05/22 15:34:29   2017/05/22 15:34:29 Error: Not enough BTC.
2017/05/22 15:34:29   !!! Cycle 41 failed. Will repeat in 30s
2017/05/22 15:34:59   [ --2017/05/22 15:34:59--poloniex--BTC_DASH  --  Gunbot v3.2 cycle #41 --------------- ]
2017/05/22 15:34:59   ::::: collecting market data...
2017/05/22 15:35:00   ***************************************************
2017/05/22 15:35:00   Low BB:0.05565247 - High BB:0.06597549
2017/05/22 15:35:00   ***************************************************
2017/05/22 15:35:01   LP 0.06  Bal.BTC 0.01773041  Bal.DASH 0(0)
2017/05/22 15:35:01   No open orders
2017/05/22 15:35:01   boughtPrice undefined
2017/05/22 15:35:01   price  grows (17)
2017/05/22 15:35:01   PriceToBuy,589.8956,priceToSell,--not set--
2017/05/22 15:35:01   Gunbot callback at 2017/05/22 15:35:01 cycle # 41
2017/05/22 15:35:01   Callback:
2017/05/22 15:35:01   ---------
2017/05/22 15:35:01   Waiting for orders: 0 DASH
need faster: no
need slower: no

Quote
2017/05/22 14:56:52   [ --2017/05/22 14:56:52--poloniex--BTC_ETH  --  Gunbot v3.2 cycle #55 --------------- ]
2017/05/22 14:56:52   ::::: collecting market data...
2017/05/22 14:56:52   ***************************************************
2017/05/22 14:56:52   Low BB:0.07684201 - High BB:0.08037168
2017/05/22 14:56:52   ***************************************************
2017/05/22 14:56:58   2017/05/22 14:56:58 Error: statusCode 422
2017/05/22 14:56:58   !!! Cycle 56 failed. Will repeat in 30s
2017/05/22 14:57:28   [ --2017/05/22 14:57:28--poloniex--BTC_ETH  --  Gunbot v3.2 cycle #56 --------------- ]
2017/05/22 14:57:28   ::::: collecting market data...
2017/05/22 14:57:29   ***************************************************
2017/05/22 14:57:29   Low BB:0.07684201 - High BB:0.08037168
2017/05/22 14:57:29   ***************************************************
2017/05/22 14:57:31   LP 0.0761  Bal.BTC 0.00714426  Bal.ETH 0(0)
2017/05/22 14:57:31   No open orders
2017/05/22 14:57:31   boughtPrice 0.06197
2017/05/22 14:57:31   price  falls (-5)
2017/05/22 14:57:31   PriceToBuy,762.4864,priceToSell,632.0940
2017/05/22 14:57:31   LP 761.0000000,<=,prBuy 762.4864000  secMargin 0.030499455801212123  grows yes
2017/05/22 14:57:31   no altcoins: 0
2017/05/22 14:57:31   price to buy: 0.0762486395030303
2017/05/22 14:57:31   price is sweet to buy
2017/05/22 14:57:31   price is growing
2017/05/22 14:57:31   Buying on poloniex 0.09437989487516427 of ETH for 0.0761
2017/05/22 14:57:39   2017/05/22 14:57:39 Error: statusCode 422
2017/05/22 14:57:39   !!! Cycle 57 failed. Will repeat in 30s
2017/05/22 14:58:09   [ --2017/05/22 14:58:09--poloniex--BTC_ETH  --  Gunbot v3.2 cycle #57 --------------- ]
2017/05/22 14:58:09   ::::: collecting market data...
2017/05/22 14:58:10   ***************************************************
2017/05/22 14:58:10   Low BB:0.07659415 - High BB:0.08047208
2017/05/22 14:58:10   ***************************************************
2017/05/22 14:58:17   2017/05/22 14:58:17 Error: statusCode 422
2017/05/22 14:58:17   !!! Cycle 58 failed. Will repeat in 30s
2017/05/22 14:58:47   [ --2017/05/22 14:58:47--poloniex--BTC_ETH  --  Gunbot v3.2 cycle #58 --------------- ]
2017/05/22 14:58:47   ::::: collecting market data...
2017/05/22 14:58:48   ***************************************************
2017/05/22 14:58:48   Low BB:0.07659415 - High BB:0.08047208
2017/05/22 14:58:48   ***************************************************
2017/05/22 14:58:50   LP 0.07617166  Bal.BTC 0.00714426  Bal.ETH 0(0)
2017/05/22 14:58:50   No open orders
2017/05/22 14:58:50   boughtPrice 0.06197
2017/05/22 14:58:50   price  falls (-5)
2017/05/22 14:58:50   PriceToBuy,761.7712,priceToSell,632.0940
2017/05/22 14:58:50   Gunbot callback at 2017/05/22 14:58:50 cycle # 58
2017/05/22 14:58:50   Callback:
2017/05/22 14:58:50   ---------
2017/05/22 14:58:50   Waiting for orders: 0 ETH
need faster: no
need slower: no
Title: Re: Bugs/Issues tracker v3.2
Post by: chemical on May 23, 2017, 12:05:52 AM
Just a minor thing when running twenty six pairs  ;D
the bottom of the GUI gets cut off

(http://i.imgur.com/7KfwPBv.jpg)
Title: Re: Bugs/Issues tracker v3.2
Post by: teknomen on May 23, 2017, 01:29:36 AM


all the pairs run normal but after 2 days i try to add DOGE pair and this happens


(http://i.imgur.com/1nmIhgX.jpg)

Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Process with an Id of 3244 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
   at ConsoleControlSample.Form2.btn_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1648.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
GUNBOT
    Assembly Version: 1.0.1.0
    Win32 Version: 1.0.1.0
    CodeBase: file:///C:/Users/Administrator/Desktop/3.2/GUNBOT.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1586.0 built by: NETFXREL2
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1647.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1586.0 built by: NETFXREL2
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Title: Re: Bugs/Issues tracker v3.2
Post by: BlkCalais on May 23, 2017, 04:46:38 AM
I have just set up Gunbot and am have the same issue as Teknomen. Not sure if i have missed something but can't seem to set up any Coin Pairs. Have tried a few different ones and get the same error.

Gunthy fixed my issue. Was an key issue.
Title: Re: Bugs/Issues tracker v3.2
Post by: Refus on May 23, 2017, 08:17:52 AM
I am also receiving the "Navigation to the webpage has been canceled" everytime when starting any pair(I make sure to wait for the pair) on the x4 tab in 3.2 Brazil, running on Amazon Windows AWS. I was running 2.0.4 smoothly before attempting the upgrade.

Have the newest Node.js installed and also tried a fresh VPS. I have tried adding http://127.0.0.1 to trusted sites, and enabling everything in the Custom Level section of trusted sites and internet as advised by the telegram chat, but to no avail.

Some people in the telegram chat think it may be API key related, but I haven't made any changes to my key that I gave Gunthar originally.

Edit: API key issue. Gunthar fixed for me.
Title: Re: Bugs/Issues tracker v3.2
Post by: BitFlipp4r on May 23, 2017, 11:42:11 AM
I'm having issues when starting new coins with missing bought price:

2017/05/20 14:48:38     Activating hot reconfig...
2017/05/20 14:48:38     [ --2017/05/20 14:48:38--poloniex--BTC_XRP  --  Gunbot v3.2 cycle #1 --------------- ]
2017/05/20 14:48:38     ::::: collecting market data...
2017/05/20 14:48:38     Server running at http://127.0.0.1:43398
2017/05/20 14:48:39     ***************************************************
2017/05/20 14:48:39     Low BB:0.00000000 - High BB:0.00000000
2017/05/20 14:48:39     ***************************************************
2017/05/20 14:48:41     LP 0.000181  Bal.BTC 0.04291979  Bal.XRP 109.975(0)
2017/05/20 14:48:41     No open orders
2017/05/20 14:48:41     boughtPrice undefined
2017/05/20 14:48:41     price  steady (0)
2017/05/20 14:48:41     PriceToBuy,0.0000,priceToSell,--not set--
2017/05/20 14:48:41     we have altcoins: 109.975
2017/05/20 14:48:41     2017/05/20 14:48:41 Error: Missing boughtPrice
2017/05/20 14:48:41     !!! Cycle 2 failed. Will repeat in 60s
2017/05/20 21:00:31     Activating hot reconfig...
2017/05/20 21:00:31     [ --2017/05/20 21:00:31--poloniex--BTC_XRP  --  Gunbot v3.2 cycle #1 --------------- ]
2017/05/20 21:00:31     ::::: collecting market data...

It works if I set SELL_ON_START to true... however this not an option if I don't want to sell my current altcoins.
I'm starting the bot with console commands (Version 3.2. Brazil)
Title: Re: Bugs/Issues tracker v3.2
Post by: beer-k0in on May 23, 2017, 11:17:29 PM
Buying and Poloniex error 422 result in less log output
(gunthy-linuxx64 binary from the GUNBOT_v3.2_GUI_edition_all_CPU on ubuntu 16.04.)

Bot wants to buy, but the buy request results in a 422

Code: [Select]
2017/05/23 13:35:14 [ --2017/05/23 13:35:14--poloniex--BTC_MAID  --  Gunbot v3.2 cycle #797 --------------- ]
2017/05/23 13:35:14 ::::: collecting market data...
2017/05/23 13:35:17 LP 0.0001765  Bal.BTC 0.30091175  Bal.MAID 0(0)
2017/05/23 13:35:17 No open orders
2017/05/23 13:35:17 boughtPrice 0.00016775
2017/05/23 13:35:17 price  falls (-3)
2017/05/23 13:35:17 PriceToBuy,1.7716,priceToSell,1.7614
2017/05/23 13:35:17 LP 1.7650000,<=,prBuy 1.7715878  secMargin 0.0000708635135333334  grows yes
2017/05/23 13:35:17 no altcoins: 0
2017/05/23 13:35:17 price to buy: 0.00017715878383333349
2017/05/23 13:35:17 price is sweet to buy
2017/05/23 13:35:17 price is growing
2017/05/23 13:35:17 Buying on poloniex 311.61523087818694 of MAID for 0.0001765
2017/05/23 13:35:21 2017/05/23 13:35:21 Error: statusCode 422
2017/05/23 13:35:21 !!! Cycle 798 failed. Will repeat in 66s

Next cycle is also a 422

Code: [Select]
2017/05/23 13:36:27 [ --2017/05/23 13:36:27--poloniex--BTC_MAID  --  Gunbot v3.2 cycle #798 --------------- ]
2017/05/23 13:36:27 ::::: collecting market data...
2017/05/23 13:36:31 2017/05/23 13:36:31 Error: statusCode 422
2017/05/23 13:36:31 !!! Cycle 799 failed. Will repeat in 66s

Since that, the log looks like this. I do not know if the bot is just skipping output or is in an bad state. But there where no trades after cycle 799.
Restart helps.

Code: [Select]
2017/05/23 13:37:37 [ --2017/05/23 13:37:37--poloniex--BTC_MAID  --  Gunbot v3.2 cycle #799 --------------- ]
2017/05/23 13:37:37 ::::: collecting market data...
2017/05/23 13:37:43 LP 0.00017681  Bal.BTC 0.30091175  Bal.MAID 0(0)
2017/05/23 13:37:43 No open orders
2017/05/23 13:37:43 boughtPrice 0.00016775
2017/05/23 13:37:43 price  falls (-3)
2017/05/23 13:37:43 PriceToBuy,1.7715,priceToSell,1.7614
2017/05/23 13:37:43 Gunbot callback at 2017/05/23 13:37:43 cycle # 799
2017/05/23 13:37:43 Callback:
2017/05/23 13:37:43 ---------
2017/05/23 13:37:43 Waiting for orders: 0 MAID
2017/05/23 13:37:43 next delay will be 55.5s


Same with BB:

Code: [Select]
2017/05/23 13:27:08 [ --2017/05/23 13:27:08--poloniex--BTC_ZEC  --  Gunbot v3.2 cycle #514 --------------- ]
2017/05/23 13:27:08 ::::: collecting market data...
2017/05/23 13:27:09 ***************************************************
2017/05/23 13:27:09 Low BB:0.09739015 - High BB:0.13685431
2017/05/23 13:27:09 ***************************************************
2017/05/23 13:27:11 LP 0.107  Bal.BTC 0.67201412  Bal.ZEC 0(0)
2017/05/23 13:27:11 No open orders
2017/05/23 13:27:11 boughtPrice 0.09772085
2017/05/23 13:27:11 price  falls (-7)
2017/05/23 13:27:11 PriceToBuy,1076.5083,priceToSell,1026.0689
2017/05/23 13:27:11 LP 1070.0000000,<=,prBuy 1076.5083000  secMargin 0.04306033333639771  grows yes
2017/05/23 13:27:11 no altcoins: 0
2017/05/23 13:27:11 price to buy: 0.10765083334099426
2017/05/23 13:27:11 price is sweet to buy
2017/05/23 13:27:11 price is growing
2017/05/23 13:27:11 Buying on poloniex 0.514518691588785 of ZEC for 0.107

2017/05/23 13:28:22 2017/05/23 13:28:22 Error: Order execution timed out.
2017/05/23 13:28:22 !!! Cycle 515 failed. Will repeat in 66s


2017/05/23 13:29:28 [ --2017/05/23 13:29:28--poloniex--BTC_ZEC  --  Gunbot v3.2 cycle #515 --------------- ]
2017/05/23 13:29:28 ::::: collecting market data...
2017/05/23 13:29:28 ***************************************************
2017/05/23 13:29:28 Low BB:0.09756363 - High BB:0.13676145
2017/05/23 13:29:28 ***************************************************
2017/05/23 13:29:36 2017/05/23 13:29:36 Error: statusCode 422
2017/05/23 13:29:36 !!! Cycle 516 failed. Will repeat in 66s


2017/05/23 13:30:42 [ --2017/05/23 13:30:42--poloniex--BTC_ZEC  --  Gunbot v3.2 cycle #516 --------------- ]
2017/05/23 13:30:42 ::::: collecting market data...
2017/05/23 13:30:42 ***************************************************
2017/05/23 13:30:42 Low BB:0.09756363 - High BB:0.13676145
2017/05/23 13:30:42 ***************************************************
2017/05/23 13:30:47 2017/05/23 13:30:47 Error: statusCode 422
2017/05/23 13:30:47 !!! Cycle 517 failed. Will repeat in 66s


2017/05/23 13:31:53 [ --2017/05/23 13:31:53--poloniex--BTC_ZEC  --  Gunbot v3.2 cycle #517 --------------- ]
2017/05/23 13:31:53 ::::: collecting market data...
2017/05/23 13:31:53 ***************************************************
2017/05/23 13:31:53 Low BB:0.09756363 - High BB:0.13676145
2017/05/23 13:31:53 ***************************************************
2017/05/23 13:31:58 2017/05/23 13:31:58 Error: statusCode 422
2017/05/23 13:31:58 !!! Cycle 518 failed. Will repeat in 66s


2017/05/23 13:33:04 [ --2017/05/23 13:33:04--poloniex--BTC_ZEC  --  Gunbot v3.2 cycle #518 --------------- ]
2017/05/23 13:33:04 ::::: collecting market data...
2017/05/23 13:33:04 ***************************************************
2017/05/23 13:33:04 Low BB:0.09756363 - High BB:0.13676145
2017/05/23 13:33:04 ***************************************************
2017/05/23 13:33:08 LP 0.10780009  Bal.BTC 0.67201412  Bal.ZEC 0(0)
2017/05/23 13:33:08 No open orders
2017/05/23 13:33:08 boughtPrice 0.09772085
2017/05/23 13:33:08 price  falls (-7)
2017/05/23 13:33:08 PriceToBuy,1077.5506,priceToSell,1026.0689
2017/05/23 13:33:08 Gunbot callback at 2017/05/23 13:33:08 cycle # 518
2017/05/23 13:33:08 Callback:
2017/05/23 13:33:08 ---------
2017/05/23 13:33:08 Waiting for orders: 0 ZEC
2017/05/23 13:33:08 next delay will be 111s


BK
Title: Re: Bugs/Issues tracker v3.2
Post by: Klon552 on May 24, 2017, 01:35:35 AM
Some people already mentioned it in the chat:

Sometimes the bot got stuck on a buy order. I use 3.2 no GUI. Windows 2008 R2.

(https://i.imgsafe.org/4d29d94dea.jpg)
Quote
Server time: 2017-05-24 00:17 UTC

And i have No Neos or NXC in my bag.

NXC seems ok:
Code: [Select]
[ --2017/05/24 00:27:19--poloniex--BTC_NXC  --  Gunbot v3.2 cycle #534 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00008496 - High BB:0.00009044
***************************************************
++++
LP 0.00008927  Bal.BTC 0.21447953  Bal.NXC 0(0)
Open orders
boughtPrice 0.00008556
price  steady (0)
PriceToBuy 0.8578 priceToSell 0.8727
LP 0.8927000 > prBuy 0.8577934  secMargin 0.0000343117338620842  grows no
no altcoins: 0
price to buy: 0.00008577933465521049
last price is too high
Gunbot callback at 2017/05/24 00:27:21 cycle # 534
Callback:
---------
price too high
need faster: yes
need slower: no

next delay will be 46.41596604148094s

But NEOS got stuck:

Code: [Select]
[ --2017/05/22 21:20:22--poloniex--BTC_NEOS  --  Gunbot v3.2 cycle #53 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00102671 - High BB:0.00109692
***************************************************
++++
LP 0.00104951  Bal.BTC 0.21447953  Bal.NEOS 0(0)
Open orders
boughtPrice 0.00104001
price  steady (0)
PriceToBuy 10.2996 priceToSell 10.6081
Gunbot callback at 2017/05/22 21:20:23 cycle # 53
Callback:
---------
Waiting for orders: 0 NEOS  <-----this!
need faster: no
need slower: no

next delay will be 95.96648976621125s

And there were/are some other coins too. Sometimes even without a buy order:

No ARDR bag:

Code: [Select]
[ --2017/05/22 21:33:32--poloniex--BTC_ARDR  --  Gunbot v3.2 cycle #633 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00006430 - High BB:0.00006813
***************************************************
++++
LP 0.00006616  Bal.BTC 0.24476679  Bal.ARDR 0(0)
No open orders
boughtPrice 0.00006461
price  grows (9)
PriceToBuy 0.6487 priceToSell 0.6590
Gunbot callback at 2017/05/22 21:33:36 cycle # 633
Callback:
---------
Waiting for orders: 0 ARDR
need faster: yes
need slower: no

next delay will be 44.58809372024429s



Also it didnt matter if i canceled the Buy order manually before or not. And it seems its always the same coins:

for example:

BTCD,BCN,DOGE,AMP, XVC

and maybe some other.

Deleting the save, log, even restart the coin from scratch with "new" config doesnt seem to help, either.

If you need some additional infos, let me know.


EDIT:

I noticed something else. Sometimes the bot got stuck for some time (minute or so) at the end of a cycle at the red line.

Quote
2017/05/24 01:32:43   [ --2017/05/24 01:32:43--poloniex--BTC_NOTE  --  Gunbot v3.2 cycle #121 --------------- ]
2017/05/24 01:32:43   ::::: collecting market data...
2017/05/24 01:32:43   ***************************************************
2017/05/24 01:32:43   Low BB:0.00003210 - High BB:0.00003422
2017/05/24 01:32:43   ***************************************************
2017/05/24 01:32:44   --canceling buy orders
2017/05/24 01:32:44   LP 0.0000343  Bal.BTC 0.29602865  Bal.NOTE 0(0)
2017/05/24 01:32:44   No open orders
2017/05/24 01:32:44   boughtPrice 0.00003302
2017/05/24 01:32:44   price  grows (6)
2017/05/24 01:32:44   PriceToBuy,0.3217,priceToSell,0.3368
2017/05/24 01:32:44   LP 0.3430000,>,prBuy 0.3216854  secMargin 0.000012867416806722673  grows yes
2017/05/24 01:32:44   no altcoins: 0
2017/05/24 01:32:44   price to buy: 0.00003216854201680668
2017/05/24 01:32:44   last price is too high
2017/05/24 01:32:44   Gunbot callback at 2017/05/24 01:32:44 cycle # 121
2017/05/24 01:32:44   Callback:
2017/05/24 01:32:44   ---------
2017/05/24 01:32:44   price too high
need faster: no
need slower: no

2017/05/24 01:32:44   next delay will be 80.89921774715756s


2017/05/24 01:32:45   Open buy orders: ,0
2017/05/24 01:32:45   
2017/05/24 01:34:05   [ --2017/05/24 01:34:05--poloniex--BTC_NOTE  --  Gunbot v3.2 cycle #122 --------------- ]
2017/05/24 01:34:05   ::::: collecting market data...
2017/05/24 01:34:06   ***************************************************
2017/05/24 01:34:06   Low BB:0.00003210 - High BB:0.00003425
2017/05/24 01:34:06   ***************************************************
2017/05/24 01:34:08   LP 0.00003375  Bal.BTC 0.28602841  Bal.NOTE 0(0)
2017/05/24 01:34:08   No open orders
2017/05/24 01:34:08   boughtPrice 0.00003302
2017/05/24 01:34:08   price  grows (4)
2017/05/24 01:34:08   PriceToBuy,0.3218,priceToSell,0.3368
2017/05/24 01:34:08   LP 0.3375000,>,prBuy 0.3217773  secMargin 0.000012871091666666647  grows no
2017/05/24 01:34:08   no altcoins: 0
2017/05/24 01:34:08   price to buy: 0.000032177729166666615
2017/05/24 01:34:08   last price is too high
2017/05/24 01:34:08   Gunbot callback at 2017/05/24 01:34:08 cycle # 122
2017/05/24 01:34:08   Callback:
2017/05/24 01:34:08   ---------
2017/05/24 01:34:08   price too high
need faster: no
need slower: no

2017/05/24 01:34:08   next delay will be 80.89921774715756s

The Bot didnt buy NOTE nor was there an buy order in "open orders".
Title: Re: Bugs/Issues tracker v3.2
Post by: zardos on May 24, 2017, 07:11:18 AM
The frozen console GUI was fixed with the steps above. Thank you all!

But now I'm having this "Waiting for orders: 0 ETH" like on the image below.

(https://preview.ibb.co/hrgZ3F/0_order.png) (https://ibb.co/h67Vca)

Not only with ETH but with lots of other pairs too.

I have to stop the pair and start it again for it to be fixed.


THIS ^^^^^   
In Telegram, many many are talking about this issue.  It's the main issue I have every day.   I just looked at my 10 pairs, and 3 of them were stuck in this waiting for 0 order state.    Granted, some had BUY orders waiting... BUT, these buy orders were WAY down on the chart -- nowhere near a buy point.   So I have to manually close the BUY order (sometimes there isn't a buy order, it's just stuck with no orders), and restart the bots every 6 hours.   Hope you can figure out what is going on here!
Title: Re: Bugs/Issues tracker v3.2
Post by: TopPlayer on May 24, 2017, 10:30:28 AM
The frozen console GUI was fixed with the steps above. Thank you all!

But now I'm having this "Waiting for orders: 0 ETH" like on the image below.

(https://preview.ibb.co/hrgZ3F/0_order.png) (https://ibb.co/h67Vca)

Not only with ETH but with lots of other pairs too.

I have to stop the pair and start it again for it to be fixed.


THIS ^^^^^   
In Telegram, many many are talking about this issue.  It's the main issue I have every day.   I just looked at my 10 pairs, and 3 of them were stuck in this waiting for 0 order state.    Granted, some had BUY orders waiting... BUT, these buy orders were WAY down on the chart -- nowhere near a buy point.   So I have to manually close the BUY order (sometimes there isn't a buy order, it's just stuck with no orders), and restart the bots every 6 hours.   Hope you can figure out what is going on here!

Same here.
Title: Re: Bugs/Issues tracker v3.2
Post by: maruaria on May 25, 2017, 12:34:43 PM
Security Margin Issue

The security margin is calculated by the price to buy, not the last buy price..

Now, [security margin] = [price to buy] * (1 - [security margin %])

it should be, [security margin] = [last buy price] * (1 - [security margin %])


In this screenshot
security margin % = 60%
security margin = 0.00004144
price to buy       = 0.00010363 => 4144/10363 = 0.400
last buy price    = 0.00010700 => 4144/10700 = 0.387 = wrong



Title: Re: Bugs/Issues tracker v3.2
Post by: adxatand on May 25, 2017, 09:55:11 PM
I have this issue as well 3.2 gui, but im running it from cmd.  It gets stuck fairly frequently.  I've had to reset ETH and a few other pairs at least 3-4 times in the last few hours, and it hasn't tried to place any orders in that time for any of the affected pairs.  I'm running about 20 pairs total on t his server.

The frozen console GUI was fixed with the steps above. Thank you all!

But now I'm having this "Waiting for orders: 0 ETH" like on the image below.

(https://preview.ibb.co/hrgZ3F/0_order.png) (https://ibb.co/h67Vca)

Not only with ETH but with lots of other pairs too.

I have to stop the pair and start it again for it to be fixed.


THIS ^^^^^   
In Telegram, many many are talking about this issue.  It's the main issue I have every day.   I just looked at my 10 pairs, and 3 of them were stuck in this waiting for 0 order state.    Granted, some had BUY orders waiting... BUT, these buy orders were WAY down on the chart -- nowhere near a buy point.   So I have to manually close the BUY order (sometimes there isn't a buy order, it's just stuck with no orders), and restart the bots every 6 hours.   Hope you can figure out what is going on here!

Same here.
Title: Re: Bugs/Issues tracker v3.2
Post by: sinabu on May 26, 2017, 12:23:21 AM
Along with the Waiting on Order O xxx Error I started noticing the last digit is getting cut off. Even starting doesn't fix the issue

Last price and last buy order price both are missing the 8th digit past the decimal and then Price to buy is expanding out way past the 8th. Wasn't sure if that was intentional or not on the last part.



Title: Re: Bugs/Issues tracker v3.2
Post by: Philippe1987 on May 26, 2017, 10:16:28 AM
Hi all,

When I click the statistics button and go to the best currencies tab, all I see is this:
(http://i.imgur.com/tgk1Pym.png)

When I open the log file, I see the bot generated the best currencies, but it just doesn't show in the GUI. :(
(http://i.imgur.com/xXtEptU.png)

A friend of mine who also owns the bot has the exact same issue.

Thanks!
Title: Re: Bugs/Issues tracker v3.2
Post by: dj31 on May 26, 2017, 07:04:24 PM
Hi all,

When I click the statistics button and go to the best currencies tab, all I see is this:
(http://i.imgur.com/tgk1Pym.png)

The text was there for me, but the color was inverted.    Try to select some text with your mouse, you should see it.
Title: Re: Bugs/Issues tracker v3.2
Post by: cw 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)

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



Title: Re: Bugs/Issues tracker v3.2
Post by: Philippe1987 on May 26, 2017, 10:39:29 PM
Indeed, now I see the text. Thanks!

Hi all,

When I click the statistics button and go to the best currencies tab, all I see is this:
(http://i.imgur.com/tgk1Pym.png)

The text was there for me, but the color was inverted.    Try to select some text with your mouse, you should see it.
Title: Re: Bugs/Issues tracker v3.2
Post by: beer-k0in on May 28, 2017, 11:42:57 PM
Buying and Poloniex error 422 result in less log output
(gunthy-linuxx64 binary from the GUNBOT_v3.2_GUI_edition_all_CPU on ubuntu 16.04.)

Looks like it is the combination buying and any error results in less log output and also no trades.

Another user in the Telegram chat had this problem because of an error of insufficient BTC:
(on Ubuntu 16.04.)

Buying and error
Code: [Select]
2017/05/28 07:54:02 [ --2017/05/28 07:54:02--poloniex--BTC_AMP  --  Gunbot v3.2 cycle #709 --------------- ]
2017/05/28 07:54:02 ::::: collecting market data...
2017/05/28 07:54:02 ***************************************************
2017/05/28 07:54:02 Low BB:0.00010209 - High BB:0.00010785
2017/05/28 07:54:02 ***************************************************
2017/05/28 07:54:05 LP 0.00010329  Bal.BTC 0.00253843  Bal.AMP 0(0)
2017/05/28 07:54:05 No open orders
2017/05/28 07:54:05 boughtPrice undefined
2017/05/28 07:54:05 price  falls (-2)
2017/05/28 07:54:05 PriceToBuy,1.0353,priceToSell,--not set--
2017/05/28 07:54:05 LP 1.0329000,<=,prBuy 1.0352849  secMargin 0.000041411394891158713  grows yes
2017/05/28 07:54:05 no altcoins: 0
2017/05/28 07:54:05 price to buy: 0.00010352848722789678
2017/05/28 07:54:05 price is sweet to buy
2017/05/28 07:54:05 price is growing
2017/05/28 07:54:05 Buying on poloniex 24.576257575757577 of AMP for 0.00010329
2017/05/28 07:54:07 2017/05/28 07:54:07 Error: Not enough BTC.
2017/05/28 07:54:07 !!! Cycle 710 failed. Will repeat in 30s
2017/05/28 07:54:37 [ --2017/05/28 07:54:37--poloniex--BTC_AMP  --  Gunbot v3.2 cycle #710 --------------- ]
2017/05/28 07:54:37 ::::: collecting market data...
2017/05/28 07:54:37 ***************************************************
2017/05/28 07:54:37 Low BB:0.00010208 - High BB:0.00010785
2017/05/28 07:54:37 ***************************************************
2017/05/28 07:54:39 LP 0.00010329  Bal.BTC 0.00253843  Bal.AMP 0(0)
2017/05/28 07:54:39 No open orders
2017/05/28 07:54:39 boughtPrice undefined
2017/05/28 07:54:39 price  falls (-2)
2017/05/28 07:54:39 PriceToBuy,1.0353,priceToSell,--not set--
2017/05/28 07:54:39 Gunbot callback at 2017/05/28 07:54:39 cycle # 710
2017/05/28 07:54:39 Callback:
2017/05/28 07:54:39 ---------
2017/05/28 07:54:39 Waiting for orders: 0 AMP
need faster: yes
need slower: no

2017/05/28 07:54:39 next delay will be 30s

From now on till a restart of the bot, the log looks like this:
Code: [Select]
2017/05/28 22:10:24 [ --2017/05/28 22:10:24--poloniex--BTC_AMP  --  Gunbot v3.2 cycle #2279 --------------- ]
2017/05/28 22:10:24 ::::: collecting market data...
2017/05/28 22:10:25 ***************************************************
2017/05/28 22:10:25 Low BB:0.00008968 - High BB:0.00009935
2017/05/28 22:10:25 ***************************************************
2017/05/28 22:10:27 LP 0.00009414  Bal.BTC 0.00597332  Bal.AMP 0(0)
2017/05/28 22:10:27 No open orders
2017/05/28 22:10:27 boughtPrice undefined
2017/05/28 22:10:27 price  falls (-1)
2017/05/28 22:10:27 PriceToBuy,0.9209,priceToSell,--not set--
2017/05/28 22:10:27 Gunbot callback at 2017/05/28 22:10:27 cycle # 2279
2017/05/28 22:10:27 Callback:
2017/05/28 22:10:27 ---------
2017/05/28 22:10:27 Waiting for orders: 0 AMP
need faster: yes
need slower: no

2017/05/28 22:10:27 next delay will be 30s

BK
Title: Re: Bugs/Issues tracker v3.2
Post by: King on May 30, 2017, 07:24:12 PM


all the pairs run normal but after 2 days i try to add DOGE pair and this happens


(http://i.imgur.com/1nmIhgX.jpg)

Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Process with an Id of 3244 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
   at ConsoleControlSample.Form2.btn_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1648.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
GUNBOT
    Assembly Version: 1.0.1.0
    Win32 Version: 1.0.1.0
    CodeBase: file:///C:/Users/Administrator/Desktop/3.2/GUNBOT.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1586.0 built by: NETFXREL2
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1647.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1586.0 built by: NETFXREL2
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Have the same issue
Title: Re: Bugs/Issues tracker v3.2
Post by: Gunthar on May 30, 2017, 09:48:28 PM
Thanks to all of you that contribute testing adn reporting, we move to the 3.3 bugs tracker now
~Gun