Documentation
RMS Monitoring, Security, and Operations
Monitor RMS connections, CPU, memory, and network usage, maintain the Linux service, and protect backend access and LAN boundaries.
Monitoring and Operations
After rollout, monitor the local RMS client, RustMinerSystem server, upstream pool, and public uplink together. A port marked “running” is not enough to prove a healthy mining path.
Dashboard Metrics
| Metric | Healthy interpretation |
|---|---|
| CPU / memory | Does not remain in a dangerous range after compression or miner-count changes. |
| Inbound connections | Close to the number of miners moved to the port. |
| Outbound connections | Matches the consolidation setting for each port. |
| Network traffic | Compared with the pre-rollout baseline for peaks, averages, and spikes. |
| Port state | Running, waiting, and error states match current operations. |
For RMS3(NB), also confirm BTC/LTC compatibility, exact server protocol, hashrate, and upstream rejects. Lower traffic with abnormal rejects or hashrate is not a successful configuration.
Backend Security
- Set an RMS backend access password.
- Configure a private safe access path when appropriate.
- Restrict management port
42703and miner listeners to trusted network sources. - Never expose the management backend directly to the Internet.
- Treat an enabled observer page as another exposed surface and restrict it.
The safe-path URL must retain a trailing slash:
http://RMS_DEVICE_IP:42703/private-path/
Linux Service and Logs
| Item | Default |
|---|---|
| Service | rmservice |
| Config | /root/rms/local.conf |
| Runtime log | /root/rms/nohup.out |
| Error log | /root/rms/err.log |
Run the installer again for the maintenance menu. Restart after changing the management port or configuration, then verify the URL, firewall, and boot state.
Operational Rhythm
- After each expansion: check connections, CPU, traffic, hashrate, and rejects.
- Daily: inspect port state, disconnects, and error logs.
- Before upgrades: back up RMS settings and RustMinerSystem port JSON.
- After upgrades: validate a small group before restoring full traffic.
- Periodically: test the bypass address and update on-site runbooks.