Closed jonathanudd closed 2 weeks ago
It has not crashed for 24 hours now. Could it be related to how far it has synced? It's starting to get close to fully synced now.
I can also see that the CPU usage is lower the last 24 hours. Could the crashes occur if the process gets limited CPU resources? Are there any recommended hardware specs to run the chain?
Thank you for the report @jonathanudd . Point number 5 indicates that the problem likely originates upstream, would you be able to submit the report to substrate?
Thank you for the report @jonathanudd . Point number 5 indicates that the problem likely originates upstream, would you be able to submit the report to substrate?
@sander2 They said that those problems should be fixed in later versions of Polkadot. See link to issue above.
Describe the bug I have deployed a Kintsugi RPC node which is still not fully synced. It syncs for a while and then the process crashes and when it's restarted it hangs for a long time before starting to sync again.
To Reproduce Steps to reproduce the behavior:
--chain=kintsugi --execution wasm --wasm-execution=compiled --rpc-methods=safe --state-pruning=archive --ws-external --ws-port=9966 --ws-max-connections=1000 --rpc-external --rpc-port=9933 --rpc-cors=all --prometheus-external
[Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
Expected behavior The process not crashing and it starting to sync quicker after a crash.
Version / Commit (e.g. 1.0.0): I started out with version
version 1.20.0-47bfef0d8b7
to avoid the issue mentioned here https://github.com/interlay/interbtc/issues/978 Then I upgraded toversion 1.23.2-33fabb23fae
and thenversion 1.24.0-rc5-76deccd2391
today.Additional notes The node is almost in sync now. I could provide the whole log file from start until now but it's 262MB and cannot be attached here.