SimonKraus
SimonKraus
For sure @crystalin !! ``` ExecStart=/var/lib/moonbeam-data/moonbeam \ --validator \ --port 30333 \ --rpc-port 9933 \ --ws-port 9944 \ --execution wasm \ --wasm-execution compiled \ --db-cache 32000 \ --database paritydb \...
For the hardware specs: It's an 2386G with 64gig RAM, NVME and 1gig dedicated uplink.
As discussed in https://github.com/paritytech/polkadot/issues/7259 I'm providing the startup logs and first few minutes of grandpa trace. The node is generating approx 100k lines of log per minute with `-lgrandpa=trace`. The...
(parachain running with `--execution wasm ` )
((Error always pops up before the collator proposes a block))
//bump we also got our mocha bridge node stuck while seeing the same messages in the logs. restart resolved it tho.
Hey @renaynay - we're seeing it in different combinations (own rpc node on mainnet, public one on testnet)
No , sorry - of course not. I meant we are seeing this on our Mainnet bridge, which uses a dedicated self-hosted RPC, as well as on our Mocha bridge,...
We are on `0.13.7` Sorry for the late reply