Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to adjust timeout again (Poloniex API asking for 130sec timeout) #40

Closed
Shoananas opened this issue May 24, 2017 · 5 comments
Closed
Labels

Comments

@Shoananas
Copy link

Hello,

Today I've seen a lot of logs like this:
notice: returnActiveLoans: Poloniex error 429: Too Many Requests. This IP has been banned for 2 minutes. Please adjust your timeout to 130 seconds.

So I guess Poloniex changed their timeout policy again and the bot needs to be adjusted to this new policy.
Other than that, the bot has been working really nice for more than a week without any interruption for me!

So, thank you again for your hard work!

@dutu
Copy link
Owner

dutu commented May 24, 2017

@Shoananas, I've noticed the error has occurred a couple of times since yesterday.
I can increase the timeout, although I'm not sure it will resolve the issue since I haven't see a timeout error prior this 429 error code.,

Can you confirm if in your case the error 492 is preceded by a timeout error? Thanks

@Shoananas
Copy link
Author

Shoananas commented May 24, 2017

Nope I didn't see the timeout error, the first error 429 happens like this:
notice: returnOpenLoanOffers: Poloniex error 429: Too Many Requests. This IP has been banned for 2 minutes. Please adjust your timeout to 130 seconds.

and then:
notice: returnActiveLoans: Poloniex error 429: Too Many Requests. This IP has been banned for 2 minutes. Please adjust your timeout to 130 seconds.

all the way untill I restarted the bot (after 5 min pause)

@dutu
Copy link
Owner

dutu commented May 25, 2017

@Shoananas , since there was no timeout error prior the error code 429, it's not clear that increasing the timeout value will solve the issue.
The occurrence of this situation seems to be very infrequent. We should keep an eye on it and see if we can come up with something more likely to solve it.

BTW, you mentioned that the issue diapered after restating the bot. Are you using it on Heroku? (as the restart may have given you a new IP address)

@Shoananas
Copy link
Author

Yes, I am using it on Heroku. I stopped the bot (maintenance mode ON) for 5min and then disabled the maintenance mode.

I'll keep you informed if I run in another 429 error.

@dutu
Copy link
Owner

dutu commented May 30, 2017

@Shoananas, these errors seem to be quite infrequent, also the reason why Poloniex server is responding with this error code is not clear (although the error message suggests a timeout issue, timeouts have not been seen in conjunction with this error).
I will not do any code modification at this stage.

@dutu dutu added the wontfix label May 30, 2017
@dutu dutu closed this as completed Jun 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants