Tutorial: How to manually download latest pruned ChainDB [GOOGLE CLOUD]

Nodes & Mining
#13

I did this process only using google’s cloud service, however, with other cloud services you don’t have to.

I saved time in updating the database.

#14

I’ve tried to archive the ChainDB folder from one of my machines (Google Cloud) and unarchive it to my Raspberry Pi, but after restarting it stucks on “Pruning”. I re-installed NKN, it’s doing the same. Any idea why?

1 Like
#15

I don’t know for sure, but one time I did the same thing between two VPS and it went wrong.
Download directly from the link, delete the ChainDB folder before extract the ChainDB_pruned_latest.tar.gz file

1 Like
#16

Fix your transfer unpack command with this one, so it’s done in one go, not wasting space on a small storage VPN.

wget -O - “https://nkn.org/ChainDB_pruned_latest.tar.gz” -q --show-progress | tar -xzf -

Also no need to delete the ChainDB file after the transfer.

#17

Hi, i´m getting this message when i run that script:

“gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now”

#18

received the same message, does anyone have an answer?

#19

Maybe in this topic

1 Like
#20

Is this software available for Windows OS yet? I am facing the pruning problem and my node status shows as “Not started”. Was syncing well all day long but just broke down a few mins ago.

image

#21

Hi，Can I do it when vps mining?
If so, when I reboot my vps, the mining program will automatic run again？
Thank you !

1 Like
#22

wget -O - “https://nkn.org/ChainDB_pruned_latest.tar.gz” -q --show-progress | tar -xzf -

There’s a problem with double quotes if you just copy paste the link. Delete and retype the quotes

#23

I’m sure I’m an idiot, but what exactly am I supposed to type on Step #5? Thank you.

username@nkn-full-node-1-vm-1:~$ sudo su
root@nkn-full-node-1-vm-1:/home/username# cd
root@nkn-full-node-1-vm-1:~# cd nkn/nkn-commercial/services/nkn-node/
bash: cd: nkn/nkn-commercial/services/nkn-node/: No such file or directory
root@nkn-full-node-1-vm-1:~# rm -r ChainDB
rm: cannot remove ‘ChainDB’: No such file or directory
root@nkn-full-node-1-vm-1:~# cd username@nkn-full-node-1-vm-1
bash: cd: username@nkn-full-node-1-vm-1: No such file or directory

#24

How would you do this on a windows node?

#25

I am having a similar issue. Did you figure it out?

#26

Same issue here, anyone figured it out yet??

#27

how can i download chaindb your link everytime say 404 not found , i waiting 4 days and never find answer about this waiting db syncing and only %2 :slight_smile: this so boring and need a help

1 Like
#28

I will ping technical team for a solution

2 Likes
#29

We no longer provide ChainDB after we introduced light sync in v2.1.7 (NKN MainNet v2.1.7 Release). Light sync takes much less storage space than ChainDB. Here is the quote about how to enable light sync:

How to enable fast sync and light sync

Please note that fast sync and light sync can only be enabled when node has NO local ChainDB directory (i.e. a fresh sync). You need to remove the ChainDB directory and let node do a fresh sync if you want to enable them.

There are two ways to enable fast sync and light sync:

  • Add --sync fast argument when starting nknd to enable fast sync, or add --sync light argument when starting nknd to enable light sync.

  • Add "SyncMode": "fast" to config.json to enable fast sync, or add "SyncMode": "light" to config.json to enable light sync.

You should only choose one sync mode, not both.

#30

thx for answers i started fast sync and wait , Should I delete it from the line after synchronization? "–sync fast
"

#31

If you want to try light sync, you should change config from fast to light, stop nknd, remove ChainDB directory, and start nknd again

1 Like
#32

The program closes after a certain period of time during synchronization. I am using a restarter. Is there a different solution?