Gunthy
GUNBOT: The automatic profit generator => Technical Support & Development => Topic started by: AlfonseX on June 08, 2017, 12:30:51 PM
-
Hello, since 2 days I have only error 422 whith gunbot v3.x (v3.2 nor v3.3 whith patches). All my pairs don't works! I can't understand why. Is there anybody have the same issue?
I have obliged to increase bot fail delay to avoid error 429.
I can upload err.txt or anything if wanted.
Thanks.
-
me too... did you try to stop the bot and start it again? you can even try to start the couples 1 by 1. I have only 5 couples but am experiencing a lot of 422 errors too. restarting the bot and increasing the delay helped a little. I'm using 59 sec bot deelay and 37 for fail, i like to use prime numbers to mitigate errors.
edit: also had 429s when restarting the bot, just waited a few minutes an tried again
-
Before I ran gunbot with 40 pairs on Polo, with no problem. I tryed with only 1 pair, and I have the same issue. Yes, I stopped gunbot, many times, wait and restart. Same thing.
bot delay is 80sec, and I set fail delay to 80sec too (was 40sec), to avoid 429.
I wrote to Gunthar, and he said it's a polo overload, not my side :<
Thanks.
-
Same problem over here :( Bot seems unusable ATM, have tried restarting the pairs multiple times & I get this error most of the times "Unhandled rejection Error: statusCode 422"
-
I too have lots of 422 errors.
Here is a screenshot of 15 pairs currently running, most of which show this error.
Despite this, some trades are happening.
Question 1: Are these errors adversely affecting my buying and selling?
Question 2: Is there anything we can do about them?
-
i am having the same troubles -_-
-
same here ...
only 422 error without a single trade ..
-
I've upgraded to 3.3.2 under Linux (text only) and since I've many many errors 422 on all my pairs (only 8 at this time).
Trace :
+Unhandled rejection Error: statusCode 422
at Object.console./snapshot/Users/Enrico/Desktop/xBot_v2.9.3/poloniex.js.module.exports.Market.getLastBuyRate.poloniex.returnTradeHistory [as callback] (evalmachine.<anonymous>:0:0)
at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:134:7)
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)
The bot is very slow, sometimes it could catch the market, sometimes it can"t.
Should I renew my API key and send it to Gunthar ?
-
Everyone is having 422 error problems....haven't seen anyone that's found a workable solution yet
-
I am getting error 422 more then actual responses now :-[
Only trading on 3-6 pairs at a time. Not sure what can be done but its a real problem.
-
The problem is Poloniex, not GB not us. I don't know what happens, but Polo lacks, even the web interface is slow (and bug sometime). :<
-
The problem is Poloniex, not GB not us. I don't know what happens, but Polo lacks, even the web interface is slow (and bug sometime). :<
That is what I was afraid of :-[
Any idea if Bittrex or Kraken is any more stable? I may need to transfer...
-
But if it's a Poloniex problem, why is it only happening AFTER people upgrade to 3.3?
I too am getting 422 errors on nearly all my pairs when running them. It's pretty bad.
-
i think that the 3.3.2 not work very good ?
till yesterday i have use the 3.2 on polo and it works well for a while......
since yesterday i try the 3.3 and have errors, but it make some trades........
on kraken i get eroors with both
-
why is it only happening AFTER people upgrade to 3.3?
Coincidence?
Any idea if Bittrex or Kraken is any more stable?
GB on Bittrex works like a charm, even with delay=20s on a big bunch of pair!
i think that the 3.3.2 not work very good ?
till yesterday i have use the 3.2 on polo and it works well for a while......
since yesterday i try the 3.3 and have errors, but it make some trades........
on kraken i get eroors with both
Please report on the bug/issue tracker: https://gunthy.org/index.php?topic=353.0
-
Its not coincidence, people who are 3 or 3.3.2 are still getting 422 , its purely because recently polo is getting bigger and bigger and bigger yet they fail to upgrade their servers or even if they did it was not enough.
-
I am also getting a mix bag of 422 errors. Does someone know what the following part of the error code is about?
C\snapshot\Users\Enrico\Desktop\xbot_v2.9.3\poloniex.js
-
Any solutions? This is getting ridiculous.
-
Please wait the next version of GB. Gunthar works hard to solve this issue.
Else, you can you proxy https://gunthy.org/index.php?topic=491.msg2525#msg2525
-
Please wait the next version of GB. Gunthar works hard to solve this issue.
Else, you can you proxy https://gunthy.org/index.php?topic=491.msg2525#msg2525
for sure we will wait for gunthar's solution to this!!!
... but Proxy solution you propose costs even more from the gunbot. :-\
-
See https://gunthy.org/index.php?topic=311.0 it may be profitable.