Gunthy

GUNBOT: The automatic profit generator => Technical Support & Development => Topic started by: Singman on December 07, 2020, 02:53:24 PM

Title: GB 20.7.5 and Kraken
Post by: Singman on December 07, 2020, 02:53:24 PM
Hi,

I get this error since GB 20.xxx series and still no hope to get it fixed.
Exchange : Kraken

Code: [Select]
GB_20.7.5 GBP-ETH@kraken Round #103045 2020/12/07 15:40:46
Error: Error: General:Invalid arguments:volume
    at errorHandler (/snapshot/test/Desktop/node14/ctx/js/kraken.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

┌───────────────────┬────┐
│ ɢՍÑɮØŁ RT Edition │    │
├───────────────────┼────┤
│ Callbacks         │ {} │
└───────────────────┴────┘

GB_20.7.5 GBP-BTC@kraken Round #103171 2020/12/07 15:41:05
Error: Error: General:Invalid arguments:volume
    at errorHandler (/snapshot/test/Desktop/node14/ctx/js/kraken.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

┌───────────────────┬────┐
│ ɢƱҊɃѺͳ RT Edition │    │
├───────────────────┼────┤
│ Callbacks         │ {} │
└───────────────────┴────┘
Does not work on any pairs I could try.
Title: Re: GB 20.7.5 and Kraken
Post by: sbogovac on December 08, 2020, 04:16:14 PM
Did you try to install the full 20.7.1 version (including node14) first...?
Title: Re: GB 20.7.5 and Kraken
Post by: Singman on December 09, 2020, 08:20:11 PM
If only package got a numbering scheme on them....
Do you have a method to check that ?
My node is the old one (v10.19.0), I dont see any prerequisite for Gunbot installation (on Linux).
Or maybe Gunbot include his own version of Node.js ? But how to check it ?
Title: Re: GB 20.7.5 and Kraken
Post by: Singman on December 09, 2020, 08:40:34 PM
Ok, I download v20.7.1 from Telegram, applied patch v20.7.5 and run my config. Result is not better (activated DEBUG to see if not missing important messages) :
Code: [Select]
Loading exchange - kraken
Loading data....
GBP-BTC@kraken trying to load state for GBP-BTC@kraken
GBP-BTC@kraken starting cl
GBP-BTC@kraken states loaded
GBP-BTC@kraken Awesome level 1 is working!!!
GBP-BTC@kraken checking balances
GBP-BTC@kraken checking positions
GBP-BTC@kraken calculating indicators
GBP-BTC@kraken Awesome level 3 is working!!!
GBP-BTC@kraken we got ema
GBP-BTC@kraken Awesome level 4 is working!!!
GBP-BTC@kraken we got bb
GBP-BTC@kraken we got rsi
GBP-BTC@kraken we got pair mfi
GBP-BTC@kraken we got XTrend
GBP-BTC@kraken we got smacross
GBP-BTC@kraken we got macd
GBP-BTC@kraken we got stoch
GBP-BTC@kraken Stoch buy: false
GBP-BTC@kraken Stoch sell: false
GBP-BTC@kraken we got stochRSI
GBP-BTC@kraken Stoch rsi: 0.12950832653222463
GBP-BTC@kraken we got atr
GBP-BTC@kraken we got ichimoku
GBP-BTC@kraken bull/bearish process
GBP-BTC@kraken checking history
GBP-BTC@kraken we got mfi btcusd
GBP-BTC@kraken we got forecast
GBP-BTC@kraken checking open orders
GBP-BTC@kraken canceling open orders
GBP-BTC@kraken starting pairs
GBP-BTC@kraken starting get prices loop
GBP-BTC@kraken calculated entry points

GB_20.7.5 GBP-BTC@kraken Round #1 2020/12/09 21:37:47
GBP-BTC@kraken skipped TakeProfit
GBP-BTC@kraken defined grid
GBP-BTC@kraken defined abp and available funds
GBP-BTC@kraken checked telegram alerts
GBP-BTC@kraken pre-grid
GBP-BTC@kraken end of grid parsing
GBP-BTC@kraken start strategies attempts
GBP-BTC@kraken refusing tests
GBP-BTC@kraken skipping smacross
GBP-BTC@kraken refusing MACD
GBP-BTC@kraken quote amount calculated
GBP-BTC@kraken keepsell
Error: Error: General:Invalid arguments:volume
    at errorHandler (/snapshot/test/Desktop/node14/ctx/js/kraken.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

┌───────────────────┬────┐
│ ɢՍΠßØŦ RT Edition │    │
├───────────────────┼────┤
│ Callbacks         │ {} │
└───────────────────┴────┘
Title: Re: GB 20.7.5 and Kraken
Post by: Aitor on December 14, 2020, 03:09:09 AM
Do you get the same error trying with other base coin instead of GBP-XXX ?
Did you set your Balance settingsn using GBP as base coin?
Also in the case this don't fix the issue, I would try changing the api key for a new one.