stado service endpoint-check
Invocation
stado service endpoint-check [OPTIONS] --host <HOST> --env-file <ENV_FILE> <NAME>Purpose
Does this unit's env file agree with what is actually listening? The endpoint half of `env-show`: every loopback URL or port the file's effective assignments declare, checked against the host's own socket table, with the process that holds each port named. `host inventory` does this for forward markers; this does it for a unit's environment. Exits non-zero when a loopback endpoint is declared and nothing is listening there, and when the check could not be performed at all.
Required inputs and options
| Input or option | Contract |
|---|---|
<NAME> | Service whose host-local process reads the environment |
--host <HOST> | The single registry host to check |
--env-file <ENV_FILE> | Environment file on the target, absolute or rooted at $HOME |
--json | Command option; required or optional as shown in the invocation. |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.