-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relay chain subsytem error #2175
Comments
@bensacc is it still appearing after restarting ? |
@crystalin It is, same as the original occurrence, after a few hours |
Maybe I'm a bit confused as to whether I should be running port 9944 or 9945. I was using 9944, but have tried switching to 9945, and so far it's continuing to sync, I guess we'll see in an hour or so. |
I see a number of these in the logs as well, following the restart, but maybe unrelated: cannot query the runtime API version: UnknownBlock: State already discarded for 0x64bbaf57336d698c00eaff6d6847631ca47ba797276590b8033467f1780daebb they don't seem to be causing any larger issues |
@bkchr this is what I mentioned before, we also experienced this issue (not the "Signal channel is terminated and empty" but the "State already discarded for") few times on our side :/ |
Should be fixed by: paritytech/polkadot-sdk#793 For the other issue, please report here: paritytech/polkadot#6759 |
Seeing similar issue here. Unable to perform full sync ./moonbeam --version
|
It seems like it is still the problem... I cannot sync new node even from a snapshot. It syncs for an hour or so and then this happens, eventually crashing the container. Running v0.31.1. Last logs, before it continues to spam the same line:
|
@Szymongib We are still investigating the sync issue. The error message is less problematic |
what I am getting from log is,
@Szymongib where is the snapshot you use? is it public for usage? I want to have a try |
@chengjiao I have used p2p snapshot https://p2p.org/snapshot/moonbeam What ended up working for me was setting up both Moonbeam and Polkadot data from snapshot. |
Attempting to spin up a new Moonriver node using purestake/moonbeam:v0.30.0, I have uit running in a docker container and after several hours of seemingly successfull syncing I'm receiving these errors:
2023-03-20 22:25:08 [Relaychain] ⚙️ Syncing 153.6 bps, target=#17126217 (40 peers), best: #7143039 (0xfc86…89fd), finalized #7142912 (0xa888…2121), ⬇ 519.2kiB/s ⬆ 247.2kiB/s
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="candidate-validation-subsystem" err=FromOrigin { origin: "candidate-validation", source: Generated(Context("Signal channel is terminated and empty.")) }
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="approval-voting-subsystem" err=FromOrigin { origin: "approval-voting", source: Generated(Context("Signal channel is terminated and empty.")) }
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="chain-api-subsystem" err=FromOrigin { origin: "chain-api", source: Generated(Context("Signal channel is terminated and empty.")) }
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="runtime-api-subsystem" err=Generated(Context("Signal channel is terminated and empty."))
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="bitfield-signing-subsystem" err=FromOrigin { origin: "bitfield-signing", source: Generated(Context("Signal channel is terminated and empty.")) }
2023-03-20 22:25:12 [Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="statement-distribution-subsystem" err=FromOrigin { origin: "statement-distribution", source: SubsystemReceive(Generated(Context("Signal channel is terminated and empty."))) }
2023-03-20 22:25:12 [Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
2023-03-20 22:25:12 [Relaychain] subsystem exited with error subsystem="availability-recovery-subsystem" err=FromOrigin { origin: "availability-recovery", source: Generated(Context("Signal channel is terminated and empty.")) }
2023-03-20 22:25:12 [Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
2023-03-20 22:25:12 [Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
2023-03-20 22:25:12 [Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
2023-03-20 22:25:12 [Relaychain] error receiving message from subsystem context: Generated(Context("Signal channel is terminated and empty.")) err=Generated(Context("Signal channel is terminated and empty."))
2023-03-20 22:25:12 [Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))
after which "[Relaychain] error=Subsystem(Generated(Context("Signal channel is terminated and empty.")))" is repeated until I kill it
docker container config:
docker run --restart=always -p 9944 -p 9944:9944 -p 30333 -p 30333:30333 -d -v "/var/lib/moonriver-data:/data" -u$(id -u $ {USER}):$(id -g ${USER}) --name="moonriver-primary" purestake/moonbeam:v0.30.0 --base-path=/data --chain moonriver --name="moonriver-primary" --execution wasm --wasm-execution compiled --state-pruning archive --trie-cache-size 0 --ws-port 9944 --ws-max-connections 100 --db-cache 16000 -- --name="moonriver-primary (Embedded Relay)
(note: "-id -u ${USER}", is just getting formatted weird in the text above)
anyone have any idea what could be causing this?? thanks so much in advance...
The text was updated successfully, but these errors were encountered: