Uninstalling Etho Protocol Nodes

How to quickly disable the Etho Protocol Node services and delete the application data.

Introduction

Removing the Etho Protocol node services and data is as simple as disabling the services and deleting the application data. When you disable the services, they still exist on your system but they are not executed upon reboot.

This guide assumes you installed the Etho Protocol Node software as the ether1node user. If you installed the software as a different user, adjust the instructions accordingly, specifically on the last step replace /ether1node/ with the username for your Etho Protocol user.

Disable Etho Protocol Services

Regardless of which node you're running, executing all the following commands will disable all Etho Protocol Node services.

sudo systemctl stop ether1node
sudo systemctl disable ether1node

Delete Application Data

Delete all IPFS data and chain data by executing:

rm -rf /home/ether1node/.ipfs/*
rm -rf /home/ether1node/.ether1/*

Reversing The Process

If you've changed your mind and want to run the Etho Protocol Node (regardless of type) after all, you can reverse the whole process and return into a fully synchronized and running node by executing:

sudo systemctl enable ether1node
sudo systemctl start ether1node

Checking Etho Protocol Service Status

Whether you've decided to stick with your decision to disable the Etho Protocol Node services or decided to enable them again, you can use the commands below to determine their status.

Make sure the Etho Protocol processes are either running or not running by executing:

sudo journalctl -f -u ether1node

You should see no records indicating activity if the services are disabled. If you see activity, the services are running.

You can also check the operational status of the Etho Protocol Node services by executing:

sudo systemctl status ether1node

The first 2 commands are specifically for Gateway Nodes while the last one is common across all Etho Protocol nodes. If the services are disabled, that will be reflected in the status message returned.

Last updated