Curu

> Hi @Curu24, > > It seems like you only can specify one URL as the relay chain. If you want to use `ws://194.163.154.254:9944` then you can not use the...

> Have you tried to specify only one flag but several values? Something like: > > ```shell > --relay-chain-rpc-url ws://57.129.1.46:9944,ws://194.163.154.254:9944 > ``` > > The doc for this flag found...

But it doesn't work even with single argument.

this gives following error: `error: Found argument '--relay-chain-rpc-urls' which wasn't expected, or isn't valid in this context` But please note, it's not my point to make it work with 2...

it's 0.10.26, so up until today it was the recent one

> [@Curu24](https://github.com/Curu24) Please provide full logs, this logs are just the symptom not the cause, they just tell you that your validators is not properly connected to other validators, missing...

@lexnv there are no custom scripts involved. the node is running via standard systemd service Also as I wrote in the end, the error "failed to register opened substream to...

Similar issues are happening on one of our Kusama validators as well. Here it is without the "failed to register opened substream to protocol" error though. An example from the...

@lexnv yes, as I mentioned there were no "failed to register opened substream" in the kusama validator logs ``` cat /proc/sys/fs/file-max 9223372036854775807 cat /proc/sys/fs/file-nr 2016 0 9223372036854775807 ``` this is...

substrate_unbounded_channel_size substrate_sync_peers substrate_sub_libp2p_incoming_connections_total substrate_sub_libp2p_peers_total the incident was basically from 2025-11-07 ~11:30:00 till 2025-11-08 ~17:18:00 with periods running ok. let me know if the metric window is wide enough