Health and diagnostics

Use these commands for a safe, mostly read-only picture of what the appliance thinks is installed, configured, and running before you restart services or change TSDuck. They are the recommended entry point for support calls and for validating a fresh boot or image update.

Recommended first diagnostic flow

Run on the guest as ec2-user:

pixop-version
pixop-preflight
pixop-healthcheck
pixop-stack status

• pixop-version — recipe, container digests, and build identity; compares your instance to what documentation assumes.
• pixop-preflight — consolidated PASS/WARN/FAIL for license (where applicable), units, GPU, and listeners.
• pixop-healthcheck — HTTP/metrics-oriented health suitable for scripting.
• pixop-startup-timeline — boot and service bring-up ordering when something is slow or racey.
• pixop-test-live — controlled live-path exercise; more invasive than preflight — read the page before running in production.

If preflight reports FAIL, fix licensing or units (Licensing and support, Service and processing) before deep stream captures.

AWS vs KVM

Guest CLI tools self-elevate; only KVM host install breaks that pattern.

Version expectations

Documentation may describe capabilities not present on your AMI recipe. Missing subcommands usually mean the tool or flag is absent on that build — not a broken install. Confirm with pixop-version and per-command -h.

Command pages

Back to the CLI reference.