Closed plusha74 closed 7 years ago
Looks like the typical Poloniex-Timeout-Issues. The Bot is working, these Errors are normal for Poloniex.
I setup a telegram notification once an hour about my loans to control the work of the bot. today he stopped sending notifications. i check status and he is empty (bot not working) Pay attention to the last errors time. Every 5 minutes the bot trying to connect again and again and can't do this
did you increase your timeout value in config?
i did it right now. i set the timeout value to 60 sec, and i got:
Welcome to Poloniex Lending Bot
2017-07-08 22:53:41 Error: <urlopen error timed out> Requesting returnActiveLoans
Timed out, will retry in 60.0sec
Error during summary notification: <urlopen error timed out> Requesting returnActiveLoans
2017-07-08 22:55:42 Error: <urlopen error timed out> Requesting returnActiveLoans
Timed out, will retry in 60.0sec
Error during new loans notification: <urlopen error timed out> Requesting returnActiveLoans
try 180 seconds
180
Welcome to Poloniex Lending Bot
2017-07-08 23:02:59 Error: <urlopen error [Errno 104] Connection reset by peer> Requesting returnActiveLoans
Caught <urlopen error [Errno 104] Connection reset by peer> Requesting returnActiveLoans from Poloniex, ignoring.
Error during summary notification: <urlopen error timed out> Requesting returnActiveLoans
No connection, status empty, telegram are silent
today I used the default settings from default.cfg.example and generated new API key without all of permits.
2017-07-09 05:14:45 Error: <urlopen error timed out> Requesting returnActiveLoans
Timed out, will retry in 60.0sec
2017-07-09 05:16:16 Error: <urlopen error timed out> Requesting returnActiveLoans
Timed out, will retry in 60.0sec
2017-07-09 05:17:49 Error: <urlopen error timed out> Requesting returnActiveLoans
Timed out, will retry in 60.0sec
2017-07-09 05:19:19 Error: <urlopen error timed out> Requesting returnActiveLoans
Timed out, will retry in 60.0sec
Later I'll try to reinstall the bot
Mine has stopped working too. Please let me know if you find a fix.
maybe the ip of pythonanywhere was banned or there is a dns-issue
tamaskan, very likely the problem is not with the user. today log: <100 errors (timeout) from 8:00 to 14:00 and 0 any error after 14:00. i just restarted the bot right now and he works without errors + sends telegram notifications. Any timeout errors are now missing.
CrossyFTW, Is your problem solved?
Sort of. I get the following when I try to run it via Pythonanywhere:
2017-07-09 23:04:52 Error: HTTP Error 502: Bad Gateway Requesting returnActiveLoans. Poloniex reports: ''
Caught HTTP Error 502: Bad Gateway Requesting returnActiveLoans. Poloniex reports: '' from Poloniex, ignoring.
But still seems to be semi-functional aside from that. Hasn't placed a loan yet, but rates are low (ie: below thresholds).
Errors seem to have stopped. Huzzah.
I didn't do anything.
Error is now intermittent, but bot seems functional.
The bot fails and then retries later. i.e. if you only see these errors from time to time this doesn't mean the bot won't manage to place orders.
Just making sure, you updated the 'timeout' in config, right? mine btw is ~90sec.
Yeah I suspected as much. Thanks for your work on this, btw!
i placed bot on pythonanywhere. he worked for 3 days with non-critical different errors, but today he finally stopped. I have a lot of errors (timeout), and today i got [Errno 104].
I killed process, killed console, restarted it and received:
how to start bot again? what am I doing wrong? Thanks for doing this! Sorry, my English is not so good.