Emergency guide for Teku client

One-page interactive complete emergency guide for Teku client.

Disclaimer

This guide is for informational purposes only. The author nor website owner does not guarantee accuracy of the information in this guide and is not responsible for any damages or losses incurred by following the guide. See more.

Teku client can be used for staking on various supported chains. Client installation is always only one, used by services with an individual configuration (different service name, data path and ports in use).

Validators cannot start due to existing lock file

This may occur, for example, in the event of a power failure—when the staking node powers back on, validators cannot start due to existing lock files.

Lock files can be removed with a use of Remove Lock files util.

Stucked Execution/TekuBeacon client

If a any client got stucked, you can simply restart them.

sudo systemctl restart ExecutionService

sudo systemctl restart tekubeacon

This (and many others) can be also automated through Teku Beacon Log Monitor service.

Interactive Config

Interactive variables

System:
User:
SSH port:
CPU type:

Execution layer

Client:
Service:
- Data:
- Port:
- P2P:
- RPC:

Consensus layer

Client:
NodeJs version:
jdk ver version:
Beacon service:
- Data:
- Port:
- P2P:
- Quic:

Install Teku client Update Teku client Add Teku validator Exit Teku validator