MultiChain Developer Q&A - Recent questions tagged port

Random ports in peer handshake

Sun, 19 Jul 2020 08:22:39 +0000

While looking at the output of getpeerinfo api call, there are random ports on addr and addr local fields. I have set the default network and RPC ports.

I have set the default network ports to be 6001 for both the nodes and connected the daemon by on the same port.

here is an example

[
    {
        "id" : 3,
        "addr" : "11.0.2.19:6001",
        "addrlocal" : "10.0.2.218:40384",
        "services" : "0000000000000001",
        "lastsend" : 1595145954,
        "lastrecv" : 1595145954,
        "bytessent" : 33682716,
        "bytesrecv" : 68302709,
        "conntime" : 1592493648,
        "pingtime" : 0.100124,
        "version" : 70002,
        "subver" : "/MultiChain:0.2.0.10/",
        "handshakelocal" : "1QEXPURG6es3LhbUNux2DELwwJyB1Jqvd9xnV4",
        "handshake" : "14MwcB2MQxLT9bcfUJR5vRrnJdJ8RWAeGGnVV5",
        "inbound" : false,
        "startingheight" : 2734,
        "banscore" : 0,
        "synced_headers" : 8676,
        "synced_blocks" : 8676,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 28,
        "addr" : "10.0.4.238:59848",
        "addrlocal" : "10.0.2.218:6001",
        "services" : "0000000000000001",
        "lastsend" : 1595145954,
        "lastrecv" : 1595145953,
        "bytessent" : 6403475,
        "bytesrecv" : 356378,
        "conntime" : 1595140368,
        "pingtime" : 0.05432,
        "version" : 70002,
        "subver" : "/MultiChain:0.2.0.10/",
        "handshakelocal" : "1QEXPURG6es3LhbUNux2DELwwJyB1Jqvd9xnV4",
        "handshake" : "1ZqTLXmJHvWrvpTniZuT4vusFBS1XUqWrZxkLL",
        "inbound" : true,
        "startingheight" : 87,
        "banscore" : 0,
        "synced_headers" : 8675,
        "synced_blocks" : 8675,
        "inflight" : [
        ],
        "whitelisted" : false
    }
]

Is this normal behavior? Will it cause any problems if there are firewall rules in place that only allow communication through the default network port?

Thanks

Multichain in Kubernetes

Wed, 13 Feb 2019 09:55:44 +0000

Hi,

I have deployed a master node in Kubernetes and I can join external (to the K8s cluster) client nodes, for instance, using Windows.

However, when I try to issue commands from the clients, and even from the master, I start to see lots of warning logs about massive peers and eventually the commands are not executed.

I presume everything is about the internal port openings that happen as part of the communication between nodes (the ports in the range of 30000 that I notice in the logs):

mchn: Sending minimal parameter set to 10.136.106.51:36906

Therefore, can you please let me know if these ports are configurable or can be somehow identified, so I can figure out how to manage them between inside and outside nodes to the K8s cluster?

Thanks!

Ethereum ICO with MultiChain

Mon, 17 Sep 2018 09:41:36 +0000

Assume the following scenario:

An ICO (ERC20 standards) is issued on Ethereum, we call the token A-token.
If we build a Multichain permissioned blockchain, on which users can settle their trades using A-token. That is to say, users can purchase A-token from crypto exchanges and use A-token to settle the trades.

Any advise on whether it is possible to implement? If it is possible, how to port A-token into Multichain?

Cannot connect to Multichain ran inside Docker

Thu, 13 Sep 2018 14:07:04 +0000

I have created a Dockerfile to run a blockchain within a Docker container. The chain is created successfully, and multichaind ran, which gives an output of:

Other nodes can connect to this node using:

multichaind dockChain2@172.17.0.2:5001

Listening for API requests on port 5002 (local only - see rpcallowip setting)

When trying to connect from another node the error received is -

Error: Couldn't connect to the seed node 172.17.0.2 on port 5001 - please check multichaind is running at that address and that your firewall settings allow incoming connections.

I have tried exposing port 5001 in docker, and using docker ps -a shows 0.0.0.0:5001->5001/tcp under PORTS.

Multichain Explorer - [ErrNo98]

Tue, 14 Nov 2017 11:08:41 +0000

Hi All

I've just gotten started on Multichain and got stuck on the Multichain Explorer part. I've been able to follow all the steps on Github up to the point of launching the explorer. The last working step was:

python -m Mce.abe --config chain1.conf --commit-bytes 100000 --no-serve

When running the following step:

python -m Mce.abe --config chain1.conf

I run into the following error:

I've tried to kill the processes listening to the port which is used for RPC API requests, however this killed the port which the other nodes require for a connection and therefore killed the blockchain.

has anybody encountered this problem and know of a possible solution?

Kind regards

Walter

starting the first node does not exit

Wed, 26 Apr 2017 15:56:10 +0000

HI

i am fairly new to multichain and was following the tutorial http://www.multichain.com/getting-started/.

so far i have created a new chain (chain1)with default parameters

now the command line does not exit when starting the node

i can try to connect with a second node but since the first one is stuck i wont be able to grant permission.

i tried some more and enabled that all can connect, so the second node can be connected but it gets stuck too upon starting!

if i force exit and try to use some multichain-cli commands i always get the error that it cant connect to the server.

what could be the cause of this?
is it a problem with the ports?

Porting to macOS

Fri, 03 Feb 2017 08:29:44 +0000

Hello,

Would you have any recommendations for someone who was thinking of attempting to port Multichain to macOS, now that the source is out?

Thanks!