docker container stopped with issue about moonbeam

[tgmichel]

Please update the client to latest release.

[Ttk69]

Please update the client to latest release.

speech about v. 0.9.6? it was stopped on 0.9.6, i've tried to restart it and it was stopped with this problem. then i used v.0.9.4 and got the same. now i'm trying 0.9.1 but don't think that will have success

[JoshOrndorff]

speech about v. 0.9.6? it was stopped on 0.9.6, i've tried to restart it and it was stopped with this problem

Yes, please use Moonbeam 0.9.6. The logs that you shared say the node was version 0.9.1

2021-07-28 12:31:36 Moonbeam Parachain Collator    
2021-07-28 12:31:36 ✌️  version 0.9.1-78d1dae-x86_64-linux-gnu 

[Ttk69]

ok. i removed local docker image v0.9.6 and start it again. and after an one or two hours it freezed.
moonbeam issue.txt

[JoshOrndorff]

I confirm you are using the correct node now. I'm surprised you still got this error. Does your syncing continue if you restart the node at this point? (It's a bug either way, but I'm curious.)

[crystalin]

@Ttk69 thank you for the report, you error on v0.9.6 is already known and pending some solution at the moment.
See paritytech/polkadot#3242
I think restarting the node should do the trick for this time

[Ttk69]

I confirm you are using the correct node now. I'm surprised you still got this error. Does your syncing continue if you restart the node at this point? (It's a bug either way, but I'm curious.)

after restart syncing continuing during may be 10 000 blocks and stops. some times dockes container goes down

upd. after next restart node completed syncing and now it' fine. watching

[crystalin]

@Ttk69 , what machine specs are you using ?

[Ttk69]

@Ttk69 , what machine specs are you using ?

4 vCPU (AMD EPYC 7282) /8 RAM /200 SSD, 100/200 Mbit/s internet channel

[purestakeoskar]

Experiencing the same issue, same block #74522:
block_74522_sync_issue.txt

Node version: 0.9.6-e9ac5d1-x86_64-linux-gnu

Content of the block can be found here: https://moonbase.subscan.io/block/74522

A workaround / fix for this seems to be to purge and resync the parachain only.