Sebastian Kunert

I came across this issue recently and also would like to customize log output folder for native provider. Just another idea one could handle this: - specify `ZOMBIENET_LOG_DIR` env variable...

Yes, could be the same issue. Which node version are you using? What was the command to launch the node? Did you see this once or is this happening regularly?

I will take a look :eyes:

In the meantime, you could pass `sync=trace` to get more debug logs.

Problem here is just a version conflict, we need to update in polkadot too. Or switch to schnellru in the spritit of https://github.com/paritytech/substrate/issues/13802

Which state is your node in? Do you see anything interesting in the logs? I started a similar node for statemine and with external rpc kusama node and the machines...

The command I used was `polkadot-parachain -lsync=trace --sync warp --chain=statemine --database=paritydb --prometheus-external --prometheus-port=9615 --rpc-port 9944 --max-parallel-downloads=2 --runtime-cache-size=1 --execution=wasm --wasm-execution=compiled --relay-chain-rpc-urls="wss://kusama-rpc.polkadot.io" --base-path=./statemine-rpc-node`, so quite similar to yours. Version was `0.9.420-c608131f0c6`. You...

I kept the node running a bit longer with the settings from my last post, so far nothing looks suspicious. 

It is strange that the traffic still looks a bit higher than before. Just making sure, this is still with these flags? ```polkadot-parachain -lsync=trace --sync warp --chain=statemine --database=paritydb --prometheus-external --prometheus-port=9615...

> I'll get back to this issue soon and see if I can reproduce the issue. > > > ... I think it's caused by the relay-chain instance that is...