Operations
Operations and troubleshooting
Run health checks, inspect logs, and isolate transfer problems.
- For
- Operators
- Updated
- September 12, 2026
Starting, stopping, or restarting?
- Run and manage RIPTON services
Use the lifecycle guide for systemd or Docker commands and safe maintenance checks.
Daily checks
sudo systemctl status ript-control --no-pager
sudo systemctl status rnode --no-pager
curl -fsS http://localhost:8080/readyz
curl -fsS -u '<user>:<password>' http://localhost:9092/api/v1/ping- Control, PostgreSQL, and every required node are reachable.
- Node storage has enough free capacity.
- Recent send and receive transfers complete successfully.
- TLS certificates are valid and not near expiry.
- Repeated transfer failures and stalled jobs are investigated.
Logs and first response
sudo journalctl -u ript-control -n 200 --no-pager
sudo journalctl -u rnode -n 200 --no-pager- 1Record the release version, time range, package ID, transfer ID, node name, and affected user.
- 2Confirm whether control readiness and node ping pass independently.
- 3Check node API connectivity separately from the UDP transfer path.
- 4Retry with a small non-sensitive file and record the exact visible error.
- 5Collect only the relevant redacted log window before escalating.