z_W
December 20, 2023, 7:27am
1
When my node connects to around 80 or more farms, the BPS becomes zero. If I turn off all the farms, it returns to normal. Why does this happen?
Hard to say, this is certainly not an expected usage of the node, but I also don’t see why would it cause issues.
If you can provide all logs (as text) from both node and all farmers, there should be something there indicating an issue.
I see block 729582 actually contains segment headers, which is something that I already noticed causes spikes on the network and will debug it. I don’t think it is necessarily related to the number of farms you have connected.
z_W
December 20, 2023, 5:06pm
3
What parameters do I need to start node with to get more detailed logs?
Even default log level should be quite telling, but I think this particular situation is something I need to debug and fix, then you’ll just upgrade and the issue should go away.
z_W
December 21, 2023, 5:40am
5
OK, I will provide you with detailed logs the next time the node is disconnected.
z_W
December 21, 2023, 4:16pm
6
CLI parameter `--execution` has no effect anymore and will be removed in the future!
2023-12-21T05:13:40.864694Z Subspace
2023-12-21T05:13:40.864913Z ✌️ version 0.1.0-309a07ddae9
2023-12-21T05:13:40.864940Z ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-12-21T05:13:40.864941Z 📋 Chain specification: Subspace Gemini 3g
2023-12-21T05:13:40.864943Z 🏷 Node name: ooplay-43100
2023-12-21T05:13:40.864944Z 👤 Role: AUTHORITY
2023-12-21T05:13:40.864949Z 💾 Database: ParityDb at /root/.local/share/subspace-node/chains/subspace_gemini_3g/paritydb/full
2023-12-21T05:13:45.500346Z [Consensus] DSN instance configured. allow_non_global_addresses_in_dht=false peer_id=12D3KooWQLFsNFte3qkp8mmchStx8reCxqmtBuCeCHpgPUqfdiA9 protocol_version=/subspace/2/418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b
2023-12-21T05:13:45.500886Z [Consensus] local_peer_id=12D3KooWQLFsNFte3qkp8mmchStx8reCxqmtBuCeCHpgPUqfdiA9
2023-12-21T05:13:45.500968Z [Consensus] Subspace networking initialized: Node ID is 12D3KooWQLFsNFte3qkp8mmchStx8reCxqmtBuCeCHpgPUqfdiA9
2023-12-21T05:13:45.501414Z [Consensus] relay::consensus block server: starting
2023-12-21T05:13:45.501544Z [Consensus] DSN listening on /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWQLFsNFte3qkp8mmchStx8reCxqmtBuCeCHpgPUqfdiA9
2023-12-21T05:13:45.501634Z [Consensus] 🏷 Local node identity is: 12D3KooWQLFsNFte3qkp8mmchStx8reCxqmtBuCeCHpgPUqfdiA9
2023-12-21T05:13:45.501773Z [Consensus] DSN listening on /ip4/43.248.98.100/tcp/30333/p2p/12D3KooWQLFsNFte3qkp8mmchStx8reCxqmtBuCeCHpgPUqfdiA9
2023-12-21T05:13:45.502320Z [Consensus] Can't listen on /ip4/0.0.0.0/tcp/30333 because: Other(Custom { kind: Other, error: Custom { kind: Other, error: Other(Left(Left(Left(Left(Right(Transport(Os { code: 98, kind: AddrInUse, message: "Address already in use" }))))))) } })
2023-12-21T05:13:45.507323Z [Consensus] Resuming archiver from last archived block last_archived_block_number=729481
2023-12-21T05:13:45.507393Z [Consensus] Archiving already produced blocks 729482..=740646
2023-12-21T05:13:50.967835Z [Consensus] 🧑🌾 Starting Subspace Authorship worker
2023-12-21T05:13:50.968058Z [Consensus] Metrics server started. endpoints=[127.0.0.1:9615]
show original
This is the first node that was started entirely according to the official default parameters. The BPS of this process became 0 around 2023-12-21T08:49:15.119317Z.
2023-12-21T08:49:15.119317Z [Consensus] 💤 Idle (49 peers), best: #747868 (0x7b02…48b7), finalized #669423 (0x10a3…98d3), ⬇ 7.9kiB/s ⬆ 1.6kiB/s
2023-12-21T08:49:20.119846Z [Consensus] ⚙️ Preparing 0.0 bps, target=#747874 (48 peers), best: #747868 (0x7b02…48b7), finalized #669423 (0x10a3…98d3), ⬇ 15.7kiB/s ⬆ 2.1kiB/s
CLI parameter `--execution` has no effect anymore and will be removed in the future!
2023-12-21T05:14:24.736701Z Subspace
2023-12-21T05:14:24.736900Z ✌️ version 0.1.0-309a07ddae9
2023-12-21T05:14:24.736928Z ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-12-21T05:14:24.736929Z 📋 Chain specification: Subspace Gemini 3g
2023-12-21T05:14:24.736931Z 🏷 Node name: ooplay431002
2023-12-21T05:14:24.736936Z 👤 Role: AUTHORITY
2023-12-21T05:14:24.736940Z 💾 Database: ParityDb at /root/sub/chains/subspace_gemini_3g/paritydb/full
2023-12-21T05:14:26.217826Z [Consensus] DSN instance configured. allow_non_global_addresses_in_dht=false peer_id=12D3KooWGgph6TvYGEAhivjszaSZSxjMB866aY3GJu4d6nMy2DDU protocol_version=/subspace/2/418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b
2023-12-21T05:14:26.218345Z [Consensus] local_peer_id=12D3KooWGgph6TvYGEAhivjszaSZSxjMB866aY3GJu4d6nMy2DDU
2023-12-21T05:14:26.218454Z [Consensus] Subspace networking initialized: Node ID is 12D3KooWGgph6TvYGEAhivjszaSZSxjMB866aY3GJu4d6nMy2DDU
2023-12-21T05:14:26.218861Z [Consensus] relay::consensus block server: starting
2023-12-21T05:14:26.219038Z [Consensus] DSN listening on /ip4/127.0.0.1/tcp/40433/p2p/12D3KooWGgph6TvYGEAhivjszaSZSxjMB866aY3GJu4d6nMy2DDU
2023-12-21T05:14:26.219139Z [Consensus] 🏷 Local node identity is: 12D3KooWGgph6TvYGEAhivjszaSZSxjMB866aY3GJu4d6nMy2DDU
2023-12-21T05:14:26.219222Z [Consensus] DSN listening on /ip4/43.248.98.100/tcp/40433/p2p/12D3KooWGgph6TvYGEAhivjszaSZSxjMB866aY3GJu4d6nMy2DDU
2023-12-21T05:14:26.221392Z [Consensus] Resuming archiver from last archived block last_archived_block_number=729481
2023-12-21T05:14:26.221450Z [Consensus] Archiving already produced blocks 729482..=740646
2023-12-21T05:14:28.135799Z [Consensus] 🧑🌾 Starting Subspace Authorship worker
2023-12-21T05:14:28.136038Z [Consensus] Failed to start metrics server. Falling back to the random port... error=Os { code: 98, kind: AddrInUse, message: "Address already in use" }
2023-12-21T05:14:28.136131Z [Consensus] Metrics server started. endpoints=[127.0.0.1:44611]
show original
This is a node where I increased the number of connections.
Did farmers disconnected and restarted?dec-22 release addresses this issue and I think you should not see 0 bps sync on segment archiving or hit RPC issues.
Please upgade and let me know how it works over next few days.
z_W
December 23, 2023, 8:37am
8
It has been running stably for 8 hours now.
1 Like
Give it another two days to make sure it went through a few archived segments without major disruption.
