Use this page for instructions regarding migrating your Secure Node to a Super Node.
Upgrading the node tracker
Zen.conf Configuration
Change from Secure Node to Super Node
Description | Command | ||||||
---|---|---|---|---|---|---|---|
Upgrading the node tracker | |||||||
1 | Stop the running tracker process | For installations using systemd (assumes the unit file is named 'zentracker.service')
For installations using pm2 (assumes the tracker is running as the only or first process, numbered 0)
| |||||
2 | Move (mv) the securenodetracker folder, renaming it in the process, generally this will be ~/zencash/secnodetracker and change directory (cd) to the new folder |
| |||||
3 | Update git with the new repository URL and retrieve the latest source code |
NOTE: If git returns an error regarding any files run the following command (replacing 'filename with the file returned in the error message) and repeat the commands above
| |||||
4 | Install the latest set of node modules required for the tracker |
| |||||
zen.conf configuration - skip steps 5 and 6 if this has already been done for your node | |||||||
5 | Locate your node's public IPv4 and/or IPv6 address(es) and append them to the zen.conf file as external IP address(es) connected over port 9033 (default) NOTE: Replace <IPv4> with the public IPv4 of your node, remove <brackets> NOTE: Replace <IPv6> with the public IPv6 of your node in compressed notation without leading zeros, remove <brackets> Use the following link to ensure your IPv6 address is in compressed notation: | Create environmental variables for IPv4
Append external IPv4 into zen.conf
Create environmental variables for IPv6
Append external IPv6 into zen.conf
Append port into zen.conf
| |||||
6 | Restart zend and check the address configuration NOTE: The output of the 2nd command should display the address(es) entered in the previous step | For installations using systemd (assumes the unit file is named 'zend.service')
For installations using monit
| |||||
7 | Run node setup again to refresh the list of tracker servers and initialise the new tracker, press enter through each of the values to retain the current set
|
| |||||
8 | Update the relevant monitoring process based on your installation
| For installations using systemd (assumes the unit file is named 'zentracker.service')
For installations using pm2 (assumes the tracker is running as the only or first process, numbered 0)
| |||||
9 | Reload the node tracker process and start it
| For installations using systemd (assumes the unit file is named 'zentracker.service')
For installations using pm2 (assumes the tracker is running as the only or first process, numbered 0)
| |||||
10 | Verify that the tracker is running successfully following the update | For installations using systemd (assumes the unit file is named 'zentracker.service')
For installations using pm2 (assumes the tracker is running as the only or first process, numbered 0)
| |||||
Change from Secure Node to Super Node | |||||||
11 | Stop the running tracker process | For installations using systemd (assumes the unit file is named 'zentracker.service')
For installations using pm2 (assumes the tracker is running as the only or first process, numbered 0)
| |||||
12 | Run the node setup again;
|
| |||||
13 | Start the node tracker | For installations using systemd (assumes the unit file is named 'zentracker.service')
For installations using pm2 (assumes the tracker is running as the only or first process, numbered 0)
| |||||
14 | Verify your Super Node is displayed on the tracking website |