I’m running mine on VPSs and wouldn’t mind tripling up
50gb/vnode should get you through a year at current transaction load. That is unless you start having logging events then your logs might stress that out.
Now if the transaction load goes up like we all hope, then you might want to be able to put 100gb/vnode.
For CPU’s, have 1vCPU, and 1-2g ram per vnode. But always start with 2vCPU’s. You have to consider the OS as needing time as well.
For networking nothing less than 100mb, with a 4-5TB bandwidth Limit, best to have a larger channel, not sure if 4Tb is still needed with the new storage update version… I don’t think the amount of data received changed, just what they store locally did. (Could be wrong)
To triple up, I would say 200-300gb storage, 3vCPU and 3-4g ram should work.
With 200mb connection 4TB bandwidth limit.
What are the steps / things to install on a fresh VPS? I’m getting errors because this script doesn’t install docker or other required programs.
I tried but failed at pulling parts from the original node script.
Run the following before running the script:
docker -v || bash -c "wget -qO- https://get.docker.com/ | sh"
I’ve updated the script to install docker and kill any other instances of
incognito.sh on launch to prevent conflicts
@mesquka Can we just update the script with more validator keys to add more nodes or is there a more recommended way to add nodes? I already used your script to get a few nodes running but now I would like to spin up some more nodes.
I did this and both are running good just haven’t been paid for around 7 days is that normal?
Yep, if you add in new validator keys and then run the script again new instances should be started up and run.
Yeah, if you can connect your nodes in the app or on my tool incognito.mesquka.com then they’re running fine. Earning slots are a bit random, see this topic for more details: My Node hasn't earned in x days/weeks
hey I did this but i do not see eth_mainnet running is that okay?
Yes, the script doesn’t start eth_mainnet. I’ll add this in as it seems like the nodes use it now. I had removed it as they didn’t seem to be using it previously.
So do we need that? because my nodes are running without it?
When I run multi nodes I see this error that comes out in the log.txt not the error_log
The multi-vnode script doesn’t change anything inside the docket containers, so that’s not a consequence of this script
One of my nodes that was setup using your script earned just a day or two ago. Any reason to rerun this script?
Have you seen that error in the logs prior?
I haven’t looked at my logs. I just check that the port is open and that it maintains uptime.
I’m trying this out on a vps with an existing node. I replaced key 1 with the existing node and key 2 with the new validator key.
- I run it and after some errors around the initial node already binding the port.
- I check docker ps. In docker I see inc_mainnet, eth_mainnet and inc_mainnet_1 which looks good to me, inc_1 is cranking away at ~100% CPU.
- I added the node in the app and staked it.
- When I added it to https://incognito.mesquka.com/nodes I don’t see an error but it is blank in the box. Should I expect it to say -2 if everything is good? Or how long will it take the tool to catch up?
If the node is showing up in the incognito tool, it’s up. Does it display a BLS key? If so it’s running fine.
One does now but one is still blank. For a test I added nonsense ip and port to see if the tool threw an error but it didn’t which is why I reached out.
I realize now that I had one with ‘direct connect’ and one without. Without is now showing -2. I’ve removed direct connect from the other, we’ll see if it shows up