Closed xiandong79 closed 1 year ago
I notice that other 3 coders reported the same issues, and the 3 issues are closed with answers.
No people to login the server and execute "sudo kill candle_runner_1h" , or something else.
@xubinlaile @leonwang893 @yancong001
Yes, I had this problem, but I haven't had much of it since I ran it in the background with “nohup”.
@yancong001
i still face this bug while I use
nohup python candle_runner_1h_futures.py > $PWD/logs/candles_1h.out 2>&1 &
2023-06-05 06:41:39,769 : INFO : BINANCE_FUTURES: starting backend task CandlesPostgres with multiprocessing=False
2023-06-05 06:57:39,808 : WARNING : BINANCE_FUTURES.ws.2: received no messages within timeout, restarting connection
2023-06-05 06:57:49,812 : INFO : BINANCE_FUTURES.ws.2: closed connection 'WebSocketClientProtocol'
2023-06-05 08:56:04,109 : INFO : FH: System Exit received - shutting down
2023-06-05 08:56:04,109 : INFO : FH: shutdown connections handlers in feeds
after another run with 2 hours, it curshed
I try to set
fh.run(install_signal_handlers=False)
I do not know where the SystemExit comes
The cryptofeed instance stopped without any Error msgs
just like #893 , #858 , #889
I got
the script I use is what you write 2 years ago.
named candle_runner_1h_futures.py
in this server, I also run the candle_runner.py BINANCE and ti_runner.py, all the scripts are written via you 2 years ago.
I just start the script in Ubuntu server, and the "candle_runner" and "ti_runner" running well for 1 month+, while "candle_runner_1h" stop automatically.