Closed yohplala closed 3 years ago
Hi,
I have restarted a second server and am about to stop that one onto which are being issued these repeating error/warning.
I am loosely monitoring CPU and RAM activity with htop
, and since these error/warning started, the RAM has been increasing.
(from about ~600Mo to ~800Mo in more than 1 day)
I have no clear data to share, and I am suspecting that the channel is still open, and is filling in redis buffer (the http stream is likely funding from BINANCE_FUTURES), but somehow cryptofeed 'lost the handle'.
Is this possible?
(I may be completely wrong of course)
I fixed this issue in cryptofeed
Describe the bug I have started cryptostore (last version of cryptofeed and cryptostore) about 2 days ago, and since about 12 hours, I have a continuously repeating warning & error, every 1s that says:
I have other websocket connections for this server that work fine, and I have other servers in parallel, connecting to Binance for other pairs, with http and websocket which are working fine (not such warning and error repeating themsleves every 1s since 12 hours). I am surprised about this. I am about to restart the server with less pairs to see if this solves the trouble.
While I find this behavior suirprising, I think there might be a typo to correct in the warning and error.
http.6
is repeated twice inERROR : BINANCE_FUTURES.http.6.http.6
. Is this normal? (for websocket connection, it is only written once, likeERROR : BINANCE_FUTURES.ws.1
)To Reproduce Steps to reproduce the behavior:
Operating System:
Cryptofeed Version fresh from source 2 days ago.