> For the complete documentation index, see [llms.txt](https://energy-web-foundation.gitbook.io/ewc-validator-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://energy-web-foundation.gitbook.io/ewc-validator-documentation/guides/maintaining-a-validator-node/validator-node-service-commands.md).

# Validator Node Service Commands

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

{% hint style="info" %}
Always make sure that you have admin rights before running any command with sudo -s
{% endhint %}

### Check if the stack is running <a href="#validatorservicecommands-checkifthestackisrunning" id="validatorservicecommands-checkifthestackisrunning"></a>

Run this command to see the status of all containers:

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>docker ps -a
</code></pre></td></tr></tbody></table>

### Restart the whole stack <a href="#validatorservicecommands-restartthewholestack" id="validatorservicecommands-restartthewholestack"></a>

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>cd docker-stack
docker-compose restart
</code></pre></td></tr></tbody></table>

### Restarting after encountering problems <a href="#validatorservicecommands-restartingafterencounteringproblems" id="validatorservicecommands-restartingafterencounteringproblems"></a>

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

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>cd docker-stack
docker-compose down
docker-compose up -d
</code></pre></td></tr></tbody></table>

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 [Validator Knowledge Base](https://discuss.energyweb.org/c/knowledge-base/15)):

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>cd docker-stack
docker-compose down
rm -r chain-data/chains/Volta/db
docker-compose up -d
</code></pre></td></tr></tbody></table>

### Update a component <a href="#validatorservicecommands-updateacomponent" id="validatorservicecommands-updateacomponent"></a>

Set the desired version in

| `vi docker-stack/.env` |
| ---------------------- |

save it and run

| `docker-compose up -d` |
| ---------------------- |

### Update configurations <a href="#validatorservicecommands-updateconfigurations" id="validatorservicecommands-updateconfigurations"></a>

Make the configuration change in either `.env` or `docker-compose.yml`<br>

and run

| `docker-compose up -d` |
| ---------------------- |

### Show logfiles <a href="#validatorservicecommands-showlogfiles" id="validatorservicecommands-showlogfiles"></a>

In `docker-stack` run

| `docker-compose logs` |
| --------------------- |

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

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>docker-compose logs -f --tail 100 parity
</code></pre></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://energy-web-foundation.gitbook.io/ewc-validator-documentation/guides/maintaining-a-validator-node/validator-node-service-commands.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.