You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed the electrumx of the latest master branch. Thank you very much for the memory leak problem that has been solved after testing, but I now encounter a new problem. I try to kill the electrumx service. When I start it again, it will get stuck in a position and cannot continue. , And it will be stuck to the position of the log below after restarting many times
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:DB:coin: Bitcoin
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:DB:network: mainnet
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:DB:height: 654,158
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:DB:tip: 0000000000000000000cec4112e9b0baa1f22f5ae1771cc55b42d63f57737d02
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:DB:tx count: 580,836,867
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:DB:flushing DB cache at 1,200 MB
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:History:history DB version: 1
Oct 28 00:52:48 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:History:flush count: 13,156
Oct 28 00:52:49 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:Prefetcher:catching up to daemon height 654,467 (309 blocks behind)
Oct 28 00:52:49 ubuntu-PowerEdge-R740 electrumx_server[41195]: INFO:SessionManager:RPC server listening on localhost:8000
The text was updated successfully, but these errors were encountered:
I installed the electrumx of the latest master branch. Thank you very much for the memory leak problem that has been solved after testing, but I now encounter a new problem. I try to kill the electrumx service. When I start it again, it will get stuck in a position and cannot continue. , And it will be stuck to the position of the log below after restarting many times
The text was updated successfully, but these errors were encountered: