Advanced set up: customize the port of your Node

@khanhj,

If I do that, I get the following output on “docker ps”

parity/parity:stable  "/bin/parity -- 26 hours ago   Up 50 seconds       5001/tcp, 8080/tcp, 8082-8083/tcp, 

8180/tcp, 0.0.0.0:8546->8546/tcp, 8545/tcp, 0.0.0.0:30303->30303/tcp, 0.0.0.0:30303->30303/udp   eth_mainnet

specifically, I still see a 8545/tcp even though I have modified the run.sh for 8546.

I have not done any port forwarding or modifications for port 30303, 5001, 8080, 8082-8083, is that going to be an issue?

1 Like

@doc

So, you go with method1.

  • you dont have to do port forwarding for those ports
  • on your machine2, please try to stop eth_mainnet: docker stop eth_mainnet
  • then execute this command: docker run -ti --restart=always --net inc_net -d -p 8546:8545 -p 30303:30303 -p 30303:30303/udp -v $PWD/${eth_data_dir}:/home/parity/.local/share/io.parity.ethereum/ --name eth_mainnet parity/parity:stable --light --jsonrpc-interface all --jsonrpc-hosts all --jsonrpc-apis all --mode last --base-path=/home/parity/.local/share/io.parity.ethereum/

=> this is how it look like on my system:

[email protected]:~$ docker ps
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS              PORTS                                                                                                                               NAMES
7213ea635ab4        parity/parity:stable                  "/bin/parity --light…"   4 seconds ago       Up 2 seconds        5001/tcp, 8080/tcp, 8082-8083/tcp, 8180/tcp, 8546/tcp, 0.0.0.0:30303->30303/tcp, 0.0.0.0:30303->30303/udp, 0.0.0.0:8546->8545/tcp   eth_mainnet
d79526ad33e6        incognitochain/incognito:20200225_1   "/bin/sh run_incogni…"   8 days ago          Up 8 days           0.0.0.0:9360->9334/tcp, 0.0.0.0:9460->9433/tcp                                                                                      inc_miner_stake20

[email protected]:~$ sudo netstat -nltp | grep docker-proxy
tcp6       0      0 :::8546                 :::*                    LISTEN      12329/docker-proxy  
tcp6       0      0 :::9360                 :::*                    LISTEN      31838/docker-proxy  
tcp6       0      0 :::9460                 :::*                    LISTEN      31824/docker-proxy  
tcp6       0      0 :::5432                 :::*                    LISTEN      22026/docker-proxy  
tcp6       0      0 :::30303                :::*                    LISTEN      12300/docker-proxy  
4 Likes

@khanhj

I wanted to touch base with you again about this, as its been 8 days and neither vNode role has moved from “waiting”, and for the 6 weeks I have been running them, that has never happened… I have always had at least 1 committee selection between the two within that period, so I wanted to verify everything looks correct. Below is outputs from docker ps, and the port forwarding scheme on my router.

vNode 1, default ports (docker ps output)

CONTAINER ID        IMAGE                                         COMMAND                  CREATED             STATUS              PORTS              
                                                                                                                  NAMES                                
b3a66831c3fd        incognitochain/incognito-mainnet:20200226_1   "/bin/sh run_incogni…"   9 days ago          Up 3 days           0.0.0.0:9334->9334/
tcp, 0.0.0.0:9433->9433/tcp                                                                                      inc_mainnet                          
328edf14671f        parity/parity:stable                          "/bin/parity --light…"   9 days ago          Up 3 days           5001/tcp, 8080/tcp,
8082-8083/tcp, 8180/tcp, 0.0.0.0:8545->8545/tcp, 8546/tcp, 0.0.0.0:30303->30303/tcp, 0.0.0.0:30303->30303/udp   eth_mainnet 

sudo netstat -nltp | grep docker-proxy

tcp6       0      0 :::9334                 :::*                    LISTEN      2097/docker-proxy                                                     
tcp6       0      0 :::9433                 :::*                    LISTEN      2085/docker-proxy                                                     
tcp6       0      0 :::30303                :::*                    LISTEN      2110/docker-proxy                                                     
tcp6       0      0 :::8545                 :::*                    LISTEN      2141/docker-proxy  

vNode 2, custom ports

CONTAINER ID        IMAGE                                         COMMAND                  CREATED             STATUS              PORTS              
                                                                                                                 NAMES                                
730d5f255ec7        incognitochain/incognito-mainnet:20200226_1   "/bin/sh run_incogni…"   9 days ago          Up 8 days           0.0.0.0:9335->9335/
tcp, 0.0.0.0:9434->9434/tcp                                                                                      inc_mainnet                          
e1199e4ca95c        parity/parity:stable                          "/bin/parity --light…"   9 days ago          Up 8 days           5001/tcp, 8080/tcp,
 8082-8083/tcp, 8180/tcp, 0.0.0.0:8546->8546/tcp, 8545/tcp, 0.0.0.0:30303->30303/tcp, 0.0.0.0:30303->30303/udp   eth_mainnet   

sudo netstat -nltp | grep docker-proxy

tcp6       0      0 :::9335                 :::*                    LISTEN      1845/docker-proxy                                                     
tcp6       0      0 :::9434                 :::*                    LISTEN      1833/docker-proxy                                                     
tcp6       0      0 :::30303                :::*                    LISTEN      1858/docker-proxy                                                     
tcp6       0      0 :::8546                 :::*                    LISTEN      1884/docker-proxy 

vNode 1: 192.168.1.128
vNode 2: 192.168.1.129

port forwarding configuration:
ports

3 Likes

Hi Doc, all the data you have are correct. As there are more than 1000 Nodes now, it is normal if you wait longer than before.
We are going to publish a post so you can know the probability of having earning today. Will keep you posted.

4 Likes

Any update with this? My vNode appears to remain with the following status:

Beacon height - variable, increasing.
Layer - Shard
Role - Committee
Shard ID - 0

Thanks.

1 Like

If the beacon height is around 350k, then there is no problem. So you are in the committee of Shard 0 and you will earn some PRV soon.

If beacon height is so less than 350k, then there is still no problem :slight_smile: This means that your node still is synching. Please see this post. Currently, synchronization is so slow.

4 Likes

@khanhj

hey. I want to connect to external parity/infura.

I checked docker image. But I dont see inside that:
GETH_NAME is used?

@abduraman maybe you got ideas here?

2 Likes

My node has settled down now and appears to be working reliably.

Correct me if I’m wrong but I think ‘Shard ID -2’ means its syncing. ‘Shard ID -1’ means its waiting. And ‘Shard ID [shard numer]’ is displayed when it’s assigned to a shard in operation.

If an expert can confirm @abduraman, hopefully this helps others also.

1 Like

Correct but you may earn when shard id is -1 or -2 (normally, it shouldn’t). This abnormal case may specific to the synching state. Most of the time, the correct shard id is shown. Please follow this topic for other details. As I remember, @mesquka was trying to find the issue.

Sorry @huglester . I have no idea yet.

Yep this seems to be correct. I’ve not had the time to work on the app but I’m hoping to do some changes to the ‘status’ field so it lets you know that the node is syncing among other things. I’m hoping to be able to get back to this in the next few days.

1 Like

is it a correct return after running

rpc_port=9334 node_port=9433 ./run.sh

-bash: ./run.sh: Permission denied

image

Try running chmod +x ./run.sh to add execution permissions

before doing running rpc_port=9334 node_port=9433 ./run.sh?

rpc_port=9334 node_port=9433 ./run.sh

/bin/sh: 0: Can't open bash

@mesquka is this editing correct?

Yep, before running rpc_port=9334 node_port=9433 ./run.sh

@huglester, so you following method #2 in this post? Advanced set up: customize the port of your Node
if you tail -f the log file you may notice that when your node sync/insert new block, it sometime require Ethereum block to verify deposit proof (Eg. from ETH to pETH in Incognito-chain)

1 Like

Hello

Ok I will test and get back to you.
For now will keep an eye on logs to make sure i do not break anything

parity light - does not show rpc connections

Apr 17 12:12:56 xxx parity[24356]: 2020-04-17 12:12:56 Syncing #9889294 0x16c0…a5f8 0.1 hdr/s 0+ 0 Qed 49/64 peers 10 MiB cache 0 bytes queue RPC: 0 conn, 0 req/s, 822 µs