Skip to main content

New Install - Uninstall Begin

After the confirmation that we want to perform the uninstall is accepted, the uninstaller will begin.

Begin Uninstall

It will stop updater service, remove the Node from service ( if applicable ), and disable the auto restart service.

Stopping updater service ...................... complete
Skipping service [node_l1] status already...... ApiNotReady
AutoRestart service with pid [disabled] ....... not running

Restore the SSH configuration

Restore the SSH configuration to preNode operational state.

Restoring ubuntu SSH access ................... auth_not_found
Restoring root SSH access ..................... running
Reloading [SSH] daemon......................... complete
Restoring root SSH access ..................... complete

You may receive an auth_not_found error. You can safely ignore this error.

The 'auth_not_found' message encountered while attempting to restore the user's SSH authorization file can be safely ignored. This message indicates that nodectl's custom backup authorization file was not located on this device.

HOWEVER It is recommended to try accessing your VPS from your local system before closing this terminal session. This step ensures that access to your VPS is not interrupted.

Log retention

We will be asked if we want to retain the nodectl.log file.

If we choose y here, the current nodectl.log file will be saved for review later, after nodectl is no longer on the server and the VPS is no longer a Constellation Node.

The nodectl logs will be copied to the /var/tmp/ directory as nodectl.log.

Would you like to retain the nodectl log file? [n]: y

If we choose y, details about where the log is located are displayed.

nodectl logs will be located in the here:
location: /var/tmp/nodectl.log

P12 retention

We will be asked if we want to retain our p12 keystore files.

SECURITY WARNING

Retaining your p12 files on a Node that is not actively participating as a Constellation Network Validator Node on either the Hypergraph or a metagraph, may create vulnerability to others being able to access your private keys, therefor exposing you to a wallet hack.

If you choose to retain your p12, make sure you retrieve them and remove them from the VPS, if the VPS had no need to retain them.

WARNING Retaining the Node's p12 files can introduce
security vulnerabilities because your p12 files will be remain on this VPS.
Would you like to retain the node p12 files? [n]:

If we choose y, details on the location of your p12 files will be displayed.

In the event nodectl finds multiple p12 files with the same name, they will be saved with a .n extension where the n is a number.

myp12name.p12
myp12name.p12.1

If we want to continue retaining our p12 keystore files, we can choose y+Enter here.

WARNING Retaining the Node's p12 files can introduce
security vulnerabilities because your p12 files will be remain on this VPS.
Would you like to retain the node p12 files? [n]: y

nodectl will warn us that the p12 files will be moved to the /var/tmp directory on your Node.

nodectl p12s will be located here:
location: /var/tmp/

Data Removal

nodectl's uninstaller will remove the data related to Tessellation.

Removing Node related data .................... complete
Removing Node related services ................ complete
Removing Node related seed lists .............. complete
Removing Node related keystores .............. complete

Node Uninstall Complete

nodectl will confirm that your uninstallation has completed.

nodectl has successfully removed the Node components from the system.

Thank you for your participation with Constellation Network. We hope to see you back soon!

Remove nodectl Binary

Finally nodectl will be removed from the system by itself, and you will be dropped back at the command line prompt.

Executing final removal of the nodectl binary.
Removing nodectl binary........................ complete