IR node starts longer than expected #1535

Open
opened 2025-12-28 17:35:46 +00:00 by sami · 2 comments
Owner

Originally created by @evgeniiz321 on GitHub (Nov 11, 2025).

In AIO IR node starts in seconds, while in neofs-testcases it takes a minute to start:

COMMAND: ./neofs-cli --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-11-11-23-48-32-205563/env_files/neofs-env-2025-11-11-23-48-33-8454031360/inner_ring_bhritstcea/ir_cli_config_tzngzjeelc.yml control healthcheck --endpoint 'localhost:49700' --ir
RETCODE: 1

STDOUT:
Error: failed to dial "localhost:49700" via gRPC: connection error: desc = "transport: error while dialing: dial tcp [::1]:49700: connect: connection refused"

STDERR:

Start / End / Elapsed	 23:48:46.963606 / 23:48:47.515637 / 0:00:00.552031

....

COMMAND: ./neofs-cli --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-11-11-23-48-32-205563/env_files/neofs-env-2025-11-11-23-48-33-8454031360/inner_ring_bhritstcea/ir_cli_config_tzngzjeelc.yml control healthcheck --endpoint 'localhost:49700' --ir
RETCODE: 1

STDOUT:
Health status: INITIALIZING_NETWORK

STDERR:

Start / End / Elapsed	 23:49:39.165310 / 23:49:39.425300 / 0:00:00.259990

Timestamps: "23:48:46.963606" -> "23:49:39.165310"

IR logs:
ir_stderr.txt
IR config:
ir_node_config_vrqilkkrlc.yml

Need to investigate the delay since it significantly slows the tests down.

Originally created by @evgeniiz321 on GitHub (Nov 11, 2025). In AIO IR node starts in seconds, while in neofs-testcases it takes a minute to start: ``` COMMAND: ./neofs-cli --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-11-11-23-48-32-205563/env_files/neofs-env-2025-11-11-23-48-33-8454031360/inner_ring_bhritstcea/ir_cli_config_tzngzjeelc.yml control healthcheck --endpoint 'localhost:49700' --ir RETCODE: 1 STDOUT: Error: failed to dial "localhost:49700" via gRPC: connection error: desc = "transport: error while dialing: dial tcp [::1]:49700: connect: connection refused" STDERR: Start / End / Elapsed 23:48:46.963606 / 23:48:47.515637 / 0:00:00.552031 .... COMMAND: ./neofs-cli --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-11-11-23-48-32-205563/env_files/neofs-env-2025-11-11-23-48-33-8454031360/inner_ring_bhritstcea/ir_cli_config_tzngzjeelc.yml control healthcheck --endpoint 'localhost:49700' --ir RETCODE: 1 STDOUT: Health status: INITIALIZING_NETWORK STDERR: Start / End / Elapsed 23:49:39.165310 / 23:49:39.425300 / 0:00:00.259990 ``` Timestamps: "23:48:46.963606" -> "23:49:39.165310" IR logs: [ir_stderr.txt](https://github.com/user-attachments/files/23488047/ir_stderr.txt) IR config: [ir_node_config_vrqilkkrlc.yml](https://github.com/user-attachments/files/23488051/ir_node_config_vrqilkkrlc.yml) Need to investigate the delay since it significantly slows the tests down.
Author
Owner

@roman-khimov commented on GitHub (Nov 12, 2025):

"not enough GAS to deploy NNS contract"

@roman-khimov commented on GitHub (Nov 12, 2025): "not enough GAS to deploy NNS contract"
Author
Owner

@roman-khimov commented on GitHub (Nov 20, 2025):

This can be solved with another config extension. NeoGo allows to pass a transaction for the genesis block, so just like we have set_roles_in_genesis: bool we can also have a send_gas_to_cn_in_genesis: int which would create a transaction pushing specified amount of GAS to each CN (or committee?) and pass it into NeoGo genesis settings. By default it's 0 and transaction is created. But pushing some 10K GAS will make nodes be instantly available to perform any actions required for deploy.

@roman-khimov commented on GitHub (Nov 20, 2025): This can be solved with another config extension. NeoGo allows to pass a transaction for the genesis block, so just like we have `set_roles_in_genesis: bool` we can also have a `send_gas_to_cn_in_genesis: int` which would create a transaction pushing specified amount of GAS to each CN (or committee?) and pass it into NeoGo genesis settings. By default it's 0 and transaction is created. But pushing some 10K GAS will make nodes be instantly available to perform any actions required for deploy.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1535
No description provided.