> For the complete documentation index, see [llms.txt](https://elys-network.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elys-network.gitbook.io/docs/developer-resources/elys-network-validators/troubleshooting.md).

# Troubleshooting

### 1: My validator has voting\_power: 0

If your validator has a voting power of 0, it has been jailed, which implies that it has been removed from the active validator set. Validators can be jailed for either failing to vote on 500 of the last 10000 blocks or double signing.

If the validator has been jailed for downtime, it is possible to recover the voting power. Start `elysd` again if it is not already running:

```
elysd start
```

Allow your full node to synchronize with the latest block. You can then [unjail](/docs/developer-resources/elys-network-validators/installing-elys-node/validator-creation.md#unjailing-a-validator) your validator.

Finally, check the validator to verify if the voting power has been restored:

```
elysd status
```

If the voting power of the validator appears to be lower than before, it implies that the validator has been slashed for downtime.

###

### 2: Node Crashes Due to Excessive Open Files

The default maximum number of files that can be opened by a Linux process is 1024, which may be insufficient for `elysd`, resulting in process crashes. To resolve this, execute ulimit -n 4096 to increase the number of open files allowed, and restart the process with `elysd` start. If you are using a process manager like systemd to launch `elysd`, it may require additional configuration. A sample systemd file to resolve this issue is provided below:

```
# /etc/systemd/system/elysd.service
[Unit]
Description=Elys Node
After=network.target

[Service]
Type=simple
User=ubuntu
WorkingDirectory=/home/ubuntu
ExecStart=/home/ubuntu/go/bin/elysd start
Restart=on-failure
RestartSec=3
LimitNOFILE=4096

[Install]
WantedBy=multi-user.target
```


---

# 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://elys-network.gitbook.io/docs/developer-resources/elys-network-validators/troubleshooting.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.