How to host a Virtual Node

Perfect, please do note about your PC specs:

  • 8 CPUs
  • 4 GBs of RAM
  • 500 GBs of SSD

As the sync data process consume a lot CPU and storage :slight_smile:
Anyway, the development team is working on the reduction of data size :wink:

1 Like

Hey @khanhj,

CONTAINER ID        IMAGE                                         COMMAND                  CREATED             STATUS              PORTS                                                                                                                               NAMES
0ba327f146a3        incognitochain/incognito-mainnet:20200213_1   "/bin/sh run_incogni…"   33 hours ago        Up 33 hours>9335/tcp,>9434/tcp                                                                                      inc_mainnet2
fee43127e869        incognitochain/logshipper:1.0.0               "/usr/local/bin/dock…"   6 weeks ago         Up 13 days                                                                                                                                              inc_logshipper
f788fcd2742b        incognitochain/incognito-mainnet:20191227_1   "/bin/sh run_incogni…"   6 weeks ago         Up 13 days>9334/tcp,>9433/tcp                                                                                      inc_mainnet
994da074e85c        parity/parity:stable                          "/bin/parity --light…"   6 weeks ago         Up 13 days          5001/tcp, 8080/tcp, 8082-8083/tcp, 8180/tcp,>8545/tcp, 8546/tcp,>30303/tcp,>30303/udp   eth_mainnet

This is the current output of docker ps. I have some questions. The difference between this output and the above output is that 3cbb737605ec was dead and 0ba327f146a3 is live. Besides, their images are different. Obviously, inc_mainnet2 docker restarted. Is this problem in terms of earning PRV? If problem exists, instead of restarting the docker container silently, could you put some logs stating why the container restarted? If not exist, why is one (20200205_1) of two images updated but the other not (20191227_1)?

Hey @abduraman,

You’re right about inc_mainnet2 restarted, this is expected behavior. The inc_mainnet2 is running latest incognito version 20200213_1
So, the real problem is inc_mainnet still running older version 20191227_1

Please execute these commands:
sudo ps -ef | grep
sudo kill -9 <>
sudo docker stop inc_mainnet
sudo bash

=> this will restart the file to pull the latest incognito build and then run on your inc_mainnet

We’ll troubleshoot the issue why your inc_mainnet not automatically update to newer version.

PS: this problem has nothing related to earning PRV


Thanks @khanhj . Now, they use the same image.

1 Like

Is there a tutorial or a guide for setting up a pNode like we have for vNodes How to host a Virtual Node? If not can someone create one? Im currently running Ubuntu Server latest on Mac Mini.


So I can get stats this is what I get.

Could anyone help me trouble shoot this…?


Hi, can you try to split the command into two rows?
curl > && sed -i “s/xxx/validator_key/”
sudo bash
Let me know how it works.

Same thing it seems…

root@vmi347454:~# curl > && sed -i “s/xxx/mykeyhere/”
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3043 100 3043 0 0 3747 0 --:–:-- --:–:-- --:–:-- 3752
sed: -e expression #1, char 1: unknown command: `▒’

I am checking, please wait a moment.

Hi Geodesix, let’s remove the double quotation mark. Please try again with this command:
curl > && sed -i s/xxx/validator_key/ && sudo bash

That seems to have worked, thanks…

When the image is updated, the container restarts. This is OK and at this condition, “CREATED” and “STATUS” parameters in the output of “sudo docker ps” are the same. Unless the node image is updated, why do the containers restart? In that case, “CREATED” becomes older than “STATUS”. Is restarting used for fault-tolerancy? @khanhj

In general, when is the restart of a container an indicator of a problem? Could we understand from “log.txt” under “data” directory?

Yeah, it would be the case, that why the keep running in background to restart the docker container when it crashed.

You can check the log.txt and error_log.txt under data/ folder for more detail.

1 Like

But there is a problem. The contents of log.txt and error_log.txt start after the restart :slight_smile: Should I change some settings?

In addition, error_log.txt is not so readable as below. Why?

2020/02/24 01:05:27 privacy-token-���]3^YC@��k�k�H/^?^Z�
2020/02/24 01:12:06 privacy-token-���]3^YC@��k�k�H/^?^Z�
2020/02/24 01:16:05 privacy-token-���]3^YC@��k�k�H/^?^Z�
2020/02/24 01:22:05 privacy-token-���]3^YC@��k�k�H/^?^Z�
2020/02/24 03:32:05 privacy-token-���]3^YC@��k�k�H/^?^Z�
2020/02/24 08:38:06 privacy-token-{8TE�~P

I have no idea about this. Let’s wait for khanhj’s assistance.

1 Like

Hey @abduraman,

I confirm this is an issue, can you create new ticket here so that our dev will fix it later?

This problem related to decoding character.

1 Like