ALLinONE-nknnode script, deploy nodes faster, with your own ChainDB!

Yes, use the new one.

Option 4: Custom URL install is the same script

ah okay, thanks

sorry you meant the script had errors, as it was still using the old name.

I fixed them just now. next time you run the script it will be fixed

sorry about that

Very cool script. Unfortunately, I ran into a problem where the software is not creating the folder. I left the script running overnight and came back to a Segmentation Fault (core dump).
I verified the service is running and tried restarting it but the folder just isnā€™t creating. Do you have suggestions on how to recover from this?

I tried going through the script and running a few of the commands myself manually including creating the folder manually, but am stuck.

image

Iā€™m working on it myself. I dontā€™ get it, I never have this bug :smiley:

I think running:
sudo su -

and

apt-get update -y; apt-get upgrade -y

before the script does the trick.

Amazing that you sent such a fast reply, thanks for that.

I am setting up two nodes at the same time. One node I did follow your directions carefully running the commands:

sudo su -
and
apt-get update -y; apt-get upgrade -y

Unfortunately both the nodes failed with the same error.
After your reply I ran the apt-get commands again and made sure I was root on both. I re-ran the script and now the nodes are running! Thanks so much for your contribution to the community.

Just updated the script

try it

wget -O nkndeploy.sh 'http://107.152.46.244/nkndeploy.sh'; bash nkndeploy.sh

BTW

what were you trying to do? Just install nodes?

I have seen wallets receiving rewards every hour or every few minutes :confused:

Yes, I was just trying to setup additional nodes, I have a server with the ChainDB on it that I was leveraging.

I just created a new node and tried the new script. It didnā€™t prompt me for the server with the chainDB so I think the install2/3 functions in the script didnā€™t run either.

Still fixing my fork up, sorry about that

Screenshot 2021-04-13 at 21.07.09

see attached pictureā€“

running Nodes on 2 power Server ( from no112358 Script)
from last 48 Hrs,
ā€”??? No rewards ??? ----

how long its take to see any rewards ? or need to wait a week or month ?

I have 36 nodes ATM and I get 1 reward or 2 per day, do the math.

Yes it takes a long time. No worries.

I was reading other post , many mention they are running for a weeks and nothing? No rewards ???

Was wondering is it worth running it ā€¦

They should give little rewards after few days to make sure end user know itā€™s working fine.

for example I am running few other coins nodes on other Machines and I can see rewards with in 24 hrs

yeah NKN doesnā€™t work like that, sorry.

You get paid when you do the work. Proof of relay.

Yes it can take week or more to get anything, but then you get 11NKN at once. That pays off the 5$ server youā€™re using.

Get your free VPS credits here:

I am not using 5$ server , they are expensive and power full one example below

ā€“VPS details belowā€”
Fujitsu PRIMERGY RX1330 M3 Intel Xeon E3-1230v6 3.50GHz
Memory: 64GB ECC DDR4 RAM
Storage: 1x 120GB SSD
Unlimited traffic per month
OS: Ubuntu 20.4
Guaranteed speed: 2 Gbit/s up & 2 Gbit/s down

-Running by yours script

Screenshot 2021-04-13 at 21.07.09

why such crazy VPS? for NKN node you need 1 core 1GB RAM 25 GB VPS

First thanks to you, you make it very easy to installā€¦

I have few server like that for other projectsā€¦

I thought just give it try to see if that worth it ā€¦

But no worries I can wait another week & seeā€¦

As you can see bandwidth is unlimited & In out speed is
2Gbit/s ā€¦ & nodes are running fine

NKN nodes eat up MAX 300 GB combined per month (about 50%/50%).

You donā€™t need that much CPU power if you deploy with ChainDB archive. After itā€™s synced up it uses very little CPU power.

Just so you know you can deploy smaller VPS.

1 Like

The NKN nodes should be: 1 core, 1 GB of RAM, 25 GB if node only, 35GB of storage if both node and web host for the ChainDB archive.

Segmentation fault is supposedly a memory thing, where you run out of it.

What specs does your server have, the one that failed?

What part of the script did you run?

Also on what VPS provider, or is it at home?

These are Azure B1s nodes. Iā€™m using up the $200 credit they give :partying_face: :partying_face: :partying_face:
1 vCPU
1 GB memory
30GB storage

I actually think that failure was caused by the script looping for hours and hours because the folder was never created. It might have eaten up memory because it was an infinite loop.
When I re-ran the full script this morning (still choosing option for new node and custom URL for download), making sure I was SU, the folders were created quickly and they are up and running. Plus the chaindb archive downloaded super fast from Digital Ocean!

1 Like