Part 10

Reboot your node
Check services start at boot

	Description	Command
1	If everything has worked through parts 1 - 10, reboot your node to ensure all services start at boot	sudo reboot
2	Allow your node to boot and SSH to validate the services, replace 'zenops' with your own username and <FQDN> with your own Fully-Qualified Domain Name, remove <brackets>	ssh zenops@<FQDN>
3	Windows users, load your last session in PuTTY to login using your SSH key pair
4	Check the status of both zend and the tracker, both should return active (running) if after running the status command you are not returned to a command prompt, exit the status details by pressing CTRL + c	sudo systemctl status -n 0 zend zentracker Example Output zenops@node01:~$ sudo systemctl status -n 0 zend zentracker ● zend.service - Zen daemon Loaded: loaded (/lib/systemd/system/zend.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-05-24 22:31:30 EDT; 34s ago Process: 21612 ExecStart=/usr/bin/zend -daemon -pid=/home/zenops/.zen/zend.pid (code=exited, status=0/SUCCESS) Main PID: 21615 (zend) Tasks: 16 Memory: 810.0M CPU: 18.963s CGroup: /system.slice/zend.service └─21615 /usr/bin/zend -daemon -pid=/home/zenops/.zen/zend.pid ● zentracker.service - Zen node daemon installed on ~/nodetracker/ Loaded: loaded (/lib/systemd/system/zentracker.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-05-24 21:34:27 EDT; 1h 1min ago Main PID: 19648 (node) Tasks: 10 Memory: 38.9M CPU: 4.110s CGroup: /system.slice/zentracker.service └─19648 /usr/local/bin/node /home/zenops/nodetracker/app.js
5	Check the status of your node on the tracking website, use the search box and enter the FQDN of your node https://supernodes.zensystem.io/nodes/all << Super Nodes Select your node and check the following values (top left of the detail page) are true and up respectively - example shown to the right

Horizen English

Part 10 - Reboot and Validate Services

Part 11 of 11 - Reboot and Validate Services

Super Nodes