Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    there are two services working on different ports: one is for client communications (Torii: commands and queries) and another is for inter-peer (consensus etc)
    Javier Rojo
    @frojomar
    And, in addPeer, you should add the second service? You should add a peer in the port 10001 of the new host IP? Or in the port 50051?
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    usually 10001 is the port for internal communications, as defined in the config:
    internal_port" : 10001,
    Javier Rojo
    @frojomar
    After trying different ways, I haven't found anything that works. There can be so many configurations where something can go wrong, that it is almost impossible to display if you don't follow a few exact steps, knowing where to change the values in the genesis.block files, in the definition of the nodes, etc...
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    while we don't have a documentation page describing this process in detail, you can have a look here https://github.com/hyperledger/iroha-deploy/tree/master/ansible/roles/iroha-docker
    Javier Rojo
    @frojomar

    If I remove all addPeer instructions from the genesis.block, it tells me a bug like that: "Irohad startup failed: Have no peers in WSV after restoration!"

    If I pick up a node with the configuration file, do an addPeer, pick up the other with the same genesis file (modifying in the addPeer of 10001 the peerKey by the public peerKey that I have created previously), both are not connected.

    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    you must not modify genesis block for the 2nd peer, they must be exactly same
    Javier Rojo
    @frojomar
    And the peerKey of the addPeer is the same for both?

    In short:

    1. I raise a node in a container, using the following genesis.block and config.docker

    2. I use the instruction "iroha-cli --account_name node1 --new_account" to generate the keys for the new node

    3. I make an addPeer to 172.22.0.5:10001 (the address of the container I will raise for the new node) and the public key I have generated in the previous step.

    4. I raise a new node in a container, using the same genesis.block as before and config.docker and having in the directory the public and private keys that I have generated.

    Is that all?

    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    if you want to add a peer to a running network, the genesis corresponds to the initial state of that network
    Javier Rojo
    @frojomar
    image.png
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    0.0.0.0 is invalid in this case
    Mikhail Boldyrev via telegram
    as is 127.0.0.1
    Mikhail Boldyrev via telegram
    it only works for 1-peer network
    Javier Rojo
    @frojomar
    must be 172.22.0.4 ? That is the IP of the first container
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    sounds right
    Javier Rojo
    @frojomar
    Are the steps correct? Or should you create the second container before doing the addPeer
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    for now its better to commit AddPeer first and then start the other peer
    Javier Rojo
    @frojomar
    image.png
    I think this is good.
    Javier Rojo
    @frojomar
    There are more steps to follow? Because, even though they've now connected, the new node doesn't have access to the data from the old one and, in the old one, the new transactions remain in the state "Transaction has collected all signatures."
    sorabot
    @sorabot

    Mikhail Boldyrev via telegram

    the new node doesn't have access to the data from the old one
    this means they did not synchronize, so maybe something gone wrong

    Javier Rojo
    @frojomar
    image.png
    Right. RPC connect failed
    Javier Rojo
    @frojomar
    It's problem of PostgresDB, I think
    Javier Rojo
    @frojomar
    This is log of original node:
    image.png
    And this is log of second node:
    image.png
    If you know the error in advance, thank you. If not, it doesn't occur to me that it may be the cause already
    Javier Rojo
    @frojomar
    Now, this change. This is node 2:
    image.png
    And this node 1:
    image.png
    (That repeat this 3 lines without stopping after add a asset)
    Sajan Maharjan
    @MaharjanSajan_twitter
    image.png

    I want to reset my initial block configuration for this, i run

    irohad --config config.docker --genesis_block genesis.block --overwrite_ledger --keypair_name node0

    but as shown in the above message, existing block store are rather restored! how can i get over this? should i define my block store to be rather stored at a different place than /tmp/block_store/ ??

    Thanks!

    Sajan Maharjan
    @MaharjanSajan_twitter
    image.png
    the above message shows that executing the above command gives me an error saying it failed to parse the genesis block
    Sajan Maharjan
    @MaharjanSajan_twitter
    any help here?
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    Sajan, obviously, as the message suggests, there is some problem with genesis block. check that it is there, is readable and if you did some changes check the syntax.
    Mikhail Boldyrev via telegram
    this is inconsistent. please check that iroha indeed was started the way you show.
    sorabot
    @sorabot
    Sumaid via telegram
    Hi
    I am a newcomer to the Hyperledger community. Is there something I can contribute in HL Iroha?
    sorabot
    @sorabot
    Mikhail Boldyrev via telegram
    Hi! Generally we track issues in Jira: https://jira.hyperledger.org/browse/IR
    also, we are participating in HL internship program, so if you are a student you can apply to one of 5 projects with Iroha.
    If you get lost in our Jira (which is a mess...) we can help you find an interesing piece of work, just say what area are you interested in most and do you want an easy-breezy taskie or a moderate chunk.
    Or you can just search the source for TODO tag.
    sorabot
    @sorabot
    Sumaid via telegram
    Thanks!
    Yes, I am a student and I am planning on applying for HL mentorship under Iroha project.
    Sumaid via telegram
    I will look for some TODO issue in Jira.
    Mikhail Boldyrev via telegram
    TODO is in the source code on GitHub
    Sumaid via telegram
    Oh I thought, you meant 'TO DO' status.
    sorabot
    @sorabot
    Sumaid via telegram
    Hi,
    I was following the docs guide to build iroha, but getting error when I try to run tests. Build was successful but still
    build/test_bin is empty
    Sumaid via telegram
    So getting error
    'Unable to find executable'
    170/170 tests failed