Multi-VNode script

Putting 2 vNodes on one VPS server will work fine.

And yes this script runs eth_mainnet. It does everything just like the original script but creates multiple nodes based on how many validator keys you provide and assigns each new instance with a new port number.

2 Likes

@doc - I think adding an extra vnode on your server (with similar specs) should work perfectly okay. I haven’t seen any problems running 2 vnodes on a VPS with 4 CPUs, 8GB RAM and 240 GB SSD. Its been up for a couple of months now and so far, so good!

3 Likes

@Jared when I ran the script and then checked with

sudo docker ps 

CONTAINER ID        IMAGE                                         COMMAND                  CREATED             STATUS              PORTS                                            NAMES                                                      
bb8d66cfbc3f        incognitochain/incognito-mainnet:20200910_1   "/bin/bash run_incog…"   10 minutes ago      Up 10 minutes       0.0.0.0:9335->9335/tcp, 0.0.0.0:9434->9434/tcp   inc_mainnet_1                                              
4750a3cfcca1        incognitochain/incognito-mainnet:20200910_1   "/bin/bash run_incog…"   10 minutes ago      Up 10 minutes       0.0.0.0:9334->9334/tcp, 0.0.0.0:9433->9433/tcp   inc_mainnet_0    

I only see the incognito mainnet running… not eth_mainnet. Any idea what could possibly be causing this?

I went ahead and modified the script to call the docker start on eth_mainnet that I saw in the original incognito/run.sh file… I think this should work, I did have to delete the previous images on my server to get it to work though.

Now I will just wait for 4-6 weeks to see if my vNodes get selected to tell if I have them setup correctly :wink:

1 Like

Hmm I’m not sure why. If I recall that script started up eth_mainnet for me.

Check your vNodes on watch.incognito.market

Also check sudo dock ps and sudo docker stats to check your vNodes are running correctly.

1 Like

This script doesn’t start eth_mainnet, it did at some points in the past however. If you want to re-enable it you’ll need to add in the docker vnet creation and have the containers setup to use them. As far as I can tell though the incognito nodes aren’t using the ethereum node.

1 Like

@Jamie Can we get some input if we need to be running eth_mainnet?

1 Like

We don’t use it anymore.

3 Likes

@mesquka @Jared @Jamie

Got this reply and just wanted to provide an FYI about having eth client for validators:

Also worth noting he updated a multinode script with eth-client as well:

I’ve updated the link, there are now 2 scripts. One with the eth container and one without so people can choose what they want to run.

5 Likes

@Jamie, can I kill eth_mainnet container on my server?

@taruneldho
Opinions seem to differ. Take a look at the most recent comments on this post

I would say, if it is running, keep it running. If it is not, leave it like that.

1 Like

First, thank you @mesquka for this script. As a newbie to ubuntu server this has been quite a learning experience for me and your script has been very helpful.

i followed all instructions (i think), to update my current server at home to run 2 nodes instead of 1. However I am seeing now that inc_mainnet_1 is not working. It is showing zero usage or stats in docker stats and in docker ps shows status “restarting (5) 38 seconds ago” and continues like that non-stop.

Any advice on where to look for a fix for this?

you already had one node running, did you completely remove that one before running the script? or did you update the starting port? did you use different validator keys?

I updated the keys in the script using my previous key for key 1 and the new key for key 2. It says here I should be able to just run the script without removing the container right?

I see now that when i check logs it says there is no space. but when i check space, there is plenty except on my thumbdrive that had the script i used. I did run the script from the thumbdrive directly…could that be the problem? Do I need to copy the script first the hard drive?

The script will use the same directory you run it from to store data for the nodes you are running. If you are running it from a USB you will need to make sure the USB either has enough space or move the script to your computer and run it there.

Thanks, yup. it looks like it created 2 new containers on the thumbdrive which are not working, my old container is still working. 4 containers total. going to remove all 4, move the script to the hard drive, and re-run.

Will update after, but i think that’s the solution here. Thank you!

@mesquka is there a recommended folder on the hard drive to run it from?

top level?

/root?

/home?

You can run it from anywhere, I run mine in it’s own directory in my home folder (~/incognito)

1 Like

Just wanted to follow-up on this. Thank you @mesquka for the script and your help. I have successfully deployed it on my server that had 1 vnode. Per your assistance I moved it to a folder on the hard disk, and ran it there. I had to remove the other node containers i had before because it didn’t do so automatically. Once i had it deployed for 2 nodes, i successfully updated things by simply adding a 3rd node key and running again, no need to remove containers at this point.

So far got it up to 5 nodes using your script.

Is there a limit? Does the port number just keep increasing> 9339? 9344? Is there an end?

I also used your tool at https://tool.incognito.best/ to confirm everything is working properly.