Transaction node is not functioning correctly, after few months of subscription RRS feed

  • Question

  • Hi Team,

    We have a POC application, for that we have setup the Azure ethereum consortium blockchain. Until few months the there is no problem with the Blockchain, But now frequently the transaction node fails. If we are restarting the Tx VM, it will run for few days. But again after few days it will stop working. Due to this our application is not functioning correctly. (Current config have 2 mining node and 1 tx node)

    See the below admin page. 

    Ethereum Node Status

    Node Hostname Consortium Participant ID Peer Count Latest Block Number
    *******55nk6-tx0 N/A Not Running Not Running
    *******55nk6-mn0 0 2 714058
    *******55nk6-mn1 1 2 714058

    Monday, April 16, 2018 10:53 AM

All replies

  • Hello,

    Based on the naming convention, it appears that you are using the older version of the Ethereum templates on Azure.

    We recommend deploying our new Ethereum solution which contains improvements for reliability, as outlined in the linked blog post.

    Microsoft Azure Blockchain Team

    Friday, April 20, 2018 12:57 AM
  • We have deployed certain contracts that uses some live data, how we can migrate it into new version. Currently the smart contract hold certain information and we need it for the existing project(data migration very important).
     Also we noticed the data movement between contract is very complex.
     How we make sure it will be stable for long term.
    Monday, April 23, 2018 4:35 AM
  • The simple approach would be to peer the new nodes with the old nodes and delete the old infrastructure after the new nodes have synced.  Unfortunately, the old version's infrastructure is dramatically different than the new Ethereum network infrastructure and will have to be paired manually.

    If your existing network was deployed as a Leader or Member (check if you have a VNet Gateway resource) then it will be easier to connect:

    1. Deploy a new Proof-of-Work network with options (Create New -> Consortium) using a new consortium member Id
    2. SSH into the old VM and use genesis.json as the custom genesis block in the new network
    3. Select the VNet Gateway resource and navigate to the Connections tab 
    4. Create a connection to the VNet Gateway of the previous deployment
    5. Perform steps 2 and 3 on the old Ethereum network connecting to the new network
    6. Navigate to the bootnode page on the old admin site: <PublicIP>/bootnodes.txt
    7. SSH onto one of the new VMs and terminate the geth process
    8. Modify geth.cfg to replace the BOOTNODE_URLS with the old network's bootnode from step 6
    9. In start-private-Blockchain.sh, comment out line 36 setup_bootnodes and line 81 BOOTNODE_URLS=...
    10. Start up geth again by running /etc/rc.local 

    Your new nodes will have a shorter Blockchain than the previous deployment and discard their chain in favor of the canonical chain.

    Microsoft Azure Blockchain Team

    Monday, April 30, 2018 8:53 PM
  • Try using the newer version of the templates. They are better. Here is an excerpt.

    These solution templates are designed to make it faster and easier to deploy and configure a multi-member consortium Ethereum network with minimal Azure and Ethereum knowledge. With a handful of user inputs and a single-click deployment, each member can provision their network footprint using Microsoft Azure compute, networking, storage, and other services across the globe. Each member's network footprint consists of a set of load-balanced transaction nodes with which an application or user can interface with to submit transactions, a set of mining nodes to manage consensus, and a VPN gateway for cross-tenant connectivity.

    I hope this helps!

    Thursday, April 30, 2020 1:00 PM