Energy Web Documentation
  • Energy Web Ecosystem
  • Launchpad by Energy Web
  • EWC Validator Documentation
  • Community Ressources
  • Legacy documentation
  • Start here
    • EWC Validator Documentation Overview
  • EWC Governance
    • Governance process
    • Proof-of-Authority Consensus Mechanism
    • EWC Validator Node Operational Functions
    • EWC Validator Roles & Responsibilities
    • Validators eligibility
    • Validators code of conduct
  • Guides
    • Set-up your Validator node in minutes with EW Launchpad
    • Installing a Validator Node
      • Host Machine Requirements
      • Recommended Security Settings
      • Operating System Requirements
      • Validator Node Installation Instructions
    • Maintaining a Validator Node
      • Validator Node Architecture
      • Validator Node Service Commands
      • Updating the Client
      • Changing the Validator Config File
      • Checking node status & logs
      • Migrating a validator node to a new environment
      • How To Transfer EWT from a Validator Node
      • Problems connecting to peers
  • Secure Your Validator Node
    • Changing validator payout address and setting up multi-signature
Powered by GitBook
On this page
  • Check if the stack is running
  • Restart the whole stack
  • Restarting after encountering problems
  • Update a component
  • Update configurations
  • Show logfiles
Export as PDF
  1. Guides
  2. Maintaining a Validator Node

Validator Node Service Commands

PreviousValidator Node ArchitectureNextUpdating the Client

Last updated 11 months ago

The following commands can be run on a node to aid in daily operation.

Always make sure that you have admin rights before running any command with sudo -s

Check if the stack is running

Run this command to see the status of all containers:

Restart the whole stack

Restarting after encountering problems

After encountering problems e.g. with the parity client, it is better to run

If after restarting the client you are still encountering problems, you can try to delete the database and re-sync the node (please only do this after trying to restart without deleting the database first; if you have any questions or need assistance please post in the ):

Update a component

Set the desired version in

vi docker-stack/.env

save it and run

docker-compose up -d

Update configurations

Make the configuration change in either .env or docker-compose.yml

and run

docker-compose up -d

Show logfiles

In docker-stack run

docker-compose logs

to e.g. show the last 100 lines of the parity client logs run

docker ps -a
cd docker-stack
docker-compose restart
cd docker-stack
docker-compose down
docker-compose up -d
cd docker-stack
docker-compose down
rm -r chain-data/chains/Volta/db
docker-compose up -d
docker-compose logs -f --tail 100 parity
Validator Knowledge Base