Elys Network
  • Introduction
    • Overview
    • How it Works
    • Key Features
  • Getting Started
    • Quick Start Guide
  • Core Features
    • Swap
    • Earn
      • Simple Staking
      • Liquidity Mining
    • Perpetuals
    • Leverage LP
  • Tokenomic and Rewards system
    • Tokenomics
    • ELYS: The All-In-One Token
    • EDEN & EDEN Boost
  • GOVERNANCE
    • Elys Network Governors
    • Governor Foundation Delegation Program
  • Developer Resources
    • Elys Network Validators
      • Initial System Setup
      • Installing Elys Node
        • Validator Creation
        • Launch the Node
      • Additional Considerations
      • Troubleshooting
    • Security
  • Social Links
    • Elys Network Socials
Powered by GitBook
On this page
  • 1: My validator has voting_power: 0
  • 2: Node Crashes Due to Excessive Open Files
Edit on GitHub
  1. Developer Resources
  2. Elys Network Validators

Troubleshooting

Common issues

PreviousAdditional ConsiderationsNextSecurity

Last updated 5 months ago

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 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
unjail