Installation and Upgrade
This guide covers installing and upgrading the Rumi Agent.
Prerequisites
Operating System: macOS (x86_64 or ARM64) or Linux (x86_64 or ARM64)
Java: JDK 11 or later
Disk Space: At least 2GB free for installation and data
Network: Access to downloads.n5corp.com (for remote installation)
For ARM64 macOS (Apple Silicon), the x86_64 distribution runs via Rosetta 2.
Quick Start
Standard Installation
curl -fsSL https://downloads.n5corp.com/rumi/agent/latest/install.sh | bashThis installs the latest version to ~/rumi/rumi-agent.
Installation with Custom Location
curl -fsSL https://downloads.n5corp.com/rumi/agent/latest/install.sh | bash -s -- \
--install-dir=/opt/rumiInstallation with External Data Directory
Installation Options
--install-dir=DIR
Installation directory (default: $HOME/rumi)
--data-dir=DIR
External data directory for persistent data
--dist-type=TYPE
Distribution type: bundled (default) or standalone
--force
Skip confirmation prompts
--verbose
Enable verbose output
--from PATH
Install from a local distribution archive
--download-only
Download distribution only (no installation)
Distribution Types
bundled — Includes InfluxDB for metrics storage (recommended for standalone deployments)
standalone — Agent only, requires external InfluxDB
Specific Version Installation
To install a specific version instead of latest:
Directory Structure
After installation, the following structure is created:
Key Directories
current/
Symlink pointing to the active release
data/
Persistent data that survives upgrades
releases/
All installed versions
Configuration
Configuration files are stored in the data/ directory and are preserved across upgrades.
Agent Configuration (data/agent/agent.conf)
Controls the agent's behavior:
HTTP server port
InfluxDB connection settings
XVM heartbeat collection settings
Controller integration
Controller Configuration (data/controller/controller.conf)
Controls the embedded Rumi Controller behavior.
InfluxDB Configuration (data/influxdb/influxdb.conf)
Time-series database configuration for metrics storage (bundled distribution only).
First-Time Configuration
On first startup, default configuration files are automatically copied from the release directory to the data directory. You can then customize these files as needed.
Starting and Stopping
Start the Agent
Or with a custom installation directory:
Stop the Agent
Verify the Agent is Running
A successful response indicates the agent is running.
Upgrading
Standard Upgrade
To upgrade to the latest version:
The installer automatically:
Detects the existing installation
Preserves your configuration in the
data/directoryInstalls the new version in
releases/Updates the
currentsymlink to point to the new version
Upgrade with Custom Data Directory
If you installed with --data-dir, specify the same directory during upgrade:
Rollback to Previous Version
If you need to rollback to a previous version:
Docker Deployment
The Agent can be deployed as a Docker container.
Building the Docker Image
Running the Container
Docker Configuration
Base image
Ubuntu 22.04
Java version
OpenJDK 8
Exposed port
7778
Data volume
/home/rumi/rumi-agent/data
Health check
curl http://localhost:7778/rumi-agent/ping
The container runs as the rumi user and includes SSH client support for remote provisioning operations.
Data Directory Management
Using an External Data Directory
The --data-dir option allows you to store persistent data on a separate volume:
Using faster or larger storage for metrics data
Separating data from application binaries
Easier backup management
Migrating Data to External Directory
If you have an existing installation and want to migrate to external storage:
When prompted, confirm that you want to migrate the existing data. The installer will copy all data to the new location and create a symlink.
Troubleshooting
Agent Won't Start
Check if the agent is already running:
Check for port conflicts:
Review the agent logs in the data directory.
InfluxDB Issues (Bundled Distribution)
Check if InfluxDB is running:
Restart InfluxDB by stopping and starting the agent.
Upgrade Fails with Data Directory Mismatch
If you see an error about data directory mismatch during upgrade:
Verify the correct
--data-dirvalue by checking the existing symlink:Use the same
--data-dirvalue shown in the symlink target.
Checking Installed Version
Listing All Installed Versions
Last updated