Error from the gemini-3c-2023-mar-22

Support
1

Issue Report

This gemini-3c-2023-mar-22 is still buggy about dsn and it hits the limit up to 100 and clogs my internet, this version doesn’t allow to add “dsn-max-in-connections”, “dsn-max-out-connections” and resulted in a fatal network error.

Fix Report

Please adjust it to limit 5-10 so that our routers reduce the load and do not lead to expensive network interruptions

1 Like
2

Those parameters still exist, they just changed name in https://github.com/subspace/subspace/pull/1258
As to fatal network error, can you provide logs (as text) with what you’ve seen?

1 Like
3

node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }
node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }
node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }
node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }
node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }
node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }
node_1 | 2023-03-22 17:32:42 [PrimaryChain] Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 }

4

I fixed it, because dev changed the rename
~ dsn_max_in_connections → dsn_in_connections
~ dsn_max_out_connections → dsn_out_connections

5

This is a known issue mentioned in release notes, upcoming releases of both reference implementation (separate node and farmer, already building) and CLI will fix it.

1 Like
6

Should be resolved in mar-23 and later releases

1 Like