mikekonan / exchange-proxy

exchange-proxy
GNU General Public License v3.0
110 stars 32 forks source link

Any solution for Outdated history ? #36

Closed PeetCrypto closed 2 years ago

PeetCrypto commented 2 years ago

freqtrade-proxy does not have Outdated history. exchange-proxy with more the 1 freqtrade bots has continue Outdated history

mikekonan commented 2 years ago

It's quite strange to find, so need to be sure that these candles have really existed. Need to compare the proxied response with the non-proxied one. Also, there may be some issues with your host and time zone(have to be UTC).

anuith commented 2 years ago

I have this issue too. The timezone is already UTC in both host and container.

It seems to happen with the large pairlist. I use one from NostalgiaForInfinity and it happens. It uses VolumePairlist at 80 pairs with filters. Errors logged in less than 5 minutes after start. But when I set the number to 20 and no errors found in 15-20 mins.

docker stats doesn't show high resource usage. But it's the same host as freqtrade. I don't know if it causes any effect.

mikekonan commented 2 years ago

"Errors logged in less than 5 minutes after the start." Please, provide proxy errors on that. Where is your VM? Is the connection is stable?

anuith commented 2 years ago

How ridiculous it doesn't happen when I tried to reproduce to get the errors.

I kept it running for 15 minutes and freqtrade logs started to show errors saying a pair is outdated with Last tick is 15 minutes old and proxy logs only shows level=info lines and the last line's timestamp is about 40 minutes ago.

But this time it happened only about 3 minutes with only one pair and seems to disappear for now. But I doubt it will happen again later.

mikekonan commented 2 years ago

use verbose 1

PeetCrypto commented 2 years ago

What would you like to see @mikekonan in the logging.

2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair RUNE/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair UOS/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair ALICE/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair CWAR/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair ENS/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair CELO/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair SENSO/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair SRM/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair PLU/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair CGG/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair WHALE/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair CWS/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair POWR/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair TOMO/USDT. Last tick is 18 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair BOND/USDT. Last tick is 18 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair PMON/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair MONI/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair DIA/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair KMD/USDT. Last tick is 23 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair TRB/USDT. Last tick is 1258 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair PDEX/USDT. Last tick is 18 minutes old 2022-02-05 08:58:14 - freqtrade.strategy.interface - WARNING - Outdated history for pair LON/USDT. Last tick is 1258 minutes old

other bot 2022-02-05 08:58:07 - freqtrade.strategy.interface - WARNING - Outdated history for pair REVV/USDT. Last tick is 7 minutes old 2022-02-05 08:58:12 - freqtrade.strategy.interface - WARNING - Outdated history for pair REVV/USDT. Last tick is 7 minutes old proxy.txt

PeetCrypto commented 2 years ago

proxy.txt is the logging with verbose 1

PeetCrypto commented 2 years ago

24207b92f355290f88238f7a3eba019aef83db4e5325557dfcd09d0bc3deb63b-json.log

This is the complete logging file

PeetCrypto commented 2 years ago

@mikekonan can you see something wrong in the log file?

lsalsich commented 2 years ago

I also get this error when first starting or restarting either proxy or a strategy. But, it seems to work itself out pretty quickly (for me). @PeetCrypto - do your errors persist for long periods of time, or just periodically?

PeetCrypto commented 2 years ago

I also get this error when first starting or restarting either proxy or a strategy. But, it seems to work itself out pretty quickly (for me). @PeetCrypto - do your errors persist for long periods of time, or just periodically?

PeetCrypto commented 2 years ago

I also get this error when first starting or restarting either proxy or a strategy. But, it seems to work itself out pretty quickly (for me). @PeetCrypto - do your errors persist for long periods of time, or just periodically?

It is working as a proxy at my side. The error the api of kucoin gives are shown at the proxy logs aswell. And i am not sure the outdated errors are giving problems even when running without a proxy