Skip to main content
Keeping your Sui node up to date is critical for network participation and security. This guide covers update procedures and maintenance tasks.

Update Process Overview

Never delete your node databases during an update unless explicitly instructed. Deleting databases will require a full resync which can take days.
Typical update workflow:
  1. Download new binary or Docker image
  2. Stop the node
  3. Replace binary or update configuration
  4. Start the node
  5. Verify successful startup

Monitoring for Updates

Official Channels

Version Information

Check your current version:
For running nodes:

Systemd Update Procedure

1

Download new binary

2

Stop the node

Verify it stopped:
3

Backup current binary (optional)

4

Replace binary

5

Start the node

6

Verify startup

Docker Update Procedure

1

Stop containers

This preserves volumes (databases).
2

Update image version

Edit docker-compose.yaml:
Or use environment variable:
3

Pull new image

4

Start containers

5

Verify startup

Automated Updates

Using Watchtower (Docker)

Watchtower automatically updates Docker containers:
Automated updates should only be used with caution. Test updates on testnet first and ensure you have monitoring in place.

Update Script

Create an automated update script:
Usage:

Configuration Updates

Sometimes updates require configuration changes.

Check for Breaking Changes

Review release notes for configuration changes:

Apply Configuration Changes

1

Backup current configuration

2

Edit configuration

3

Validate configuration

4

Restart node

Rollback Procedure

If an update fails, rollback to the previous version:

Systemd Rollback

Docker Rollback

Maintenance Tasks

Database Pruning

Check database size:
Pruning is configured in validator.yaml:
Manual compaction (if needed):

Log Rotation

For systemd:
For Docker:

Metrics Cleanup

Prometheus data retention:

Emergency Maintenance

Node Crash Recovery

1

Check logs for errors

2

Verify database integrity

3

If database corruption detected

You may need to restore from snapshot. See Snapshots for details.

Disk Full Recovery

Security Updates

Private Security Fixes

For critical security vulnerabilities, Mysten Labs may release signed binaries before source code publication. Public key location:
Download and verify private release:
For specific binaries:

Testing Updates

Test on Testnet First

Always test updates on testnet before mainnet:
  1. Run a testnet validator
  2. Apply update to testnet validator
  3. Monitor for 24-48 hours
  4. If stable, apply to mainnet

Update Checklist

  • Review release notes
  • Test on testnet
  • Backup configuration
  • Schedule maintenance window
  • Notify delegators (for validators)
  • Perform update
  • Monitor for 1 hour post-update
  • Verify metrics and logs
  • Update documentation

Scheduled Maintenance

Planning Maintenance Windows

For validators:
  • Communicate with delegators
  • Schedule during low-activity periods
  • Keep downtime under 1 hour
  • Have rollback plan ready

Maintenance Mode

Before major maintenance:
Leaving and rejoining the committee should only be done for extended maintenance. For normal updates, simply restart the node.

Post-Update Verification

After any update: