iroha icon indicating copy to clipboard operation
iroha copied to clipboard

[BUG] Failed to finalize configuration public and private keys using docker-compose

Open timofeevmd opened this issue 1 year ago • 0 comments

OS and Environment

MacOS ventura 13.3, DockerHub

GIT commit hash

4de547fd

Minimum working example / Steps to reproduce

docker-compose -f docker-compose.local.yml up -d

I got the same problem when I tried docker-compose -f docker-compose.yml up -d

logs of any peers

Error: Failed to finalize configuration

Caused by:
    Please add `PUBLIC_KEY and PRIVATE_KEY` to the configuration

Location:
    cli/src/lib.rs:572:10

Actual result

Error: failed to load configuration

Caused by:
    The network consists from this one peer only (no `sumeragi.trusted_peers` provided). Since `--submit-genesis` is not set, there is no way to receive the genesis block. Either provide the genesis by setting `--submit-genesis` argument, `genesis.private_key`, and `genesis.file` configuration parameters, or increase the number of trusted peers in the network using `sumeragi.trusted_peers` configuration parameter.

Location:
    /iroha/config/src/parameters/actual.rs:63:22

Expected result

build successful

Logs in JSON format

Log contents GENESIS
2024-02-27T07:11:37.785951Z  INFO iroha: Hyperledgerいろは2にようこそ!(translation) Welcome to Hyperledger Iroha! version="2.0.0-pre-rc.20" git_commit_sha="4de547fd"
2024-02-27T07:11:37.793032Z  INFO init:start{listen_addr=0.0.0.0:1337}: iroha_p2p::network: Network bound to listener
2024-02-27T07:11:37.805008Z  INFO init:kura_init: iroha_core::kura: Kura init complete mode=Strict block_count=0
2024-02-27T07:11:37.805483Z  WARN init: iroha: Failed to load wsv from snapshot, creating empty wsv error=Failed reading/writing "./storage/snapshot/snapshot.data" from disk
2024-02-27T07:11:37.817786Z  WARN init: iroha: Telemetry not started
2024-02-27T07:11:37.822878Z  INFO iroha_core::sumeragi: Sumeragi has finished loading blocks and setting up the WSV
2024-02-27T07:11:37.845179Z  INFO iroha: Starting Iroha
2024-02-27T07:11:39.977745Z  INFO request{method=GET path=/status/blocks version=HTTP/1.1 remote.addr=127.0.0.1:34202}: warp::filters::trace: processing request
2024-02-27T07:11:39.985500Z  INFO request{method=GET path=/status/blocks version=HTTP/1.1 remote.addr=127.0.0.1:34202}: warp::filters::trace: finished processing with success status=200
2024-02-27T07:11:40.130654Z  INFO consensus: iroha_core::sumeragi::main_loop: Genesis block created role=Leader block_hash=297d77e702e0fb3dbecd5f438e57d0b684e5476b3f609b7dac45b7a28ce49865
2024-02-27T07:11:40.131999Z  INFO consensus: iroha_core::sumeragi::main_loop: Committing block addr=0.0.0.0:1337 role=Leader block_height=1 block_hash=297d77e702e0fb3dbecd5f438e57d0b684e5476b3f609b7dac45b7a28ce49865
2024-02-27T07:11:40.144708Z  INFO consensus: iroha_core::sumeragi::main_loop: Sumeragi initialized addr=0.0.0.0:1337 role_in_next_round=Leader
2024-02-27T07:11:42.112581Z  INFO request{method=GET path=/status/blocks version=HTTP/1.1 remote.addr=127.0.0.1:48584}: warp::filters::trace: processing request
2024-02-27T07:11:42.113589Z  INFO request{method=GET path=/status/blocks version=HTTP/1.1 remote.addr=127.0.0.1:48584}: warp::filters::trace: finished processing with success status=200

ANY PEER

Error: failed to load configuration

Caused by:
    The network consists from this one peer only (no `sumeragi.trusted_peers` provided). Since `--submit-genesis` is not set, there is no way to receive the genesis block. Either provide the genesis by setting `--submit-genesis` argument, `genesis.private_key`, and `genesis.file` configuration parameters, or increase the number of trusted peers in the network using `sumeragi.trusted_peers` configuration parameter.

Location:
    /iroha/config/src/parameters/actual.rs:63:22

Who can help to reproduce?

@timofeevmd

Notes

No response

timofeevmd avatar Feb 27 '24 07:02 timofeevmd