Buy crypto anonymously on the Incognito pDEX   

How to setup your own node in a blink of an eye (Now support multi-nodes per host)

#26

I don’t see https://raw.githubusercontent.com/incognitochain/incognito-chain/production/bin/inc_node_installer.sh with the update to GETH_PORT=""

1 Like
#27

The code is not yet merged. you will have to change it manually as in step 2 of the instruction (I updated the instruction).

#28

What’s the command to wipe and re-sync the vnode since “sudo rm -rfv data” and “sudo bash run.sh” no longer work?

#29

If you’re using the script above, the vNode is run under user incognito and the data is in its home folder. Try:

sudo rm -rf /home/incognito/node_data

You should first stop the vNode if it’s running and then restart it, unfortunately it’s not done by the service. Trying doing something like:

# Stop the update service
sudo systemctl stop IncognitoUpdater.service
# Stop and remove the running docker
sudo docker rm -f inc_mainnet
# Delete the cached latest tag
sudo rm /tmp/inc_node_latest_tag
# Remove all node data
sudo rm -rf /home/incognito/node_data
# Start the update service again and it will start the latest docker
sudo systemctl start IncognitoUpdater.service
1 Like
#30

That was very helpful, exactly what I needed. Thank you!

1 Like
#31

is this a correct return for the

sudo systemctl status IncognitoUpdater.service

Loaded: loaded (/etc/systemd/system/IncognitoUpdater.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2021-06-04 10:11:57 CEST; 16s ago
Process: 23551 ExecStart=/bin/run_node.sh (code=exited, status=0/SUCCESS)
Process: 23795 ExecStop=/usr/bin/pkill run_node.sh (code=exited, status=1/FAILURE)
Main PID: 23551 (code=exited, status=0/SUCCESS)

image

(Solved) Stuck trying to host VNode!
#32

Yes, it is. Since the update checking process will only need a few seconds to complete its task then it will exist.
When the update interval comes, systemd will restart the process by first stop it with ExecStop=/usr/bin/pkill run_node.sh then start it up again.
But since the process completed and existed already, ExecStop action will return the error as you already saw.

1 Like
#33

thanks, gotcha

could you refer to the "How to check if node sync and other necessary staff’ please. I don’t mean the monitoring tool - How to use the Node monitor. I mean if we can monitor nodes in terminal.

#34

Sorry to be a pain, but you should throw in curl there as well, or remove curl from the update script and replace it with wget. As it is right now, on a fresh install, you’ll end up with this in your system log and nothing is started.

systemd[1]: Started IncognitoChain Node updater.
IncNodeUpdt[13196]: Getting Incognito docker tags
IncNodeUpdt[13199]: /bin/run_node.sh: line 57: curl: command not found
systemd[1]: IncognitoUpdater.service: Control process exited, code=exited, status=1/FAILURE
#35

My bad, will include curl right now

2 Likes
#37

Can one infura API be used for multiple nodes?

#38

Yes, I use one API key for more than one node.

2 Likes
#39

One Infura with free plan supports 100,000 Requests/Day. So yeah, you can use one Infura for more than one.

1 Like
#40

After using the new script “sudo ./inc_node_installer.sh”, I see only “inc_mainnet” running after sudo docker ps. I no longer see “eth_mainnet” running in docker after using the new script. Is this correct? Can someone share a correct return value for “sudo docker ps” after running the ./inc_node_installer.sh script?

1 Like
#41

hello! Eth_mainnet The command incognito does not use) infura)

  • On Setting tab of project, copy the mainnet endpoint api key
    image
    Eg. Copy this string be5fe1410b024a8f94f62fbc106439xx
    [/quote]
    How to host a Virtual Node
#42

We no longer use eth_mainnet docker image. We use Infura instead.

#43

If only inc_mainnet is running and no settings for infura are included in the script, what functionality is lost regarding incognito? My nodes appear to be functioning normally.

#44

Please check the post again, I believe there’s a reference to Infura setup guide already.

#45

Sorry, I see the post now and have setup infura and restarted the node. One last question regarding infura: in what ways can I test or check that the infura connection to eth network is working?

#46

@Socrates, let your node sync data and validate transaction for a while (few days i think) then check setting on infura to see if there is any query
mine, for example
image

1 Like