As a node operator, you probably want your node software to run persistently in the system background. Linux distros each have their own way of managing background services, but most (e.g. Ubuntu, Debian and CentOS 7/8) use the systemd software. systemctl is a command to introspect and control the state of the systemd system and service manager.
Controlling the vagachaind Service
Use systemctl to start, stop, and restart the service:
# Check health
sudo systemctl status vagachaind
# Start VagaChain
sudo systemctl start vagachaind
# Stop VagaChain
sudo systemctl stop vagachaind
# Restart VagaChain
sudo systemctl restart vagachaind
# Start VagaChain automatically at the next system restart
sudo systemctl enable vagachaind
# Do not start VagaChain automatically at the next system restart
sudo systemctl disable vagachaind
Access Logs
Use journalctl to access entire logs, entire logs in reverse, and the latest and continuous logs:
Available Commands:
add-genesis-account Add a genesis account to genesis.json
collect-gentxs Collect genesis txs and output a genesis.json fileedito
debug Tool for helping with debugging your application
export Export state to JSON
gentx Generate a genesis tx carrying a self delegation
help Help about any command
init Initialize private validator, p2p, genesis, and application configuration files
keys Manage your application's keys
query Querying subcommands
rollback rollback cosmos-sdk and tendermint state by one height
rosetta spin up a rosetta server
start Run the full node
status Query remote node for status
tendermint Tendermint subcommands
tx Transactions subcommands
validate-genesis validates the genesis file at the default location or at the location passed as an arg
version Print the application binary version information
Flags:
-h, --help help for vagachaind
--home string directory for config and data (default "/<rootc directory>/.vagachain")
--log_format string The logging format (json|plain) (default "plain")
--log_level string The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
--trace print out full stack trace on errors
