Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Validator Node Guides
    • 💰Delegated Staking
      • What is delegated staking?​
      • For Node Operators
      • Understanding Delegated Staking
      • Prerequisites
      • Create Delegated Staking Configuration
      • First Time Configuration
      • Modify Existing Configuration
      • Add/Update Delegating Staking Parameters
      • Update Delegated Staking
      • Duplicate Update
      • Status Command
    • 🚧Build Your Node
      • Create Discord Account
      • 🗒️Node Operator Notes
      • ⚙️Node Specifications
      • 🚧Generic Build a VPS Guide
      • ☁️Cloud Provider Specific
        • 🚧Build AWS EC2 Instance
        • 🚧Build DigitalOcean Droplet
        • 🚧Build Hetzner Server
      • 🚉First Time Connection Guide
      • 💽The nodectl utility
      • Download nodectl
      • 🏗️Turn your VPS into a Node
        • 🚩Node Prerequisites
        • 🐇Quick Install Guide
        • 🎨Normal Install Guide
        • 🛠️Manual Installation
      • 🏆Authorize to Join Hypergraph or metagaph
    • 💰Collateralize Your Node
    • 1️⃣First Time Cluster Connection
    • 💫Enable Auto Restart
    • 📂Operational Guides
      • ♻️Restart Validator Node Guide
      • 🐎Upgrade Tessellation Quick Start
      • 🏭Upgrade Tessellation Guide
      • 🏗️Reinstallation Guide
      • ♻️Backup/Restore a P12 KeyStore
      • 🚋Migrate V1 to V2 - P12 Keystore
  • 👑MainNet
    • MainNet & IntegrationNet Quick Start Guide
    • 🚧Upgrade Tessellation to v3
  • 🥅IntegrationNet
    • 🧪IntegrationNet Quick Start Guide
  • Metagraphs
    • 🚪Dor metagraph
      • 🚪Dor Validator Onboard Guide
      • 🚪Understanding Rewards
      • 🚪Technical Procedures
        • 🚪Build Dor Validator Node
  • 📚References
    • 📚nodectl Command Reference
    • Firewall Settings Table
    • 🔐SSH Remote Access
      • 🔑Create SSH Keys
      • 📁Upload SSH Public Key
      • 🔐Securing SSH Access
      • ♻️How to SSH into VPS
    • 🍴Node Fork Types
    • 🗝️P12 Keystore
    • 🏐Tarball
    • 💻Virtual Private Server
  • GitHub nodectl utility
  • Run a Node Validator
  • Lattice Dashboard
Powered by GitBook

Main

  • Website
  • Get DAG
  • Explore Projects
  • Partners

Socials

  • Telegram
  • Discord
  • X (Twitter)

Tools

  • Wallet
  • DAG Explorer
  • Coingecko

© 2025 CONSTELLATION NETWORK

On this page
  • Understanding the various auto restart options
  • 🔁 auto_restart
  • ⬆️ auto_upgrade
  • 🔄 on_boot

Was this helpful?

Export as PDF
  1. Validator Node Guides

Enable Auto Restart

This guide outlines how to enable nodectl's auto-restart feature along with auto-upgrade support.

PreviousFirst Time Cluster ConnectionNextOperational Guides

Last updated 4 days ago

Was this helpful?

Enabling this configuration allows your node to:

  • Automatically monitor and restart services if they become unresponsive or disconnected from the cluster

  • Automatically check for and apply updates via nodectl when new versions of Tessellation are available (based on your configuration preferences)

This ensures your node remains healthy, up-to-date, and engaged in network operations with minimal manual intervention.

1

Enter Configuration Edit Mode

sudo nodectl configure -e -cb -d
2

Access Auto Restart Options

We will choose the R from the Edit Menu.

3

Enable All Options

  • Choose y to enable auto_restart

  • Choose y to enable auto_upgrade

  • Choose y to enable on_boot

4

Confirm Selections

Choose y to confirm selections.

5

◽ Exit Configurator

Choose Q to exit back to the command line interface.

6

Confirm Auto Restart is Enabled

sudo nodectl auto_restart status

Understanding the various auto restart options

The nodectl utility includes several optional features designed to automate node recovery, version compliance, and startup behavior. These options help ensure your Validator node remains online, up-to-date, and resilient without requiring constant manual intervention.


🔁 auto_restart

When auto_restart is enabled, nodectl continuously monitors the health and cluster status of your node.

Key Functionality:

  • Detects if your node drops off the cluster due to issues such as network interruptions, process failures, or misconfigurations.

  • Automatically attempts to restart and rejoin the node to the cluster without user involvement.

  • Automatically attempts to return your node to consensus if it stops participating for a variety of reason.

This is especially helpful for maintaining high availability and reducing downtime.


⬆️ auto_upgrade

Constellation Network requires all active Validator nodes to run the same version of Tessellation. If your node is not running the correct version during a cluster upgrade, it will be rejected from joining, regardless of its other credentials (e.g., collateral, seed list status).

When auto_upgrade is enabled:

  • nodectl will monitor the current cluster version.

  • If a version mismatch is detected, it will automatically upgrade your node to match the active cluster version.

This ensures version compliance and minimizes the risk of node rejection due to outdated software.


🔄 on_boot

Enabling on_boot ensures that nodectl's auto-recovery features are initialized automatically when your VPS starts up, such as after:

  • A manual system reboot

  • An unexpected crash

  • Cloud maintenance or hardware restarts

How it works:

  • On system boot, nodectl launches the auto_restart process.

  • If necessary, auto_upgrade also activates to bring the node back in sync with the cluster version.

  • This setup enables your node to recover and reconnect unattended after the VPS completes its boot sequence.


These automation features are highly recommended for production Validator nodes, as they enhance stability, uptime, and operational efficiency across the Constellation Network.

💫
​
​
​
​
​
​