Node Quick Reference
This guide serves as a handy quick reference for Node operators to efficiently configure, monitor, and troubleshoot their Kaia nodes. It covers common tasks like configuring nodes, understanding and analyzing logs, managing chaindata, and using essential commands. The guide aims to help Node operators smoothly run and maintain their blockchain nodes by equipping them with key information and best practices.
📄️ Configuration
This document explains the configurable properties of the node. Kaia node package ships with good defaults and requires very little configuration. If you changed any settings of a running node, you must restart the node to reflect the changes.
📄️ Node Log
This page details some important or frequently asked logs from Kaia nodes.
📄️ Log operation
Configure Log Rotation
📄️ Frequently Used Commands
How to find the Kaia Directory (Normally “Kaia DIR”)
📄️ Troubleshooting
Where can I find a log file for the running Kaia node using the Kaia binary package?
📄️ Use Chaindata Snapshots
You can start a node from an already-synced database called a chaindata snapshot. A chaindata snapshot is a compressed Kaia data directory.
📄️ Use AWS AMIs
The AWS AMI service for Kaia endpoint nodes is no longer being updated (last update: November 2024). While existing AMIs (dated November 2024) are still available for use, please note that they may require additional synchronization time to catch up with the current blockchain state. For alternative setup methods, such as using chaindata snapshots or performing full synchronization, please refer to Block Synchronization.
📄️ Prune Node Data
This page explains how to delete historical block states to reduce the storage requirement. Kaia offers two approaches for pruning block states:
📄️ Configure Upstream Archive Node: Upstream EN
The Upstream EN (Endpoint Node) feature allows a full node operator to utilize an archive node as an RPC fallback. For more information about full and archive nodes, see the Block Synchronization page.