Vagrant (ssh) + Multichain Explorer

Tue, 28 Mar 2017 19:51:14 +0000

I'm trying to duplicate my local working setup (Host + VirtualBox VMs + multichain + explorer) on a Vagrant setup just to showcase my work using the Multichain Explorer.

I Vagrant ssh into my VM Nodes and setup a testchain and followed every other instructions on the Explorer, just like I did with my local setup. I used bridged networks in the network setup in my vagrant setup, this is so it mimics my local VM setup.

This is a clean run and I get the below results. Please help, I don't know what I'm doing wrong and I've tried so many other methods.

$ sudo python -m Mce.abe --config testchain1.conf --commit -bytes 100000 --no-serve

ddl_implicit_commit=true
create_table_epilogue=''
max_varchar=4294967295
clob_type=CLOB
binary_type=buffer
int_type=str
sequence_type=update
limit_style=native
[(u'foobarbaz', u'bazfoobar')]
concat_style=ansi
Assigned chain_id 1 to MultiChain testchain1
Failed to catch up {'blkfile_offset': 0, 'blkfile_number': 1, 'chain_id': 1, 'loader': u'default', 'conf': None, 'dirname': u'/home/vagrant/.multichain/testchain1', 'id': 1}
Traceback (most recent call last):
  File "Mce/DataStore.py", line 2892, in catch_up
    if not store.catch_up_rpc(dircfg):
  File "Mce/DataStore.py", line 3117, in catch_up_rpc
    tx = get_tx(rpc_tx_hash)
  File "Mce/DataStore.py", line 2974, in get_tx
    rpc_tx_hex = rpc("getrawtransaction", rpc_tx_hash)
  File "Mce/DataStore.py", line 2949, in rpc
    ret = util.jsonrpc(chain_name, url, func, *params)
  File "Mce/util.py", line 246, in jsonrpc
    raise JsonrpcException(resp['error'], method, params)
JsonrpcException: getrawtransaction: No information available about transaction (code -710)

And here is my vagrant file

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "ubuntu/trusty64"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end

getaddednodeinfo - info on all nodes

Mon, 05 Oct 2015 12:32:46 +0000

Hi, what is the closest command to getaddednodeinfo in multichain? is it listpermissions?. I need info on all the nodes that have got permissions, but may not be connected at the point in time.

getaddednodeinfo doesn't return any data.

Thanks

Senthil

Nodes on virtual boxes

Thu, 20 Aug 2015 12:40:34 +0000

I am trying to run two unix nodes as virtualboxes on a windows computer (So its creating some kind of virtual network within a computer). The address on the two nodes (when I run multichaind chain1 listpermissions) are exactly the same. Is this normal? The nodes are not connecting to each other as well.

MultiChain Developer Q&A - Recent questions tagged virtual-nodes

Vagrant (ssh) + Multichain Explorer

getaddednodeinfo - info on all nodes

Nodes on virtual boxes