Error code reference
Generated file. Do not edit by hand. Regenerate from the repo root with
make docs/generate(or directly withCGO_ENABLED=0 go run scripts/gen-errors-md.go scripts/docsgen_wiring_pin.goand always both files: without the wiring pin the generator sees only the ce registry and silently drops every shc-registered module).
Every typed error SHC can raise. Codes follow the pattern
X<HTTP><SEQ><MNEMONIC> where HTTP is the HTTP status class
(400 = client error, 500 = server error), SEQ is a 3-digit
sequence, and MNEMONIC is a 6-or-more-letter hint.
Exit codes: usage and parse errors exit the CLI with 2; every
runtime failure, any X-code, exits with 1. The HTTP class does
not select the exit code; it travels to scripts as http_status
in the -o json error envelope. See the
output contract §7.
Total: 3481 error codes across 131 modules. Source of truth is the
coded registry (core/coded), populated by each module’s
errors.go init().
(global): 58 codes(unattributed): 9 codesacme: 6 codesadapter: 29 codesapp: 757 codesapparchive: 3 codesaudit: 6 codesauth: 116 codesbackup: 338 codesbranding: 14 codesca: 24 codescapabilities: 2 codescapacity: 10 codescatalog: 5 codescatalogbuild: 2 codescertbroker: 8 codescli: 3 codesclone: 88 codescluster: 121 codesclusterfs: 10 codescmd: 2 codescollector: 7 codescompletion: 2 codescondition: 3 codesconfig: 21 codesconnections: 77 codesconsole: 4 codescontainerbroker: 19 codescore/addrblock: 8 codescore/api: 16 codescore/appcatalog: 1 codecore/appref: 1 codecore/collectorcfg: 1 codecore/composeunits: 1 codecore/config: 3 codescore/containerendpoint: 2 codescore/daemonclient: 8 codescore/db: 37 codescore/eegate: 1 codecore/eestub: 1 codecore/enginemarker: 1 codecore/executor: 86 codescore/fwdhook: 1 codecore/herd: 1 codecore/hostactivate: 14 codescore/hostplat: 3 codescore/incusapi: 2 codescore/jinja: 13 codescore/labeltext: 2 codescore/log: 1 codecore/nic: 2 codescore/nodefact: 2 codescore/objchange: 2 codescore/openstack: 3 codescore/otelboot: 2 codescore/pagecache: 1 codecore/replicalabel: 4 codescore/rqlited: 29 codescore/secretscratch: 1 codecore/selector: 11 codescore/svcexec: 12 codescore/tenantscope: 1 codecore/timescale: 2 codescore/usagecharge: 1 codecore/validation: 3 codescore/volume: 34 codesctx: 1 codedaemon: 57 codesdeploymentspec: 11 codesdepnet: 3 codesdns: 73 codesdocker: 15 codesdoctor: 17 codesevents: 11 codesexport: 42 codesfabric: 54 codesfailover: 2 codesfence: 52 codesforms: 2 codesforward: 9 codesfreeze: 5 codeshealth: 20 codesinspect: 2 codesinternal_rpc: 35 codesjob: 26 codeskv: 3 codeslabelcheck: 3 codesleader: 5 codeslicense: 39 codeslogs: 8 codesmcp: 4 codesmesh: 50 codesmetrics: 7 codesnetwork: 1 codenode: 24 codesnodeagent: 24 codesnodelease: 19 codesnotification: 14 codesotelrelay: 12 codespods: 50 codesportal: 45 codesportforward: 7 codesprivilege: 2 codesproxy: 15 codespurge: 3 codesquota: 20 codesrebalance: 1 codereplicadoc: 10 codesrepo: 26 codesresolver: 5 codesretention: 8 codesrollout: 15 codesscan: 4 codesschedule: 14 codesscheduler: 31 codessearch: 3 codesselfclean: 2 codesshell: 8 codesstack: 16 codesstorage: 168 codesstorerpc: 5 codessubsystems: 121 codessupportbundle: 14 codestask: 13 codestelemetry: 5 codestenant: 13 codestest: 10 codesunderlay: 16 codesuser: 33 codesvault: 64 codesvip: 26 codes
(global)
Section titled “(global)”Source: core/coded
Count: 58
| Code | HTTP | Message template |
|---|---|---|
X200002INVFMT | 200 | invalid {format_type} format {value}, {detail} |
X200003OPFAIL | 200 | operation failed {operation}{error}{output} |
X200008VLTREN | 200 | failed to rename vault secrets {error} |
X200009RESFAL | 200 | {operation} failed for {resource} {name} {error} |
X200013PRSFAL | 200 | failed to parse {file} for {purpose} {error} |
X200129CFGCHG | 200 | collector config changed {changed_keys}, restart required |
X200920SUBFAL | 200 | subsystem {name} {operation} failed {error} |
X400000BADREQ | 400 | bad request {detail} |
X400003FLDUNK | 400 | --fields matched no key in this output, requested {fields}, available {available} |
X400007VLTRES | 400 | failed to resolve vault reference, {reason} |
X400008CTXREQ | 400 | context required to {operation} |
X400011EMPMNT | 400 | empty mount specification |
X400015NOTTYP | 400 | interactive confirmation required, pass --yes to go ahead without a prompt |
X400038NMEREQ | 400 | name is required |
X400051INVURI | 400 | invalid secret-ref uri {value}, {reason} {error} |
X400071SCLMAL | 400 | service {service_name} has a malformed x-shc-scale block: {reason} |
X400124VLTREF | 400 | could not resolve vault ref {ref} |
X400225SCLOLD | 400 | --scale {service}={value} is the retired spelling, write --scale {service}={now} |
X400955RTMDRV | 400 | runtime {runtime} has no driver in this daemon, so nothing can run it here |
X400955RTMPIN | 400 | cannot deploy {requested_runtime} stack on node {node_id}, runtime is {node_runtime}, pick a node whose runtime is {requested_runtime} or change this node’s runtime |
X400957INVDUR | 400 | invalid duration format {duration} |
X403000FORBID | 403 | permission denied |
X404000NOTFND | 404 | not found |
X404023CLSNOF | 404 | cluster {name} not found in config, available {available} |
X404101OPRNOF | 404 | operation {operation_id} not found or expired |
X404128FILNOF | 404 | file not found {path} |
X404912TNTNFD | 404 | tenant {tenant_name} not found |
X408000REQTMO | 408 | operation timed out |
X409000CONFLT | 409 | already exists |
X429001RATLMT | 429 | rate limit exceeded, try again later |
X499000REQCNL | 499 | request canceled |
X500000UNKNOW | 500 | unknown error |
X500002RNDDEC | 500 | render decode failed {detail} |
X500005VARNLD | 500 | vars not loaded, call load first |
X500051SVCNWR | 500 | {module} service not wired |
X500052SVCNRS | 500 | {module} service returned nil result |
X500095NOCRTS | 500 | missing cluster-CA certs, {reason} |
X500104SUBCYC | 500 | circular or unresolvable subsystem dependency {stacks} |
X500107TOKEXE | 500 | cluster tokenExec failed {detail} |
X500901OPFAIL | 500 | {operation} failed {error}{output} |
X500935INTUNH | 500 | internal server error {error} |
X500938RSPENC | 500 | failed to encode {what} response {error} |
X500939FSMKDR | 500 | mkdir failed {path} {error} |
X500940FSWRTF | 500 | write_file failed {path} {error} |
X500941FSREAD | 500 | read_file failed {path} {error} |
X500942FSRMTF | 500 | rmtree failed {path} {error} |
X500943FSCPYT | 500 | copytree failed {src} {dst} {error} |
X500944FSLIST | 500 | listdir failed {path} {error} |
X500947FSCHWN | 500 | chown failed {path} {uid} {gid} {error} |
X503011NDIDUN | 503 | cannot route to node {node}, this daemon could not resolve its own node id and will not run the request locally |
X503020ENTNRD | 503 | ent client not ready for {operation} |
X503908LDRMOV | 503 | the cluster has no leader to answer this request right now, leadership is moving or quorum is lost, try again in a few seconds |
X503911VOTCHG | 503 | this node is rejoining the cluster store as a {suffrage} while its voter role changes, so it cannot answer for a few seconds, try again |
X503912STOUNR | 503 | this node’s request to the cluster store failed, {reason} |
X503955RTMUNK | 503 | cannot read this node’s runtime record, so nothing runs here, {error} |
X503999RTENYI | 503 | {feature} not yet wired |
X504000DLNEXC | 504 | operation timed out |
X507000NOSPCE | 507 | no space left on device |
(unattributed)
Section titled “(unattributed)”Count: 9
| Code | HTTP | Message template |
|---|---|---|
X400719WKSPAG | 400 | workshop {workshop} page {page} line {line}, {detail} |
X401720WKSSGN | 401 | signing in to {portal} failed, {detail} |
X403720WKSOWN | 403 | session {session} on {portal} belongs to another learner |
X404718WKSNON | 404 | no workshop named {name}, the built-in ones are {known} |
X404720WKSOFF | 404 | the portal {portal} offers no workshop {workshop} |
X500718WKSTMX | 500 | tmux {step} failed, {detail} |
X502720WKSPRT | 502 | the portal {portal} answered {step} with {detail} |
X503720WKSFUL | 503 | the portal {portal} has no room for a session of {workshop} now, it said {notification} |
X504720WKSWAT | 504 | session {session} did not start in {wait} |
Source: modules/acme
Count: 6
| Code | HTTP | Message template |
|---|---|---|
X200858ACMRTY | 200 | certificate {name} not issued, retrying in {wait}, {error} |
X200860ACMGON | 200 | certificate {name} not issued, the answering node {node} is gone, retrying in {wait}, {error} |
X400856ACMPRV | 400 | acme provider {provider} is not configured, set acme.providers.{provider} |
X409857ACMCHL | 409 | acme authorization for {name} offers no {type} challenge |
X500859ACMSTO | 500 | acme certificate store {step} for {name} failed, {error} |
X502855ACMORD | 502 | acme order for {name} from provider {provider} failed at {step}, {error} |
adapter
Section titled “adapter”Source: modules/adapter/importsaga, modules/adapter
Count: 29
| Code | HTTP | Message template |
|---|---|---|
X400148ADPROT | 400 | --install-root is gone, write --root |
X400948ADPRUN | 400 | cannot run migration for {subject}, {detail} |
X400950ADPMAN | 400 | invalid foreign app manifest, {detail} |
X400951ADPMIG | 400 | invalid migration file {path} {error} |
X400953ADPREQ | 400 | invalid adapter request, {detail} |
X400960SAGEVI | 400 | import saga step {step} completed without evidence, so it is not done, a step that claims something about the world must measure it |
X400961SAGPLN | 400 | invalid import saga plan, {detail} |
X400966ADPSRC | 400 | cannot extract migration source for {app}, {detail} |
X400968ADPOLD | 400 | --from {value} is the retired spelling, write {now} |
X404950ADPMNF | 404 | no migration path for adapter {adapter} app {app} |
X404951ADPNOA | 404 | no {adapter} apps found on the box, {detail} |
X409060SAGORD | 409 | import saga step {step} cannot run until {needs} has completed with evidence, run shc import resume after resolving {needs} |
X409061SAGBND | 409 | refusing to bind {stack} to its shared external store: {missing}, binding now lets a first-boot ceremony or a second writer reach data the source estate is still serving |
X409062SAGINS | 409 | refusing to re-install {stack}: an edge has already been bound, so the install’s first-boot ceremony would run against live shared storage, compensate the saga or finish it forward by hand |
X409063SAGDET | 409 | refusing to install {stack}: the install line still carries the held-back shared-store edge {edge}, the detach did not happen and first boot would write into live shared storage |
X409064SAGCMP | 409 | refusing the {step} compensation, {why} |
X409065SAGCLB | 409 | the restore into {stack} did not survive verification twice, {detail}, stop the app’s own initialisation before restoring again rather than re-running the restore |
X409066SAGRSM | 409 | import saga {saga} will not resume unattended, {why} |
X500950ADPENU | 500 | failed to enumerate adapter {adapter} catalog {error} |
X500951ADPTRN | 500 | failed to transpile foreign app {app} {error} |
X500952ADPCAT | 500 | cannot read the {adapter} app catalog on the box, {detail} |
X500957ADPMAT | 500 | failed to materialize adapted app {name} {error} |
X500958ADPGRP | 500 | failed to assemble migration group for {name} {error} |
X500962ADPXFM | 500 | migration transform {job} failed {error} |
X500967ADPBND | 500 | no binding export for deployment {deployment}: {detail}; restate -i at install |
X500967SAGJRN | 500 | import saga journal {op} failed, {detail} {error} |
X500968SAGACT | 500 | import saga step {step} failed {error} |
X501000ADPSSH | 501 | box ssh transport to {host} failed {error} |
X501001ADPPUL | 501 | failed to pull data volume {volume} from box {error} |
Source: modules/app/exposeflag, modules/app
Count: 757
| Code | HTTP | Message template |
|---|---|---|
X200021RDRLIT | 200 | plug {plug_name} on provider {provider_stack_name} mints an OIDC client with a bare wildcard redirect, declare allowWildcardRedirect: true in the plug to record the decision, or narrow it to absolute callback URLs |
X200038SOKUNS | 200 | integration edge {plug_name} to {provider_stack_name} is unbound, {reason}, the render proceeds without it |
X200039IDPUNR | 200 | restored deployment {stack} has identity edge {plug} whose issuer {issuer} is unreachable ({problem}), SSO logins will fail while every health check stays green, and if the app disables password login the site is unloggable-into, restore the IdP at that address or repoint the edge with shc update {stack} -i {plug}= |
X200042NOLOGIN | 200 | restored deployment {stack} has NO usable login path, {closed_by} is on so its credential login form is not rendered and none of its {edges} is reachable, the deployment answers 200 while offering nobody a way in including admins, reopen the local door with shc update {stack} --var {closed_by}=false, or bring the recorded IdP back and re-render |
X200055VDPMIG | 200 | vdeployment sidecar directory {path} was not migrated{error}, the instances under it stay invisible to listing and to the destroy guard until it is moved by hand |
X200056VDPMGD | 200 | vdeployment sidecar directory migrated from {from} to {to} |
X200058VDPKEY | 200 | vdeployment sidecar {path} still carries the retired vapp body key and was not rewritten{error}, the instance under it stays invisible to listing and to the destroy guard until the file is fixed by hand |
X200059SOKDRF | 200 | socket {socket} of {provider}: {what} could not be rendered, {detail}; a consumer reads it as the empty string |
X200063PLCWHY | 200 | placement put {tenant}/{stack} ({environment}) on {node} by rule {source}: {reason} |
X200066DCKTHR | 200 | registry pull rate limit for stack {project}, retrying in {delay} |
X200069PLCPRF | 200 | {tenant}/{stack} ({environment}) runs on {node}, which --prefer {prefer} does not name: {reason} |
X200086PODPRJ | 200 | {deployment} has no replica projects, its compose runs as before: {error} |
X200087PODROW | 200 | {deployment}‘s replica assignment rows were not written by its install, the leader’s scheduler binds them from its stored spec: {error} |
X200088PODPIN | 200 | {deployment}‘s replicas run on {node}, and the fabric addresses of its replicas that left were not released, they stay reserved until a later install or update of it releases them: {error} |
X200091JOBRAN | 200 | start job {job} of {deployment} ended 0 for run {run} |
X200092DCKWAT | 200 | waiting for deployment {project} to converge for up to {budget}, containers {state} |
X200093APPORP | 200 | deployment {stack} dropped the retired declaration {file} from its app tree, the app no longer ships it, so any persisted edge still resolving through it is now unbound and must be repointed with shc update <consumer> -i <retired>! -i <served>=<provider> |
X200094DCKONE | 200 | deployment {project}: compose up --wait reported failure only for the completed {oneshots}, continuing with the convergence poll |
X200095DEPRCY | 200 | deployment {project}: this deploy recreated {recreated}, so {dependents} were restarted: a recreated container takes a new address and a dependent that resolved the old one at startup would keep using it forever |
X200096DEPRCK | 200 | deployment {project}: this deploy recreated {recreated}, and {refused} declare a dependency on what moved but were not restarted. Each may still hold the old address; restart by hand only if the reason no longer applies |
X200097CVGRST | 200 | deployment {project}: the failed converge had already stopped {casualties}, so {started} were started back and re-observed running; the converge itself still failed. compose up recreates before it fails, and restart: unless-stopped does not restart a container that was never started |
X200098CVGRSU | 200 | deployment {project}: the converge failed and whether it left containers stopped is unknown, {reason}, nothing was started back. Check by hand with {command} ps and start anything the converge stopped |
X200099STKRCN | 200 | deployment {subject} was parked at {parked} with no operation behind it and is now {settled}: {reason} |
X200103SVCUND | 200 | deployment {tenant}/{stack}/{environment} no longer declares {services}, so the rows were removed and desired-vs-actual stops counting a replica nothing can satisfy |
X200112APPSHD | 200 | app {app} resolves from repo {repo}, not {dir}, which no installed app owns, move {dir} out of the shipped root to stop it shadowing the published app |
X200113SCHPRG | 200 | schedules of uninstalled deployment {stack} in environment {environment} not removed{error}, remove them with shc schedule rm |
X200115DEPIMG | 200 | deployment {project}: this deploy superseded {superseded}; kept {kept} for rollback (SHC_DEPLOY_IMAGE_KEEP), removed {removed} |
X200116DEPIMK | 200 | deployment {project}: superseded images left in place: {refused} |
X200117DEPIMS | 200 | deployment {project}: superseded-image cleanup skipped on this node: {reason} |
X200120SPCINT | 200 | deployment spec for {tenant}/{stack} not forgotten{error}, its stored specs stay until a reinstall writes over them |
X200121HKDEFR | 200 | deployment {tenant}/{stack}/{environment}: {services} stopped by its operator, so this update did not run the {hook} jobs {jobs}, which need them; they run at its next start, shc start {stack} -t {tenant} -e {environment} |
X200122HKDRAN | 200 | deployment {tenant}/{stack}/{environment}: ran {jobs}, the {hook} jobs its last update left for this start |
X200124HKDWAI | 200 | deployment {tenant}/{stack}/{environment}: the {hook} jobs {jobs} its last update left still wait for {services}, stopped by its operator; shc start {stack} -t {tenant} -e {environment} starts them and runs the jobs |
X200130STRPRT | 200 | deployment {stack}: the shared-content-container scan could not read {scopes}, so the check that another deployment does not already hold this one’s bucket or database is partial, so a clean result here proves less than it looks like it does |
X200131STRPRE | 200 | deployment {tenant}/{stack}/{environment} was already sharing a content container before this deploy ({conflicts}). Either consumer’s teardown destroys it whole, so give one of them its own container name; this deploy was allowed because the sharing is not new |
X200132HKRRND | 200 | deployment {tenant}/{stack}/{environment}: the {hook} hook changed {keys} after this deploy had rendered them, so the deployment is rendered and converged once more to hand the new values to its services |
X200135UNICMP | 200 | uninstall of {tenant}/{stack}/{environment} did not read its rendered compose{error}, only the networks and volumes labelled for it were removed |
X200136SPCRVT | 200 | deployment {tenant}/{stack}: the staged spec could not be put back{error}, the node agent may refuse the old containers until an update records again |
X200138DEPDRP | 200 | deployment {tenant}/{stack} ({environment}) kept status {held}: dropped deploy outcome {outcome}, the row no longer held {expected} |
X200140RNDSEL | 200 | the rendered documents of {deployment} are kept in RAM and not sealed, because this node’s vault is locked, so a reboot loses them and it starts again only at its next update |
X200141PUBTPL | 200 | {stack}: service {service} publishes {port} in its own compose, which a cluster that listens itself does not do, publish it with --expose {expose} |
X200157VARHEL | 200 | the credential vars {keys} of {deployment} stay as literals on this node’s disk until the next backup seals them, the render could not seal them into the vault: {error} |
X200168SYSFRC | 200 | uninstalling {stack}, a module of the master tenant, with --force; the deployments that lose their provider with it: {consumers} |
X200169PRVRBD | 200 | {consumer} still binds {provider} and was not bound to it again:{error}; run {command} |
X200170PRVLOS | 200 | the deployments that lose their provider with {stack}: {consumers} |
X200182OTLNIL | 200 | no telemetry collector runs in this cluster, so the OTLP export of {tenant_name}/{stack_name} ({environment}) has no destination and its telemetry is lost |
X200183VLTPRG | 200 | vault secrets of uninstalled deployment {tenant}/{stack}/{environment} not removed{error}, list them with shc vault ls -t {tenant} -s {stack} -e {environment} and remove them with shc vault rm |
X200185RULPRG | 200 | placement constraints of uninstalled deployment {tenant}/{stack}/{environment} not removed{error}, list them with shc constraint ls -t {tenant} and clear them with shc constraint clear --scope deployment -t {tenant} -s {stack} -e {environment} |
X200186UNIUNA | 200 | uninstall of deployment {tenant}/{stack} ({environment}) continued using the nodes that answered; these nodes could not be asked: {unasked}; any deployment directory on them was left untouched and is reported by the database.orphaned-dirs diagnosis when doctor runs on them after they return |
X200188RNDKPT | 200 | {path} on {node}, an older render of deployment {tenant}/{stack}/{environment}, was not removed, {reason}, this node asks again on its agent’s next pass |
X200189RNDDRP | 200 | the rendered documents held for {dir}, deployment {tenant}/{stack}/{environment}, could not be dropped and stay in memory until the daemon restarts or the deployment renders on this node again: {cause} |
X200191DIRRMV | 200 | removed {path} on this node, the directory it kept of deployment {tenant}/{stack}/{environment}, which was uninstalled at {deleted_at} |
X200192DIRKPT | 200 | {path} on this node, the directory it kept of deployment {tenant}/{stack}/{environment}, uninstalled at {deleted_at}, was not removed, {reason}, this node asks again on its agent’s next pass |
X200193CPYKPT | 200 | copy of uninstalled deployment {tenant}/{stack}/{environment} on {node} not removed, {reason}, shc ls there still lists it until the copy goes, install and uninstall the deployment again to remove it |
X200194REPKPT | 200 | replicas of uninstalled deployment {tenant}/{stack}/{environment} on {node} not taken down, {reason}, they run until that node’s agent next applies its assignments |
X200196TRERMV | 200 | removed {path} on this node, a move set it aside of deployment {tenant}/{stack}/{environment}, which was uninstalled at {deleted_at} |
X200197OWNPRG | 200 | backup schedules, config values and kv entries of uninstalled deployment {tenant}/{stack}/{environment} not removed{error}, a later deployment of this name reads them, list them with shc doctor run --category database and remove them with shc backup schedule unset and shc config unset --scope deployment -t {tenant} -s {stack} -e {environment} |
X200198BKSARM | 200 | backup schedule {schedule} of uninstalled deployment {tenant}/{stack}/{environment} was deleted but the leader still fires it{error}, stop it with shc backup schedule unset --scope {level} -t {tenant} -s {stack} -e {environment} |
X200199TREKPT | 200 | {path} on this node, which a move set aside of deployment {tenant}/{stack}/{environment}, uninstalled at {deleted_at}, was not removed, {reason}, this node asks again on its agent’s next pass |
X200204RLGCNS | 200 | a hook of {provider} handed tenant {tenant} a login for registry {server}, and tenant {tenant} does not list {provider} in {key}, so no connection was written; list it there to take the login |
X200205RLGHST | 200 | a hook of {provider} handed tenant {tenant} a login for registry {server}, which is none of the hosts {provider} serves ({hosts}), so no connection was written |
X200206RLGOWN | 200 | a hook of {provider} handed tenant {tenant} a login for its connection {name}, and that connection exists and {provider} did not write it, so it is left as it is; remove it to let {provider} write it |
X200207RLGWRT | 200 | a hook of {provider} handed tenant {tenant} a registry login, and writing its connection {name} failed: {error} |
X200208RLGNWR | 200 | a hook of {provider} handed tenant {tenant} a registry login, and this process has no connections service to write it with, so no connection was written; deploy through the daemon |
X200209RLGBAD | 200 | a hook of {provider} printed {markers} that do not parse, so they were left out; the shape is ::shc-hook:registry-login: |
X200210RLGDRP | 200 | a hook of {provider} took tenant {tenant}‘s registry login away, and removing its connection {name} failed: {error} |
X200211SHRCNS | 200 | a hook of {provider} handed {target} a secret, and tenant {tenant} does not list {provider} in {setting}, so nothing was written; list it there to take it |
X200212SHRKEY | 200 | a hook of {provider} handed {target} a secret under {key}, which {reason}, so nothing was written |
X200213SHROWN | 200 | a hook of {provider} handed {target} a secret, and that deployment already holds {key} and {provider} did not write it, so it is left as it is; remove it to let {provider} write it |
X200214SHRWRT | 200 | a hook of {provider} handed {target} a secret, and writing it failed: {error} |
X200215SHRNWR | 200 | a hook of {provider} handed {target} a secret, and this process has no vault to write it with, so nothing was written; deploy through the daemon |
X200217SHRDRP | 200 | a hook of {provider} took {target} away, and removing it failed: {error} |
X200219SHRBAD | 200 | a hook of {provider} printed {markers} that do not parse, so they were left out; the shape is ::shc-hook:secret-share: |
X200221SHRSET | 200 | a hook of {provider} wrote {target} the secret with digest {digest}: {result} |
X200222SHRRNF | 200 | a hook of {provider} wrote {target} a new secret with digest {digest}, and re-rendering {receiver} failed, so it runs on its last render and reports its vault changed until it is updated: {error} |
X200261PUBPND | 200 | deployment {deployment} is running, and its published ports still pending after {waited} are {ports} |
X200262ROUPND | 200 | deployment {deployment} is running, and its routed hosts still wait after {waited} on the fabric policy of {nodes} |
X200277SPCDOC | 200 | replica documents of {tenant}/{stack} not pruned{error}, older versions stay in the vault until the next update or uninstall prunes them |
X200278SPCDOC | 200 | deployment {tenant}/{stack} ({environment}) is removed, its replica documents are still in the vault and will be retried |
X200296PLCRUM | 200 | {tenant}/{stack} ({environment}) is placed without the disk check for its images on what could not be measured: {unmeasured} |
X200303VOLSIZ | 200 | the app now sizes volume {volume} at {asked}, it stays at {current} |
X200304VOLUNK | 200 | the app now sizes volume {volume} at {asked}, it stays at a size SHC has no record of: {reason} |
X200334VOLPEND | 200 | deployment {tenant}/{stack}/{environment} has durable mounts {mounts} still on the node disk while this estate offers block storage, migrate them deliberately, for example {reason} |
X200336VOLLOC | 200 | deployment {tenant}/{stack}/{environment} keeps durable mounts {mounts} on the node disk instead of new block storage, for example {reason} |
X200337VOLRBK | 200 | rollback of failed install for stack {stack} could not release a block volume it created{error} |
X200338VOLHST | 200 | service {service} mounts the host {kind} {source}, which SHC mounts as the data volume {volume} |
X200339VOLKPA | 200 | uninstall of {tenant}/{stack}/{environment} kept {count} block volumes; {command} deletes them all |
X200339VOLKPT | 200 | uninstall of {tenant}/{stack}/{environment} kept block volume {volume} on {provider}, {size}, because {reason}; {command} deletes it |
X200340VOLINR | 200 | service {service} mounts {source}, which the platform provides: {how} |
X200341CMPTRN | 200 | service {service} writes {key}; {did} |
X200346PRVWVR | 200 | {app} service {service} is waived for {class} {value} by its own app.yaml declaration ({reason}) |
X200355OOPWDN | 200 | system openobserve admin password changed for admin user {username}, live password changed, record written, deployment updated |
X200421DPFSTO | 200 | {stack} @ {environment} already exists, so --storage {storage} is ignored, an update keeps the storage its install chose |
X200427JOBPIN | 200 | job run {run} of {deployment} ended but its container could not be confirmed gone, its fabric address stays held until the deployment is uninstalled |
X200428JOBDEP | 200 | a job run of {deployment} could not be confirmed removed at its teardown, its fabric address is released with the deployment’s |
X200441DROPPD | 200 | uninstall of {consumer} dropped {stores} on {provider} |
X200441KEPTDT | 200 | {consumer} left {stores} on {provider}: {why}; a later deployment of this name refuses them until they are deleted |
X200487VLTMNT | 200 | vault keys {keys} the refused install of {tenant}/{stack}/{environment} minted were not removed{error}, remove them with shc vault rm -t {tenant} -s {stack} -e {environment} |
X200538SHYTWO | 200 | {app} has shc.yaml and compose.yaml; shc.yaml is the app and compose.yaml is not read |
X200557INGSRC | 200 | the addresses the system ingress reaches a deployment from did not read, so the render trusts no forwarded header{error} |
X200567STKPHS | 200 | {operation} of {deployment} took {phases} |
X200653GLBCNT | 200 | deployment {deployment}: the replica count of its global services was not recorded{error}, shc ls compares their replicas with the count from before |
X200676LICSEC | 200 | the licence section kept what it served for the {part}, {error} |
X200713UPDSTL | 200 | {consumer}: plug {plug} on {provider} socket {socket} was rendered before this update moved {fields}, shc update {stack} -t {tenant} -e {environment} renders it again |
X200716IMGVOL | 200 | service {service}: the VOLUME paths of image {image} could not be read ({reason}), so this render declares none of them as the deployment’s volumes, and the node keeps each in a volume of the replica’s own that backups and moves do not reach |
X200717IMGREC | 200 | service {service}: the VOLUME paths of image {image} could not be read ({reason}), so this update keeps the volumes the deployment’s record declared for it, as it does on every node |
X200741RSTKEY | 200 | consumer {consumer}: the {plug} edge to {provider} could not be re-keyed after the provider restore: {detail}; the data is restored, retry the consumer’s update |
X200742RSTCNS | 200 | the consumers of restored provider {provider} could not be read: {detail}; the data is restored, consumer socket jobs were not run |
X200745DAPUNR | 200 | the app tree of {deployment}‘s committed render could not be read on this node: {reason}, so nothing of it is read for {reader} |
X200785DNTKEP | 200 | networks {networks} of {deployment} on node {node} keep their subnets after its teardown, {reason}; a teardown that removes them releases the subnets |
X200787UNINTA | 200 | uninstall of {tenant}/{stack}/{environment} takes no safety backup, there is nothing to archive: no node holds a directory of it and the store holds no spec and no volume of it |
X200788DNTHLD | 200 | node {node} holds networks on subnets no deployment network row named: now held in the ledger so no deployment is given them, {held}; released because their network is gone, {released} |
X200789DNTWID | 200 | node {node} has networks wider than a /16 that overlap the deployment network range, {networks}; the ledger cannot hold them, so a deployment network given a subnet they cover is refused by the engine until the network is removed |
X200790DNTENG | 200 | node {node} could not ask its engine which subnets its networks hold, {error}; the deployment network ledger keeps what it holds and the node asks again on its next pass |
X200791RBKRUN | 200 | the failed install of {deployment} is not rolled back yet on {nodes}: its rows are retired and its spec is gone, but those nodes still held a container of it, or could not be asked, when the wait ended; each stops what it holds on its agent’s next pass |
X200804DNSPLX | 200 | hosts of stack {stack} carry ports through {connections}, {reason}, so they publish no private dns record and private clients resolve the public one |
X200805DNSDFO | 200 | newly bound host {hostname} has no dns record yet, its target is not decided this pass, the publish is owed and retried |
X200819INTKEP | 200 | the {plug} edge to {provider}, which this update does not change, failed its socket job and is left as it was; the update goes on: {error} |
X200828INTWAT | 200 | the {plug} edge to {provider} is waiting for {condition}: its socket job {job} said so, and SHC runs it again until it no longer waits |
X200829INTWTF | 200 | the waiting {plug} edge to {provider} ({condition}) was run again and did not finish; SHC tries it again: {error} |
X200900KCISUR | 200 | system Keycloak issuer origin changing {old} -> {new}, live SSO sessions invalidate and consumers must re-render, reconcile is converging, this is not a hard failure |
X200901SHDNSZ | 200 | system host dns resolved zero target specs, nothing registered, retries on the next ingress endpoint change |
X200902SHDNSF | 200 | system host dns record sync for {hostname} failed{error}, retried with backoff until it publishes |
X200903DNSLFT | 200 | managed dns records for host {hostname} were not released ({reason}), they may still be live in the zone |
X200905CLHFLP | 200 | cluster host changing {old} -> {new}, live SSO sessions invalidate and every keycloak-integrated deployment re-renders, the old host stays served until {retire_at} and its dns record is released after that, this is not a hard failure |
X200907TRFHUP | 200 | reloading system Traefik after a dynamic config change failed{error}, routes and certs stay as traefik last read them until the next sweep re-signals |
X200908DNSLAN | 200 | lan-only host {hostname} has no dns record, public connection {connection} never carries its private address {address} and no private dns connection covers its zone, connect one for that zone or redeploy with --public |
X200910CONOVR | 200 | integration plug {plug} requested {field} {requested} but the connection mint provisioned {minted}, using {minted}, the platform names this resource and scopes its credential to that name |
X200911RBKPIU | 200 | rollback of failed install for stack {stack} did not sweep its deployment dir{error}, the pre-image could not be read so the added-entry set is unknown, the deployment dir is left intact rather than risk deleting pre-existing data |
X200912HKSKIP | 200 | pre_update job {job} skipped, service {service} of stack {stack} has no running container to exec into |
X200913PROMIR | 200 | protection flag for {tenant}/{stack} written to the cluster config only, this node holds no deployment sidecar to mirror it onto, a daemonless uninstall on the placement node will not see it |
X200915PRJCOL | 200 | deployment {tenant}/{stack}/{environment} already shares compose project {project} with {other_tenant}/{other_stack}/{other_environment}, a teardown of either destroys the other, rename one of them |
X200916SYSCAP | 200 | module {app} needs {required} CPUs for service {service} but no node measured more than {capacity}. {app} was skipped. shc reconcile installs it once a node with the capacity has joined |
X200921VAPKEP | 200 | vdeployment {stack}/{instance} retained, plug {plug} detaches without removing the instance it declares, remove it with shc uninstall {stack}/{instance} |
X200926KCPWBG | 200 | system keycloak admin password rotation starting for app {app}, trigger {trigger}, steps live reset then record update then redeploy |
X200927KCPWDN | 200 | system keycloak admin password rotation complete for app {app} admin user {username}, trigger {trigger}, live reset done, record updated, deployment redeployed |
X200928VAPDFR | 200 | app {app} plug {plug} requires a {vapp} vapp instance that cannot exist before this first install creates its host deployment, the install proceeds, create it with {fix}, the plug integration converges on the next update |
X200929VAPDWN | 200 | vdeployment {stack}/{instance} declared by plug {plug} is removed together with its host deployment, the uninstall takes every instance on the deployment down |
X200930SOKSVC | 200 | socket {socket} of app {app} names no compose service, neither by matching one nor by declaring an existing one, so its fronting service was guessed as {picked}, the first alphabetically of {candidates}; pin it with service: <name> in {socket}.socket.yaml |
X200931ALICOL | 200 | provider {stack} aliases hostname {hostname} onto both {service} and {other}. Docker DNS round-robins the name and wrong-A connects refuse; give the sockets distinct hostnames or one fronting service |
X200932RSTDIA | 200 | service {service} declares restart: {compose} and deploy.restart_policy implying {deploy}; the restart key governs and the deploy.restart_policy stanza was dropped from this render |
X200934ACCUNR | 200 | deployment of {app} has an unreadable or unverified app.yaml declaration, {reason}, so it renders gated: SSO required, no ungated paths |
X200935UNIMOV | 200 | edge {plug} teardown skipped for deployment {tenant}/{stack}: this is a move leg and the deployment survives at the move target, so its provider-side grants are still in use and were left wired |
X200938UPDBND | 200 | service {service} of {stack} rolls stop-first, not the start-first it states: it binds host port {ports}, which a copy started beside it could not bind |
X200939BKYPKG | 200 | the deployment at {dir} holds no copy of its committed render on this node and its committed spec or stored app archive could not be read: {reason}, so backups and teardowns here read no backup.yaml |
X200941SWMXLT | 200 | app {app} speaks Swarm, translated: {detail} |
X200944ORPNIS | 200 | manifest {path} for {tenant}/{stack}/{environment} has no deployment row, and its render bound something, which only the store holds, or it could not be read; it was not imported, because the row would hold none of its bindings. shc doctor names what it bound; run the recovery, clone or install that made it again with the daemon up, or remove the directory |
X200945ORPTMB | 200 | manifest {path} for {tenant}/{stack}/{environment} predates its uninstall at {deleted_at} and nothing runs under project {project}, so it was not imported; it is a leftover of that uninstall and the directory can be removed by hand |
X200945QTAKNB | 200 | quota knob {key} is set but unreadable and was ignored, the app’s own figures apply |
X200946ORPSTP | 200 | manifest {path} for {tenant}/{stack}/{environment} had no deployment row and nothing runs under project {project}, so it was imported as stopped, not running; if it is a leftover of an uninstall, shc uninstall {stack} -t {tenant} -e {environment} removes it |
X200946QTASRC | 200 | service {service} {axis} quota {value} comes from {source}, not from this deployment |
X200947ORPUNK | 200 | manifest {path} for {tenant}/{stack}/{environment} had no deployment row and this node cannot observe runtime {runtime}, so whether anything runs under project {project} is unknown and it was imported as unknown, not running |
X200947QTACLM | 200 | service {service} authored a {axis} reservation of {authored} above its {source} quota of {quota}; the reservation was lowered to {quota} because docker refuses a limit below a reservation |
X200948ORPLIV | 200 | manifest {path} for {tenant}/{stack}/{environment} predates its uninstall at {deleted_at}, but {objects} still run under project {project}, so it was imported to keep that workload visible; uninstall it again |
X200948QTALRT | 200 | deploy.limit_ratio {raw} is below 1 or unreadable and was clamped to 1.0: a limit under the quota would cap tenants below what they are charged for |
X200949VAPRET | 200 | vdeployment {stack} retained, {jobs} skipped, {reason}, the resources that cleanup would destroy are left in place |
X200950APPUGW | 200 | app {stack} published open with no built-in auth, self_auth is false, anyone reaching it is unauthenticated |
X200951HSTNOA | 200 | {stack} has no web address, give it one with: shc -t {tenant} update {stack} --expose |
X200951VAPUNG | 200 | vdeployment {stack} cleanup job {job} refused, its command is destructive ({verb}) but the vsocket declares no cleanup@boolean guard, the resource is left in place, declare cleanup@boolean in schema.plug to make destruction opt-in |
X200952SCHSYN | 200 | app crons for stack {stack} not reconciled into schedule rows{error}, app-declared crons may not fire until the next successful install or update |
X200953LEAFRC | 200 | ingress served leaf for {host} not recorded {op}{error}, renewal subsystem will not track it until re-served |
X200954HMINTN | 200 | ingress host_mapping intent for {host} not persisted{error}, multi-node reconcile will not materialize this route until recorded |
X200955INGMAT | 200 | ingress reconcile could not materialize {tenant}/{stack}{error}, skipped this sweep retries next tick |
X200955UNILOC | 200 | the deployment row of {tenant}/{stack}/{environment} records node {node}, which holds no deployment directory for it; this node holds one, so the teardown ran here |
X200956CMPNGR | 200 | plug {plug} of {consumer} names {field} {requested}, which tenant {requested} has not opened to this deployment in {key}, so it is given its own tenant’s {field} {tenant} as before |
X200956LEAFRN | 200 | ingress renewal could not re-sign leaf {tenant}/{host}{error}, skipped this sweep retries next tick |
X200956UNINON | 200 | the deployment row of {tenant}/{stack}/{environment} records node {node}, which holds no deployment directory for it, and neither does this node, so the teardown ran best-effort here; a copy on any other node stays until you uninstall there, and the uninstall tombstone keeps it out of the boot import unless something still runs under it |
X200957CMPFLD | 200 | plug {plug} of {consumer} declares {field}, which only an edge into another tenant’s compartment opened by that tenant may carry, so it is left out |
X200957TRFRCR | 200 | traefik dns-01 reconcile recreate of system Traefik failed{error}, skipped this sweep retries next tick |
X200958KCBPRC | 200 | keycloak basePath reconcile recreate of system Keycloak failed deployed {deployed} desired {desired}{error}, skipped this sweep retries next tick |
X200959OOBPRC | 200 | openobserve basePath reconcile recreate of system OpenObserve failed deployed {deployed} desired {desired}{error}, skipped this sweep retries next tick |
X200960NETPRE | 200 | shared network {network} pre-create did not complete{error}, installs will join it once it exists |
X200960SECCHD | 200 | the secrets of {stack} were restaged from this node’s sealed cache because vault provider {provider} did not answer: {cause} |
X200961DNSRTD | 200 | managed dns write for {tenant}/{stack}/{environment} suppressed, its uninstall is releasing those records |
X200961SECCNS | 200 | the secrets of {stack} from vault provider {provider} were staged but not cached on this node, so its containers cannot restart while that provider is down: {reason} |
X200963NETUNW | 200 | provider network {network} is not visible from this host, rendering the consumer without joining it |
X200966KCRORP | 200 | the orphaned keycloak access role ledger could not be persisted for {tenant}/{stack}, role {role}: {reason}. The leaked role will not be retried, reap it by hand |
X200967KCRINH | 200 | fresh install of {tenant}/{stack} could not delete pre-existing keycloak access role {role} ({reason}). It is recorded for retry, but until then this deployment may inherit every grant an earlier deployment of the same name left on it |
X200967NAMDNS | 200 | deployment {id} is named for its software, not its job: it serves {labels}, so the convention name is {suggested}. A stack is named for the DNS label it answers on: docs runs paperless, oncall runs goalert, projects runs huly, and app names are unaffected. Rename it with shc rename {stack} {suggested} && shc update {suggested} AS ONE OPERATION, since a rename does not re-render traefik and the ingress upstreams are literal container names, or record why it must differ with --naming-exception " |
X200968KCRSIB | 200 | the keycloak access role family stack:{stack} was not touched for {tenant}/{stack}/{environment}: {scope}; the family is shared by every environment of a stack, so it is reaped with the last one |
X200968NAMAMB | 200 | deployment {id} serves several DNS labels and matches none of them ({labels}), so there is no single convention name to suggest. Pick the label that names the deployment’s job and rename to it with shc rename {stack} <label> && shc update <label> AS ONE OPERATION, drop the routes that do not belong to it, or record why it fronts several with --naming-exception " |
X200969UNISHR | 200 | unintegration job {job} of edge {plug} was not run: it destroys a provider-side resource identified by {fields}, and environment {environment} of stack {stack} is still deployed naming the same resource; it is retained and will be destroyed with the last environment that uses it |
X200970CONSIB | 200 | connection-minted credentials for {tenant}/{stack}/{environment} were not revoked: {scope}, and the mint is keyed by tenant and app with no environment, so every environment of this stack shares one credential; it is revoked with the last one |
X200970RMVNOP | 200 | {flag} removal {token} matched nothing on this deployment and was ignored, live entries are {live} |
X200971KCUNPN | 200 | system Keycloak KC_HOSTNAME pin {deployed} is being removed, operator declared hostname_pin=unpinned, the OIDC issuer becomes per-request-host and live SSO sessions invalidate while consumers re-discover, reconcile is converging, this is not a hard failure |
X200971UPDHED | 200 | deployment {tenant}/{stack} carries no app version pin, so this update re-renders it from whatever the catalogue currently publishes for {app}: an app revision can change capability, not just version; name a version with shc update {stack} |
X200972RMVDON | 200 | {flag} removal {token} matched this deployment and was applied to its persisted state |
X200972SYSDEB | 200 | module {tenant}/{stack} was pinned to app version {from} and this node now ships {to}, refreshing the pin so the platform re-renders from the app it installed |
X200974UPDCFG | 200 | update of {stack} changes its effective configuration: {delta} |
X200975DURDEL | 200 | uninstall --data of {tenant}/{stack} is destroying mount {mount}, which its backup.yaml lists as persistent data, only a backup or the path that protects it still holds those bytes |
X200977VARUND | 200 | {stack} carries {keys}, which {app} does not declare, so the render reads no such override and the app default applies |
X200980DNSDEF | 200 | exposure=internet but the system ingress has no public endpoint for stack {stack}, dns record deferred until a traefik-node public address via shc node update --public-address or dns.public_address exists |
X200981DNSAMB | 200 | system ingress web listeners span connections {conns} and none is the one edge for stack {stack}‘s location, dns deferred until one is |
X200982DNSPUB | 200 | managed dns record for host {hostname} was not republished{error}, whatever the last successful pass wrote is still what resolves |
X200983DNSVIP | 200 | system ingress connection {conn} has no ready vip yet, dns for stack {stack} deferred until it provisions |
X200983PLGSVC | 200 | plug {plug} pins consumer service {service} which is not in the rendered compose |
X200984DNSIGP | 200 | system ingress port mappings could not be read from the committed deployment spec: {reason} |
X200984PPINTN | 200 | proxied ports intent for {tenant}/{stack} not persisted{error}, leader proxy reconcile will not see this deployment’s LB mappings until recorded |
X200986PRXTRU | 200 | the sources a PROXY v2 port may trust did not read, so the render trusts none{error} |
X200986RBKBCK | 200 | rollback of the failed install of {deployment} did not return it to the spec it had committed because it could not {step}{error} |
X200987DNSNIL | 200 | dns socket edge {plug} declares records but every one of them rendered empty, nothing was written this pass |
X200988SHDNST | 200 | system host dns state could not be {operation}{error}, superseded host releases will retry on the next pass |
X200989ACMPRV | 200 | ingress host {host} can never be issued a public certificate ({reason}), serving an SHC-signed leaf instead of requesting ACME |
X200989DEPPRG | 200 | deployment lifecycle config for stack {stack} not purged after uninstall{error}, a reinstall may inherit a stale lease or protection flag |
X200990DNSOVD | 200 | private dns records on the overlay plane publish {address}, derived from the system traefik node’s address, set dns.lan_address to pin it |
X200990LSESTM | 200 | lease stamp for stack {stack} failed after successful deploy{error}, the deployment has no enforced ttl until re-stamped with shc lease renew |
X200991PROSTM | 200 | protection flag for stack {stack} failed to persist after successful deploy{error}, protection unchanged until re-applied |
X200992LSERTY | 200 | lease reap for stack {stack} failed, attempt {attempt}/{max_attempts}, retrying in {delay_seconds}s, {detail} |
X200993RBKROW | 200 | rollback of the failed install of {deployment} did not run because its replica rows could not be retired:{error}; the nodes that hold them would have kept its replicas running after the rest was removed, so what the install started is left as it is, uninstall {stack} to remove it or install it again |
X200994RBKSPC | 200 | rollback of the failed install of {deployment} kept its replica rows and its stored specs because the store could not say whether it was installed before:{error}; a deployment that was is running, and retiring its rows would stop it |
X200995HSTSKP | 200 | route {route} of {stack} is not served by this render, which leaves out {service}, the service the app declares at that path; the route stays declared and the first render that includes {service} serves it |
X200996HSTDRP | 200 | persisted route {route} on {tenant}/{stack} is not expressible in the current --expose grammar and was dropped from this render, the deployment and its remaining routes are unaffected, re-add it under a path with no exclamation mark if it is still wanted |
X200998APKINT | 200 | archive digest for {tenant}/{stack} not persisted{error}, cluster-wide archive digest reads as unknown for this deployment until recorded |
X200999KCRLFT | 200 | keycloak access role {role} for {tenant}/{stack} was not deleted on uninstall ({reason}), it is still on the shc-access client in realm {tenant}. Delete it, or a reinstall of {stack} inherits every grant on it |
X201002RTMFIX | 201 | deployment row for {tenant}/{stack}/{environment} recorded runtime {was} but its manifest sidecar records {now}, the row has been corrected to {now}, every read taken against {was} since it was written was answered for the wrong engine |
X201004SSORXP | 201 | app {stack} declares an sso_redirect login_path {pattern} that cannot be rendered into a traefik rule, {reason}, no sso auto-redirect router was rendered for this deployment, its login page is served unchanged |
X201005RTELIT | 201 | route {route} on {tenant}/{stack} carries a backtick, which closes a traefik rule matcher and makes the whole route file unloadable, no router was rendered for it and the deployment’s other routes are unaffected, remove the route and re-add it under a hostname and path with no backtick |
X201006INGLIT | 201 | ingress value {value} for {surface} carries a backtick, which closes a traefik rule matcher and makes the rule unloadable, {surface} was not rendered, set a cluster host and module host override with no backtick |
X201007SSOXHS | 201 | app {stack} declares an sso_redirect whose login_path names service {login} and whose sso_start names service {start}, the redirect target keeps only its path and is re-attached to the login page’s own host, so it would resolve to a path that host does not serve, no sso auto-redirect was rendered for this deployment, its login page is served unchanged |
X201008SSOTPL | 201 | app {stack} declares an sso_redirect value {value} still carrying the unresolved expression {leftover}, sso_redirect values are not rendered through jinja, only the literal url() and path() prefixes are substituted, no sso auto-redirect was rendered for this deployment, its login page is served unchanged |
X201009DSHSSO | 201 | dashboardHost {host} is set but the traefik render has no forward-auth sidecar to gate it, the dashboard route was not rendered, install the system keycloak so the traefik oidc integration binds, then shc update traefik |
X201009SSOCLK | 201 | app {stack} declares an sso_redirect sso_click_selector {selector} that may not be rendered, {reason}, no client-side sso click payload was rendered for this deployment, its login page is served unchanged |
X201010DSHLAN | 201 | dashboardHost {host} is set and lanEnforcement is armed but the lan allowlist was underivable ({cause}), the dashboard route was not rendered, name the admitted networks via lanAllowlistCidrs or disarm lanEnforcement, then shc update traefik |
X201011ACMWCH | 201 | ingress host {host} falls inside declared wildcard namespace {wildcard} but resolves over HTTP-01, which cannot validate a wildcard identifier, the host keeps its own per-host certificate order and spends its own slot, configure a DNS-01 capable DNS connection owning its zone to bring it under the wildcard |
X201018ACMWDN | 201 | wildcard route {host} of deployment {stack} in tenant {tenant} is not routed, only a DNS-01 order can certify a wildcard name and {provider} cannot solve DNS-01, give the zone a DNS connection whose provider can |
X201020CTROBD | 201 | container observation for {tenant}/{stack}/{environment} service {service} dropped at container {container}, {reason}, {consequence}, further drops for this deployment are muted for 15m |
X201021SVCRLK | 201 | service row {service} on {tenant}/{stack}/{environment} was relinked to the current deployment row, its previous parent row no longer exists, as with rows predating the store’s current shape, container {container} proved the linkage, the observation proceeds and the deployment’s status follows it, no action needed |
X201022CTROBE | 201 | container observation for {tenant}/{stack}/{environment} service {service} could not resolve its rows at container {container}, {error}, the stored status cannot follow this container until the read succeeds, further failures for this deployment are muted for 15m |
X201023CTRORP | 201 | container {container} is {state} and labelled {tenant}/{stack}/{environment} service {service}, but no such deployment exists, so nothing strands, it is left over from a removed or renamed deployment, docker rm {container} clears it and leaves volumes alone, shc doctor run -c state lists every such container, reported once per daemon start |
X201024MNTDIG | 201 | deployment {tenant}/{stack}/{environment} service {service} binds app content past what the mount digest reads of a bind, {mib} MiB and {entries} entries; past it a file counts by its size and the rest of the bind is not read, so an edit there that keeps the digest does not recreate the service on update |
X201025KCALAN | 201 | system keycloak {host} has lanEnforcement armed but the lan allowlist was underivable ({cause}), its /admin routes keep the last good ranges or the estate’s own networks, fix lanAllowlistCidrs for master/keycloak so the admitted networks derive |
X201026CTRRST | 201 | restarted container {container}, service {service} of {subject}, unhealthy for about {elapsed}, past its wait of {after}, restart {restart} of this episode, the next waits {next} |
X201027CTRRSF | 201 | restarting container {container}, service {service} of {subject}, unhealthy past its restart_after, failed {error} |
X201028VIPNCV | 201 | this node’s routes dial no server until its service VIP state converges, {reason} |
X201029CTRCAP | 201 | container {container}, service {service} of {subject}, has failed its health check through {restarts}, its node now restarts it once every {every} until it passes, the check last said {said} |
X201030KCACON | 201 | {deployment} binds the system keycloak but its fabric addresses are left out of the /admin allowlist, {reason}, they are admitted again once it binds the system keycloak as installed and served now, its committed render reads, and its serviceAccountRoles render from its committed vars alone |
X201031KCACNS | 201 | the system keycloak /admin allowlist admits no consumer’s fabric addresses, {cause}, only the estate’s own networks reach /admin until the bindings, fabric pins and proxy edges read again |
X400004INSTNM | 400 | an instance name is required when installing vdeployment {app_name}, spell the target as --into |
X400005PARNOF | 400 | host deployment {parent_app} must be installed before the vdeployment of vapp {vapp_name} can be installed into it |
X400010APPYML | 400 | app.yaml parse failed for app {name} {error} |
X400016TYPMIS | 400 | socket type mismatch, plug expects {expected} but socket provides {actual} |
X400017SOKDCL | 400 | plug {plug_name} declares socket {declared} but {provider_stack_name} resolved socket {resolved}, point the integration at a provider that serves {declared} or connect the plug that speaks {resolved} |
X400018FLDREQ | 400 | field {field_name} is required but got null |
X400019APPNAM | 400 | app name is required |
X400021RDRURI | 400 | plug {plug_name} on provider {provider_stack_name} rendered redirectUris {rendered}, which cannot mint a safe OIDC client: {why} |
X400023HKNOID | 400 | keycloak socket job refuses to act on realm {realm} client id {client_id}, an empty realm or client id names no client and the admin API answers an empty clientId filter with every client in the realm, declare realm and clientId on the plug or repair the deployment edge state and re-run |
X400024SOKUNS | 400 | plug {plug_name} wants socket {wanted} but provider {provider_stack_name} serves {served}, {hint} |
X400025PLGUNM | 400 | integration with {provider_stack_name} cannot be inferred, the provider serves {served} and the app ships plugs {plugs}, name the plug explicitly with -i |
X400029HKBCURL | 400 | keycloak socket job refuses to register backchannel logout url {url} for client {client_id} in realm {realm}, it is not an absolute http or https url and keycloak would accept it and then never deliver, the attribute is registered empty instead, declare an absolute url on the plug or drop the field |
X400030HKSAPUB | 400 | keycloak socket job refuses to flip client {client_id} in realm {realm} to a public client because it holds a service account that a public client cannot hold, the flip would disarm every client credentials mint with nothing reporting it, the client stays confidential, declare serviceAccount false on the plug if giving the service account up is what was meant |
X400031PRTMAP | 400 | invalid port mapping {value}, expected external or external-service or external-service-container, with optional conn@ prefix and /udp suffix |
X400039CMDREQ | 400 | command is required |
X400044HKSAROL | 400 | keycloak socket job refuses to grant role {role} to the service account of client {client_id} in realm {realm}, it is outside the allowlist this socket shares with keycloakAdmin, remove it from the plug serviceAccountRoles or serviceAccountRealmRoles list |
X400045HKAUDM | 400 | keycloak socket job could not establish audience {audience} on client {client_id} in realm {realm}, the oidc-audience-mapper named shc-audience was not written, so every access token this client mints keeps aud account only and any app validating its own audience will refuse them all |
X400052ADNVRN | 400 | add-on version error, {detail} |
X400054ADNMAL | 400 | add-on file {path} cannot be read, {detail}, an add-on that does not parse is refused rather than skipped |
X400055ADNTYP | 400 | add-on {addon} is authored for {declared} but was named on an install of {requested}, an add-on token never resolves across install targets |
X400056ADNAMB | 400 | {app}/{name} is ambiguous, {name} is both a vapp and an add-on in {app}, spell the add-on {app}/{vapp}/{name} or the vapp instance {app}/{name} with --into |
X400057ADNVAP | 400 | {app}/{vapp}/{addon} names vapp {vapp} but add-on {addon} declares {declared}, an add-on’s vapp comes from its own file, drop the middle segment and spell {app}/{addon} |
X400058ADNINS | 400 | add-on {addon} of {app} is typed against the app itself and installs as a deployment of its own, {stack} names an instance it cannot have, drop --instance and type shc install {app}/{addon} --into {deployment} |
X400060ADNHST | 400 | add-on {addon} of {app} is typed against vapp {vapp} and installs as an instance under a deployment, which --into names and --stack {stack} does not, type shc install {app}/{addon} --into {stack} |
X400063ADNTOK | 400 | add-on target {token} is not |
X400069INVNME | 400 | invalid stack name {name} |
X400070SCLUNV | 400 | cannot verify the declared replica ceiling for {subject} ({source}); refusing the replica change. Run shc update {subject} to re-render the deployment, then retry |
X400072APPRTN | 400 | app {app} declares requires.runtimes [{declared}] and cannot run under the {requested} runtime, install it with --runtime {suggest} |
X400073SCLVAL | 400 | --scale {service}={value} is not a count, |
X400074UNILFT | 400 | unintegration job {job} of edge {plug} declares lifetime:, which SHC no longer reads, the job was not run and the state it undoes is still live; a job that destroys data checks a variable of the integration, such as cleanup on the s3 plug, and integration.protected itself |
X400075HKGRPM | 400 | keycloak socket job could not establish the groups mapper shc-groups on client {client_id} in realm {realm}, so tokens this client mints carry no groups claim and any group-keyed authorization in the app sees no membership at all |
X400075SRCAMB | 400 | install source {source} with stack name {stack} is ambiguous, {reason}; a slash is <parent_stack_app>/ |
X400078INSACT | 400 | install refused, the request stated installed_by {actor} and {reason} |
X400080HKROLM | 400 | keycloak socket job could not establish the roles mapper shc-roles minting claim {claim} on client {client_id} in realm {realm}, so every token this client mints reaches the app carrying no realm roles and any authorization keyed on that claim resolves to nothing |
X400082HKOAUD | 400 | keycloak socket job could not establish optional audience {audience} on client {client_id} in realm {realm} via optional client scope {scope}, so a token-exchange grant that names that audience is refused and the consumer cannot act as the user against the target |
X400083PODSCL | 400 | the pods of {subject} cannot scale as asked: {reason} |
X400085PODPRJ | 400 | {deployment} cannot render as one compose project per replica: {reason} |
X400087PODRTM | 400 | {deployment} cannot run on this node: its runtime {runtime} cannot run {service}: {reason}; a node of a runtime that can run it would take it, which --runtime states, and so would an app without what {runtime} refuses |
X400091JOBORD | 400 | {deployment} cannot order its start: {why} |
X400092IDNVAL | 400 | plug {plug_name} field {field} is {value}, which is not an identifier: the provider’s integration jobs name a database object with it, so it must match {pattern}: a letter or underscore, then letters, digits and underscores, up to 63 characters. Pick a name in that set |
X400093GRPMAX | 400 | group {group} of {subject} takes at most {max} members, not {asked} |
X400094GRPSHP | 400 | group {group} of {subject} takes a count or counts per place, not {value} |
X400095GRPSVC | 400 | {subject}: --scale {name} names a service group {group} stamps; scale the group: --scale {group}= |
X400096GRPDUP | 400 | group {group} of {subject}: {detail}; a group and a service may not share a name |
X400097GRPEMT | 400 | group {group} of {subject}: {detail}; a members block sits inside services: and stamps services |
X400098GRPLNK | 400 | {subject}: service {service} shares a namespace or volumes with {other}, which is not in its member |
X400099GRPREP | 400 | {subject}: service {service} of group {group} states {replicas} replicas; a member runs one copy of each of its services, any other count is not supported yet |
X400100HKATTR | 400 | keycloak socket job could not establish the userinfo attribute mapper for {attribute} on client {client_id} in realm {realm}, so the app’s userinfo answer carries no {attribute} claim and whatever the app keys off it sees nothing |
X400101HKCROL | 400 | keycloak socket job could not establish the client roles {roles} of client {client_id} in realm {realm}, or put the default ones in the realm’s default role, so a token this client mints lacks a role the app reads |
X400103ARCREQ | 400 | app {app} supports only {required} but every candidate node is {available}, its images cannot run on this estate, add a node with a supported architecture |
X400126CMPNRM | 400 | {deployment}‘s rendered compose cannot run as written: {reason} |
X400127ENVINH | 400 | {deployment}‘s service {service} takes {key} from the environment the engine runs with: {reason} |
X400132STKQRY | 400 | shc.stack.status refuses name, use stack_name |
X400138PUBSEL | 400 | listen selector {selector} does not resolve: {reason} |
X400140RTMSWM | 400 | runtime {runtime} is not supported, the runtimes are docker, podman, incus and apple |
X400143PRFDEP | 400 | service {service} depends on {dependency}, which runs only when its profile {profile} is selected |
X400144LBLFIL | 400 | service {service} reads labels from {path}, which SHC cannot read: {why} |
X400145ADNTWO | 400 | add-on targets take one |
X400151PRTHST | 400 | hostname {hostname} is shared by ports {ports} whose targets differ, give each port its own hostname or one shared listen |
X400153VARJSN | 400 | app {app} declares json vars that hold values that are not a JSON object or list, {vars}, write each as one JSON object or list |
X400156VARSEL | 400 | app {app} vars hold values outside their declared options, {vars} |
X400157VARSLD | 400 | app {app} declares select vars that cannot be offered as a pick, {vars} |
X400158VARUID | 400 | app {app} declares uuid vars that hold values that are not UUIDs, {vars}, use the 8-4-4-4-12 form |
X400161TRFHDR | 400 | app {app} cannot log the access-log headers it is given, {reasons} |
X400178INSNOD | 400 | an install does not name a node ({node}), say where the deployment may run with a rule, for example --where node={node} |
X400191DEPLBL | 400 | label {key} is SHC’s: SHC derives it, so no operator sets it |
X400212PUBPRV | 400 | --expose {mapping} sets +private on connection {connection}, whose edge decides who reaches the port; a connection publish already listens on the node’s private address, so drop +private or the connection |
X400223SCLLOC | 400 | --scale {service}={value}: {location} names no place, no node is in a location by that name; the locations are: {known} |
X400224SCLAMB | 400 | --scale {service}={value}: {location} could be any of the locations {candidates}; name one of them in full |
X400226FLGOLD | 400 | {flag} is gone, write {now} |
X400227OVRSVC | 400 | {flag} names nothing {app} has, {known} |
X400229SCLENT | 400 | --scale {entry} is not |
X400240PODNET | 400 | {deployment}: service {service} joins the network namespace of {owner}, which has no fabric address for {service} to be reached at; {owner} must be a service of this app on the deployment’s network, not one that sets network_mode itself |
X400241PODPUB | 400 | port {mapping} cannot publish container port {port} of {deployment}: {reason} |
X400242PODADR | 400 | {deployment}: {target} names service {service}, whose network_mode {mode} leaves it no address of its own and no VIP, so nothing routed or published to it can reach it; route or publish a service on the deployment’s network |
X400242SCLGON | 400 | the scale hook action is gone, use stop: and start: |
X400256INTSEL | 400 | {file} sets {key}; a socket or plug is bound by name, never by a selector |
X400259BKPFRM | 400 | backup of {subject} refused: converter {converter} reads one member from {from}, and {reason} |
X400262BKPJPH | 400 | {app} refused: its backup.yaml lists jobs under {phase}, which the backup does not run from that file; a {phase} step is an app.yaml hook with a |
X400273STKOLD | 400 | --stack {stack} is gone, write --into {deployment} --instance {instance} |
X400274INSREQ | 400 | --instance {instance} needs --into |
X400276INTOBT | 400 | --stack {stack} and --into {into} cannot both be set, the deployment a vdeployment attaches to is --into |
X400302BNDSRC | 400 | service {service} mounts {mount}, and the app directory has no {path}, nothing was changed |
X400303STGVAL | 400 | --storage {value} is not {grammar} |
X400304STGVOL | 400 | --storage names volume {volume}, which {app} does not declare, and {app} declares {declared} |
X400305STGBKE | 400 | --storage names backend {backend}, which this cluster does not have, and the cluster has {backends} |
X400307STGBND | 400 | --storage puts volume {volume} on {backend}, which cannot bind a block volume on this cluster |
X400330XSHUNK | 400 | compose declares {key} at {path} which is not an SHC directive and will be ignored{hint} |
X400331XSHLVL | 400 | compose declares {key} at {path} but SHC reads it {want} only |
X400332XSHFLD | 400 | {key} at {path} declares unknown field {field}, it reads {known} |
X400333XSHVAL | 400 | {where} at {path} cannot be honoured as declared, {why} |
X400339DURCON | 400 | backup.yaml lists mount {mount} under both include and keep, a backup either copies a mount or leaves it to the path that protects it, remove it from one list |
X400341VDCUNK | 400 | {file} declares {key} at {where}, which SHC does not read and will silently ignore; it reads {known}{hint} |
X400342VDCSHP | 400 | {file} declares {where} as {got}; SHC reads it as {want}, so as written it decodes to nothing |
X400343INTPHS | 400 | {file} declares jobs.{phase}, which no runner executes and the parse silently discards; this surface runs {known}{hint} |
X400343INTSHP | 400 | {file} declares {where} as {got}; SHC reads it as {want}, so as written it decodes to nothing |
X400345DURSHP | 400 | backup.yaml {subject} {problem} |
X400346PLCDST | 400 | {file} serves {iface}, a data store, without placement.colocate; name the fence kind its consumers share: node, location or none |
X400346PLCEXC | 400 | {file} fronts an external provider and colocates by {kind}; an external provider is no node, so it colocates by location or none |
X400346PLCEXL | 400 | {file} fronts an external provider without placement.location; name the fence it lives in from a var, which may render empty |
X400346PLCKEY | 400 | {file} declares placement.{key}, which SHC does not read; placement takes {known} |
X400346PLCKND | 400 | {file} colocates by {kind}; a catalog app may name only node, location or none, since custom fence kinds differ per estate |
X400346PLCRSN | 400 | {file} loosens {iface}‘s colocation from {def} to {kind} without placement.reason; say why its services need not run near the socket |
X400346PLCSHP | 400 | {file} declares placement as {got}; SHC reads a mapping of colocate, location and reason, each a string |
X400346PLCSVC | 400 | {file} dials {iface}, colocated by {kind}, without a services list; the rule binds only the services the plug lists |
X400346PLCSVN | 400 | {file} lists service {service}, which the app’s compose does not declare |
X400348PRVSCK | 400 | privileges.docker_socket is {value}, and the scopes are self and full |
X400348PRVWVB | 400 | privileges.waivers entry for service {service} is not a valid waiver, {detail} |
X400350INTSEL | 400 | {file} declares {key}: on jobs.{phase} job {job}; a plug or socket job takes no selector, it runs where its integration’s endpoint runs |
X400353OOUSRN | 400 | the system openobserve’s admin user is [email protected], the user the exporter, the collector and the telemetry reads sign in as, and username {username} would create it under another name that none of them signs in as; remove the modules.openobserve.vars.username row or the --var that sets it, nothing was changed |
X400354OOPREF | 400 | every platform reader reads the system openobserve’s admin password from ref+vault://password, and {ref} names a secret none of them reads; give modules.openobserve.vars.password a literal, which is sealed into that record, or remove it, nothing was changed |
X400357LBLSHC | 400 | service {service} writes the label {key}, which is the platform’s; a behaviour is a compose key |
X400358LBLTRF | 400 | service {service} writes the label {key}; routes come from --expose |
X400359LBLRSV | 400 | service {service} writes the label {key}, which SHC derives for every replica |
X400360OOPWRF | 400 | the system openobserve refused the new admin password, it answered {answer}; nothing was changed |
X400361INTFLD | 400 | {file} declares {key}: on jobs.{phase} job {job}, which no runner reads; the fields it reads are {known} |
X400363APPKEY | 400 | {file} declares {key}:, a top-level key no reader looks for, so it would do nothing{hint} |
X400366SYSEXP | 400 | {app} in the master tenant is published by its system route, not by --expose: set its public host with shc config set modules.{app}.host <host>, give the cluster a host with shc cluster host set <domain> if it has none, and install it without --expose |
X400369RSZUNR | 400 | {deployment} service {service} {field} {value} is not a size compose runs |
X400370REPCNT | 400 | service {service} {field} {value} is not a replica count compose runs |
X400406DPFPRS | 400 | deployfile {path} could not be read: {detail} |
X400408DPFREQ | 400 | deployfile {path}: {what} is missing or unusable: {why} |
X400409DPFENV | 400 | deployfile {path} declares no environment {environment}; it declares {declared} |
X400410DPFVAR | 400 | {where} references the variable {name} which is not defined. An undefined variable is a refusal, not an empty value ({remedy}) |
X400411DPFSLG | 400 | deployfile {path}: environment review needs --slug: the review host is |
X400412DPFAPP | 400 | deployfile {path}: app {app} not found, resolved from the working directory {wd} as the CI generator resolves it |
X400414DPFENF | 400 | --env-file {path} could not be read: {detail} |
X400418DPFTNT | 400 | deployfile {path} declares tenant {fileTenant} but the command line names {flagTenant}. A deployment is keyed by tenant, stack and environment, so this is two answers to one question; drop the -t, or deploy the file that belongs to {flagTenant} |
X400418UPDABD | 400 | update of {stack} abandoned at the variables form: nothing was sent and nothing changed; the form asked for {vars}, so re-run without --interactive supplying them with --var, or answer it |
X400419DPFVER | 400 | deployfile {path}: the key {key} is not in the schema this shc understands ({schema}): either it is a typo, or the file was written for a newer shc: catalog, repo, version, tenant, integrate and gated need shc {since} or later |
X400419VARMIS | 400 | {subject} requires {missing} not provided by this command: {vars} |
X400420DPFINT | 400 | deployfile {path}: {key} = {provider} is not a usable provider reference: {why} |
X400420RPTAPP | 400 | repoint needs a catalogue app to move onto: name it as shc repoint <stack> <app>[@<version>], or pass --back to return the deployment to the source it was repointed off |
X400421RPTSRC | 400 | repoint target {token} is a {kind} source. Repoint moves a deployment onto a source whose drift can be seen, a catalogue app or a git remote at a ref, and moving it to a path or an archive leaves it exactly as invisible to drift as it is now; install from a path with shc install --from |
X400422RPTCMP | 400 | the app at {dir} has no readable compose.yaml services ({error}), so the service and volume sets this repoint would change cannot be compared, and two apps that could not be compared have not been shown to agree |
X400427DPFCYC | 400 | the deployfiles wait on each other in a cycle: {cycle}. A deployment waits for every deployment in the set its integrate: names, so none of these could start; remove one of these integrate: lines |
X400428DPFSET | 400 | deployfiles {first} and {second} both deploy {stack} in tenant {tenant}, environment {environment}; a set deploys each deployment once, so drop one of them |
X400429DPFDOT | 400 | deployfile {path}: {key} is a dotted key, and vars nest like an app’s vars.yaml: write {nested} |
X400471INTPRV | 400 | integration provision takes one -i |
X400472APPUPL | 400 | the uploaded app does not unpack into a tree: {error} |
X400490EXPFMT | 400 | --expose {entry} is not usable: {reason} |
X400492EXPOPT | 400 | --expose {entry} names unknown option +{option} |
X400493EXPATR | 400 | --expose {entry} puts @ on a Traefik route, which has no meaning yet; drop the @ or write an L4 port |
X400495EXPPTH | 400 | --expose {entry} puts a path on an L4 port, and a port has no path |
X400496EXPLSP | 400 | --expose {entry} sets +local and +spread, but +local never forwards to another node and +spread sends to any node’s replica; keep one |
X400497EXPWLD | 400 | --expose {entry} names the wildcard host {host}, and a wildcard host is one whole leading * label over a domain of at least two labels, like *.pages.example.com |
X400498EXPTGT | 400 | --expose {entry} targets {target}, which is neither a service nor a service selector of this app, its services are {services} and its service selectors are {service_selectors} |
X400499EXPVIP | 400 | --expose {entry} publishes service selector {service_selector}, which answers only at its service VIP, and this cluster runs no service VIPs |
X400530SHYUNK | 400 | {app} shc.yaml: {where} writes {key}, which is not a shc.yaml key{hint} |
X400531SHYCMP | 400 | {app} shc.yaml: {where} writes {key}, a compose key shc.yaml does not take{instead} |
X400532SHYXSH | 400 | {app} shc.yaml: {where} writes {key}, and shc.yaml has no x-shc keys{instead} |
X400533SHYPRT | 400 | {app} shc.yaml: {where} exposes {port}, which is not a listening port; expose takes a port or port/protocol and a deployment publishes it with --expose |
X400534SHYHST | 400 | {app} shc.yaml: {where} mounts the host path {source}; a mount is a named volume, an app file (./…) or a platform mount (/etc/shc/…) |
X400535SHYVAL | 400 | {app} shc.yaml: {where} sets {key} to a value SHC cannot honour: {why} |
X400536SHYPRV | 400 | {app} shc.yaml: {where} writes {key}, {why} |
X400537SHYDOC | 400 | {app} shc.yaml is not one YAML mapping SHC can read: {why} |
X400539SHYCNV | 400 | {dir}: compose.yaml cannot be converted to shc.yaml: {why} |
X400553UPDRBS | 400 | {deployment} cannot roll back, the settings its kept spec records could not be read: {error} |
X400554UPDRBX | 400 | --rollback puts a kept spec back whole and takes no other change: drop {flags} |
X400556UPDRNW | 400 | --rollback-on-failure rolls back when the update’s rollout fails, so it waits for the rollout; drop --no-wait |
X400562SHCREQ | 400 | app {app} needs SHC {required} or newer and this node runs SHC {running}, upgrade SHC on this node or install a version of the app that runs on it |
X400563SHCVER | 400 | app {app} declares requires.shc {required}, which is not an SHC release version X.Y.Z, so no node can run it |
X400601BKPUND | 400 | {app} refused: it declares volumes {volumes} and ships no backup.yaml; list what a backup copies under include, or ship an empty backup.yaml when there is nothing to back up |
X400603BKPCNV | 400 | {app} refused: backup.yaml converter {converter} reads mount {mount}, which include does not list; a backup that does not run the converter copies the mount itself, so list it under include |
X400713HLTPRB | 400 | service {service} declares an SHC health probe that cannot run: {reason} |
X400714RPLUSE | 400 | {deployment}: {file} line {line} reads replica in {tag}, {reason} |
X400715RPLKEY | 400 | {deployment}: {what} prints replica, which SHC reads before a replica is finished, print it into environment, command, entrypoint, healthcheck, hostname, working_dir or labels |
X400725UPDCFG | 400 | app {app} sets an update this cluster cannot roll: {detail} |
X400740PLGSTEM | 400 | integration name {plug} is not a consumer plug stem, write -i |
X400742PLGACC | 400 | plug {plug} accepts only {accepted} as its provider but {provider_stack_name} runs {runs}, bind it with -i {plug}= |
X400743PLGPRV | 400 | {file} declares providers as {got}; SHC reads a non-empty list of distinct app names, the provider apps this plug accepts |
X400779EXEHKJ | 400 | runtime {runtime} cannot run the {hook} job {job}, a {context} job runs through the compose CLI only, nothing was deployed |
X400782DNTIPM | 400 | network {network} of {deployment} sets its own {field}, the render allocates every deployment network’s subnet and MTU on the node it lives on, take {field} out of the app’s compose |
X400793CNVEXP | 400 | app {app} backup.yaml converter {converter} refuses expect entry {entry}: {detail} |
X400797RTMKEY | 400 | {deployment}: {what} differs by shc.runtime: {reason} |
X400808ABNGON | 400 | {flag} is gone, nothing binds a deployment to a provider by itself, a plug is bound only by -i |
X400809LFTGON | 400 | {flag} is gone, SHC keeps no edge lifetime: a socket’s unintegration job destroys what it provisioned only when a variable of the integration says so, such as cleanup on the s3 plug; drop the flag |
X400832VARINPUT | 400 | variable {key} is not declared by {app}, run shc show {app} to list its variables |
X400842PRFNAM | 400 | --profile {name} is not a compose profile name: a letter or digit, then letters, digits, ’_’, ’.’ or ’-‘ |
X400843CFGNDC | 400 | config {config} is used by a service and no top-level configs entry declares it |
X400845CFGONE | 400 | config {config} needs one of file or content |
X400846CFGPTH | 400 | config {config} has a file key that names no path |
X400847CFGTXT | 400 | config {config} has content that is not text |
X400848CFGSUB | 400 | config {config} {reason} |
X400849CFGNAD | 400 | config {config} has a file relative to the app directory and this render has none |
X400857CFGOUT | 400 | config {config} has a file that is not under the app directory |
X400877DSKPLG | 400 | app {app} declares no {plug}.plug.yaml, so the {token} socket has nothing to serve this edge; either add the declaration or drop the -i {plug}={token} bind |
X400878DSKFLD | 400 | app {app} plug {plug} authors field {field} which the {token} socket contract does not declare, fix the field name or remove it |
X400902SCLMAX | 400 | service {service_name} declares x-shc-scale.max {max}; refusing to run {requested} replicas: more than one writer against its volume forks the dataset. Run {max} or fewer with shc update <stack> --scale {service_name}={max}, or raise the ceiling in the app’s compose.yaml and re-install |
X400903INVAPP | 400 | invalid app definition with {detail}{error} |
X400907DEPENV | 400 | environment is required to delete a deployment: stack {name} in tenant {tenant} occupies {environments}, name one with ?environment= |
X400909PRTDFT | 400 | --expose {outside} names no service or port, so it goes to the app’s default service, and {reason}. Name the target in --expose {outside}= |
X400914TMPFAL | 400 | template rendering failed for {name}{error} |
X400935CLHNEW | 400 | cluster host {host} is not usable as the estate’s serving domain, {reason}, nothing was changed |
X400936HSTNOP | 400 | no ingress candidate matches selectors {selectors}, write --expose |
X400937HSTAMB | 400 | multiple ingress candidates match {candidates}, write --expose |
X400938HSTPRM | 400 | services {services} each declare x-shc-primary, only one service may be the primary ingress target because compose services are an unordered mapping and picking one would route differently between renders, delete the marker from all but the front door |
X400939HSTPRP | 400 | service {service} declares x-shc-primary but no container port can be elected for it, {reason} |
X400940HSTSEC | 400 | service {service} declares a secondary ingress path that cannot be honoured, {reason} |
X400941HSTSCL | 400 | services {services} each declare x-shc-path {path}, two services cannot serve one path on the same hostname because compose services are an unordered mapping and picking one would route differently between renders, delete the marker from all but the service that owns the path |
X400941SWMVOC | 400 | app {app} speaks Swarm in a way this cluster has no form for: {detail} |
X400942SECSRC | 400 | secret {secret} must come from the vault alone: declare it as x-shc-vault: ref+vault://<key>, a file or environment secret would sit on disk or in the compose |
X400944CFGHST | 400 | config {config} takes its bytes from {source}, which does not travel with the project to the node that runs it; inline them with content: |
X400945SECNAM | 400 | secret name {secret} must be letters, digits, dot, dash or underscore, starting with a letter or digit |
X400952STKREQ | 400 | stack name required |
X400954XNDSCK | 400 | integration with local-only socket {socket_name} cannot span nodes, provider on {provider_node} |
X400960CONDTY | 400 | app {app} connection declaration {name} has unknown type {type}, declare a type the connections registry knows |
X400961CONBND | 400 | app {app} declares no connection named {name}, declared {declared}, bind with -C name=connection |
X400963SEEDEC | 400 | app {app} seed_once declaration is incomplete, {problems} |
X400964VARIDN | 400 | app {app} refuses to rewrite identifier vars during a move, {vars}, an identifier is an identity and changing it is a new install not a move |
X400965CONAMB | 400 | bare -C {connection} needs exactly one declared connection in app {app}, declared {declared}, use -C name=connection |
X400966VARURO | 400 | app {app} declares url vars with no role, {vars}, qualify each as name@url: |
X400967VARROL | 400 | app {app} declares unknown variable roles, {vars}, use one of {roles} |
X400968VARBOL | 400 | app {app} declares boolean vars that hold non-boolean values, {vars}, use true or false |
X400969VAPREQ | 400 | app {app} plug {plug} requires a {vapp} vapp instance on its own deployment and none matches, create it with {fix} |
X400972INTAMB | 400 | integration removal {token} addresses more than one persisted row ({matches}), which share one identity and so cannot be told apart by any token, nothing was removed, this deployment’s integration state is inconsistent and a plain shc update normalises it |
X400973INTPLG | 400 | integration {provider} cannot be resolved to one consumer plug, the provider offers {sockets} and this app declares {plugs}, name the plug explicitly with -i plug={provider} |
X400974HSTIDN | 400 | route removal {token} names a service or container port selector, a route is removed by its identity {identity} only |
X400975STKNAM | 400 | stack name {name}, {reason} |
X400976ENVNAM | 400 | environment name {name}, {reason} |
X400978VARREQ | 400 | app {app} required vars not set, {vars}, supply them via --var, an add-on, or an integration |
X400984PRTNOP | 400 | no service exposes container port {container_port}{service_selector}, cannot resolve the port’s target |
X400985PRTAMB | 400 | multiple services expose container port {container_port}, {services}, name the service in --expose |
X400986DNSPLG | 400 | app {app} declares no {plug}.plug.yaml, so the dns socket has no records to write; either add the declaration or drop the -i {plug}=DNS bind |
X400986PRTCON | 400 | connection {conn} of type {type} has no proxy capability, port {mapping} needs a proxy-capable connection |
X400986PRTHDR | 400 | port {mapping} publishes the system traefik on connection {conn}, which sends no PROXY header, so every client would reach traefik as the load balancer; set proxy_protocol=v2 and edge_addresses on {conn} |
X400986PRXNOH | 400 | port {mapping} reaches {service}:{container}, which declares app_protocol: proxy-v2 and reads a PROXY v2 header, and connection {conn} sends none; set proxy_protocol=v2 and edge_addresses on {conn} |
X400986PRXPLN | 400 | port {mapping} reaches {service}:{container}, which declares app_protocol: proxy-v2 and reads a PROXY v2 header, so only a load balancer that sends one can publish it; publish it through a connection with proxy_protocol=v2 |
X400987PRTUDP | 400 | proxy connection {conn} backend {impl} is tcp-only, port {mapping} cannot forward udp |
X400988PRTDUP | 400 | port {external} on shared-vip connection {conn} is already claimed by deployment {stack} environment {environment} |
X400989PRTALO | 400 | no free node port in {min}-{max} for port {mapping} |
X400989PRTPRV | 400 | port {mapping} on connection {conn} has no node to reach: its edge listens on a node’s private underlay address and no node in {location} has one |
X400990PRTFIX | 400 | connection {conn} backend forwards without port remap, port {mapping} needs node port {external} which is already published |
X400991PRTIDN | 400 | port removal {spec} names a service or container port, a mapping is removed by its identity {identity} only |
X400991SECRPL | 400 | replica {replica} is not one path element, so its secrets cannot be staged |
X400992HSTEXP | 400 | persisted route {route} cannot be expressed in the current --expose grammar, no --expose spelling can name it, run shc update on the deployment once to drop it from the deployment state and then re-add the route under a path with no exclamation mark |
X400992PRTOWN | 400 | port {port}/{protocol} is {service}‘s on this node; publish another port |
X400992SECNSC | 400 | replica secrets were asked for the deployment’s own set |
X400993HSTFMT | 400 | invalid --expose declaration {value}, expected |
X400993PRTADR | 400 | connection {conn} has no addresses to choose from, write the port without :{address} |
X400994PLGREQ | 400 | app {app} required plugs not connected, {plugs}, connect each with -i plug=provider or point its vars at an external service via --var |
X400994PRTONE | 400 | ports on connection {conn} name both {first} and {second}, a deployment holds one address of a connection |
X400995DLGBAD | 400 | device_login declared by {declarer} is not published on {domain}: {reason}, the rest of the document still publishes |
X400995HSTTGT | 400 | host {host} uses the removed =target override {target}, drop the suffix, dns follows the system ingress endpoint |
X400996LSEPRT | 400 | lease operation on stack {stack} refused, environment {environment} is protected, pass --force to override |
X400997HSTSEL | 400 | route {declaration} uses a retired selector spelling, write it as {canonical} |
X400997LSETTL | 400 | invalid ttl {ttl}{error}, expected a duration like 72h or 30m |
X400998TPLUND | 400 | app {app} compose references undefined values, {refs}, guard each with a default filter or supply the value |
X400999CONREQ | 400 | app {app} required connections not bound, {connections}, bind each with -C name=connection or point its vars at direct credentials via --var |
X403144RNDLDR | 403 | {deployment} is finished for node {node} only by the leader, and this node does not lead |
X403215APPVTR | 403 | refusing to place a tenant workload on voter {node} while a non-voter exists. Pass --where to select a non-voter, or install as tenant master |
X403293VOLFRM | 403 | {deployment} service {service} mounts another container’s volumes through volumes_from {entry}, which no backup reads, so declare the volume in this deployment and mount it |
X403332CBRRTM | 403 | node {node} runs {runtime}, which has no Docker API for the deployment’s broker socket |
X403369POLRWT | 403 | {deployment} {subject} field {field} holds a value compose rewrites after the render read it |
X403950INSGRT | 403 | installing into environment {environment} of tenant {tenant} needs the role {role} or install, which a tenant admin grants with shc user grant <user> {role} --tenant {tenant} |
X403974IMGEEO | 403 | module {app} image {var} is set to {override} but SHC ships {shipped}, substituting an image that carries SHC’s own enforcement code requires an SHC Enterprise licence with the custom_images entitlement, to serve that same image from your own registry keep the @sha256 digest and change only the host or path, mirroring is free on every tier |
X403976ENVEEO | 403 | named environment {name} requires an SHC licence with the environments capability, Hobby tier and up; community edition deploys everything into the default environment |
X403978SYSTNT | 403 | app {app} cannot deploy into the {tenant} tenant, {tenant} is reserved for SHC’s own modules, install it into a tenant of your own with -t |
X403979SYSSRC | 403 | module {app} cannot be installed into the master tenant from {origin}, SHC’s own tenant deploys SHC’s own packaging, install your build into a tenant of your own with -t |
X403980SYSENV | 403 | module {app} cannot deploy into environment {environment} of the master tenant, SHC’s own tenant runs in the {baseline} environment only and an install into it needs no -e at all, install it with no -e or with -e {baseline} or install into a tenant of your own with -t |
X403981BLTTNT | 403 | {app} declares kind: module and cannot deploy into tenant {tenant}, {app} is part of SHC’s own platform and runs once in the {system} tenant, which every tenant already reaches, install the platform copy with -t {system} if it is missing, or consume it from your tenant with an -i integration or a tenant-scoped instance where the app offers one via shc install {app}/ |
X403982LDPEEO | 403 | integration with the ldap socket on {provider} requires SHC EE with the sso entitlement, outbound LDAP serving is a paid identity capability and community edition establishes no new ldap edges |
X403987DNSPRK | 403 | DNS publish for {hostname} is parked until its hourly retry or inputs change |
X403989XIDEEO | 403 | integration with the {socket} socket on external identity provider {provider} requires SHC EE with the sso entitlement, community edition wires oidc and saml to the bundled keycloak only and establishes no new external identity edges |
X403994TNTSRC | 403 | a tenant install cannot use the {kind} source {source}, {reason} |
X403995DLGTIR | 403 | device_login declared by {declarer} is not published: only a system-tier deployment, in the master tenant and the platform environment, may declare it |
X403995PKGLNK | 403 | app {app} carries the link {link}, which resolves outside the app, a tenant’s app may only link within itself |
X403996TNTCMP | 403 | app {app} cannot run as a tenant’s app, {detail} |
X403997TNTPRT | 403 | port {mapping} cannot be published by a tenant, {detail} |
X404002APPNOF | 404 | application {name} not found |
X404006SOKNOF | 404 | socket {socket_name} not found in {stack_name} |
X404007PLGNOF | 404 | plug {plug_name} not found in {stack_name} |
X404012APPDIR | 404 | app {name} not found, looked under {candidates} |
X404013APPDPF | 404 | app dir not found, {path} |
X404014MANNOF | 404 | no deployment manifest found at {dir} |
X404015APPKPT | 404 | the app deployment {deployment} keeps could not be read, {reason} |
X404019ADNNFD | 404 | add-on {addon} not found, available add-ons, {available} |
X404021ADNEMP | 404 | no add-ons published in {location} |
X404022ADNPIN | 404 | plug {plug} pins vapp {vapp} add-on {addon} to version {version} which the catalog cannot serve{error}, a pin is never silently moved, fix the pin or ship the version in the add-on file |
X404041APPVSEL | 404 | app {name} has no version {version} in this node’s catalogue{error}. shc catalog show {name} lists what it serves, and shc repo sync (read-only) refreshes the index |
X404064SRCNFD | 404 | source path not found {path} |
X404070VDPNOF | 404 | vdeployment {instance} not found on host {host} in environment {environment} |
X404143RNDNOF | 404 | {deployment} cannot be finished for node {node}: its stored spec carries no stored render, so nothing renders it there; reinstall or update it to store one |
X404464INTPLG | 404 | {deployment} has no {plug} plug that {provider} serves: {reason} |
X404906STKNOF | 404 | stack {name} not found in tenant {tenant} environment {environment} |
X404907DEPNOC | 404 | stack {name} is not deployed in tenant {tenant}: it occupies no environment |
X404907RPTBCK | 404 | deployment {stack} has no recorded repoint to go back to: --back undoes the last repoint and this deployment has not had one; name the app to move onto instead |
X404946UNINDH | 404 | node {node} holds no deployment directory for {tenant}/{stack}/{environment}, so it tore nothing down |
X404990SECLDR | 404 | secret {secret} is not in the vault yet; it is minted by the leader’s render, and this node does not mint it |
X409001DEPROT | 409 | deployment {tenant}/{stack} is protected, unprotect it before destroy |
X409002DEPUNK | 409 | protection state of deployment {tenant}/{stack} could not be determined{error}, refusing destroy |
X409003STKEXS | 409 | stack {name} already exists in environment {environment} |
X409004PRJCOL | 409 | deployment {tenant}/{stack}/{environment} would share compose project {project} with existing deployment {other_tenant}/{other_stack}/{other_environment}, tearing down either one would destroy the other, choose a name that does not fold onto it |
X409004RPTSVC | 409 | repoint of {stack} onto {app} refused: the catalogue app renders a different shape than the deployment is running ({delta}), so the next shc update would create or destroy containers, or bind this deployment’s data somewhere else; run shc repoint {stack} {app} --diff to read the whole difference, and re-install under a supervised window rather than repointing if the change is intended |
X409005HKGATE | 409 | pre_update hook refused the update of stack {stack} in tenant {tenant} environment {environment}, the new version was never started and the deployment still runs the previous one, resolve what the hook reported and re-run the update{error} |
X409007DEPNOA | 409 | pre-uninstall safety backup for {tenant}/{stack} produced no usable archive, {evidence}, refusing teardown, pass --no-backup to tear down without one |
X409008DEPNOG | 409 | no pre-uninstall safety backup can be taken for {tenant}/{stack} on this build, the backup service is not wired, refusing teardown, run against a daemon or pass --no-backup to tear down without an archive |
X409009STKOFN | 409 | stack {name} exists in tenant {tenant} environment {environment} but its deployment directory is on node {node}, not this one, so its socket contract and deployment vars cannot be read from here |
X409010DEPNOS | 409 | deployment {tenant}/{stack} ({environment}) exists but has no persisted state at {dir}, refusing to re-render it: this run would carry forward no ports, no variable overrides, no integration edges, no ingress hosts, no protection and no placement, and would persist that emptiness as the deployment’s own state |
X409012DEPNOB | 409 | the pre-uninstall safety backup of {tenant}/{stack} failed, {error}, nothing was removed, fix the cause and run the uninstall again or pass --no-backup to tear down without an archive |
X409039APPAMB | 409 | app {name} is offered at the same priority and version by {repos}, refusing to pick one |
X409041APPVSPN | 409 | app {name} version {version} matches published revisions that render different images ({span}), refusing to pick one |
X409042APPVSUB | 409 | app {name} is pinned to version {version}, which this node’s catalogue does not carry, while the shipped app declares {shipped}, so it refuses to render a different version under the pin |
X409045KCPWDS | 409 | system keycloak admin password desync for {username}{error}, the recorded credential no longer authenticates against the live keycloak database, nothing was changed, run shc update keycloak -t master to realign the live password to the recorded seed, an offline self-heal with a short downtime, and retry |
X409046KCPWNL | 409 | system keycloak is not deployed on this node ({node}), so its admin password cannot be observed or rotated from here, run the command on the node hosting the system keycloak deployment |
X409070VDPEXS | 409 | vdeployment {instance} already exists on host {host} in environment {environment}, or its install or uninstall is still in flight |
X409074VARRST | 409 | --var removal {key} cannot take effect, module {app} restates it from {source} on every update, remove it there instead |
X409075SEDGAT | 409 | deployment {stack}: hook {hook} job {job} is a seed ceremony ({verb}) and the data it would write over was restored from an archive: {holders}. It refuses rather than re-seeding; restore the deployment again if its data is wrong, or run shc backup clear-restore-seal on the holder once you have satisfied yourself the data is what it should be |
X409076STRSHR | 409 | deployment {tenant}/{stack}/{environment} refused: it would bind a content container another live deployment already holds: {conflicts}. A shared bucket or database is destroyed whole by either consumer’s teardown, aws s3 rb --force or DROP DATABASE; give this deployment its own name for the container with --var |
X409077BNDORP | 409 | deployment {tenant}/{stack}/{environment} has no deployment row, and its render bound {plugs}; an install or an update that recorded an empty binding set would read it as bound to nothing. Rerun the install that bound it: shc install {app} -s {stack} -t {tenant} -e {environment} {bindings} |
X409081PODBND | 409 | deployment {deployment}: its replica rows were not bound{error}, nothing was started |
X409082PODNRW | 409 | replicas {replicas} of deployment {deployment} were rendered and have no assignment row, so the update cannot wait for them to read ready |
X409091JOBFAL | 409 | start job {job} of {deployment} did not end 0, so nothing that starts after it was started: {reason} |
X409092JOBNAM | 409 | start job {job} of {deployment} was not started: {service} reads ready, and its address {address} did not answer on the node that runs the job within {wait}: {why} |
X409102HKSECO | 409 | keycloak socket job refuses to replace the secret of client {client_id} in realm {realm}: the client exists, this deployment did not make it, and its secret differs from the one this deployment’s vault holds, so whatever signs in with it now would stop; copy the client’s current secret into the deployment’s vault under the key its clientSecret names, or, when an uninstalled deployment left it behind, delete it with shc auth delete-oidc-client {client_id} --tenant {realm}, then deploy again |
X409103HKOWNR | 409 | keycloak socket job refuses client {client_id} in realm {realm}: deployment {owner} made it, not {consumer}, and a deployment never takes over another’s client; give this deployment a client id of its own, or uninstall {owner} first, or, when {owner} is gone and left the client behind, delete it with shc auth delete-oidc-client {client_id} --tenant {realm}, then deploy again |
X409103PLNSTL | 409 | the render of {stack} on this node is unverified against the stored spec and the stored app archive could not be read, run the dry-run on the node that runs it |
X409120INSGON | 409 | deployment {stack} in tenant {tenant} environment {environment} was uninstalled while its install waited, so nothing is installed |
X409136PUBOVR | 409 | {deployment} cannot listen on {port}/{protocol} at {nodes}: {holder} already does |
X409137PUBAMB | 409 | --expose @{name} is both a connection and a location; rename one of them |
X409142PUBHST | 409 | {hostname} is already served by {holder} |
X409146EDGCAP | 409 | module {app} needs {required} CPUs for service {service} but this node measured only {capacity}. Nodes join this cluster through it on 443, so init stopped. Give this node at least {required} CPUs, or lower the ceiling with shc config set deploy.limit_ratio <ratio>, then run shc init again |
X409147SYSFIT | 409 | module {app} needs {required} CPUs for service {service} but no node measured more than {capacity}, so it was not installed. Init leaves {app} out of this cluster for the same reason, X200916SYSCAP. Join a node with at least {required} CPUs, or lower the ceiling with shc config set deploy.limit_ratio <ratio>, then install it again |
X409148RLTNFN | 409 | the rollout of {deployment} {standing} |
X409152RFNRLT | 409 | the rollout of {deployment} re-finished for shcd {version} did not finish: {rollout} |
X409167SYSUNI | 409 | {stack} is a module of the master tenant and the platform runs on it; the deployments that lose their provider with it: {consumers}. Nothing was stopped. Take it down anyway with shc uninstall {stack} -t master --force |
X409175GRPOLD | 409 | deployment {deployment} keeps its data in the volume {old} and this version keeps member 1 of the group {group} in {volume}. Nothing was changed. Back up the deployment with the version that wrote {old} and restore it with this one, or reinstall it. |
X409176RNDOLD | 409 | deployment {tenant}/{stack}/{environment} on node {node} has render mark {mark}, not the committed mark {want}; no current render holder was resolved; run shc update for this deployment before retrying |
X409179PLCRPL | 409 | no node can take replica {replica} of {deployment}: {rules} allows {nodes}, and {why} |
X409194CPYLIV | 409 | this node’s directory of deployment {tenant}/{stack} ({environment}) was not removed, {reason}; a copy goes only while the deployment’s record is being removed and names another node, nothing was stopped or deleted |
X409238UPDRBF | 409 | the update of {deployment} failed, and --rollback-on-failure rolled it back to {spec}: {cause} |
X409240UPDRPF | 409 | the rollout of {deployment} to spec {spec} finished but did not update {failed} |
X409261ROLACT | 409 | deployment {deployment} has a rollout to {spec} still {state} after {waited}, so the install stopped before it moved any replica: install again once the rollout has finished |
X409262ROLPSD | 409 | deployment {deployment} has a paused rollout to {spec}, so the install stopped before it moved any replica: an update settles a paused rollout before its own, and an install does not |
X409303VOLSHR | 409 | volume {volume} is {current}, an update cannot shrink it to {asked} |
X409304VOLGRW | 409 | volume {volume} is {current} and cannot grow to {asked} yet |
X409305VOLNOD | 409 | volume {volume} already sits on a block volume, and putting it on the node disk would leave its data behind |
X409311VOLQTA | 409 | volume {volume} cannot be capped at {size} on node {node} ({filesystem}): {why} |
X409355OOPWDS | 409 | the system openobserve does not accept the admin password on record, it answered {answer}, so the record and the store are apart already and nothing was changed; put the password the store holds on record with shc vault set -t master -s openobserve password, then run this again |
X409357OOPWNR | 409 | no admin password is on record for the system openobserve, so there is nothing to sign in with and nothing was changed; put the password the store holds on record with shc vault set -t master -s openobserve password, then run this again |
X409429PODDNS | 409 | {deployment} is not started on this podman node: the engine’s resolver is on for network {networks}, and this node does not run it, so its containers would have no resolver; remove the network with podman network rm once no container names it; a deployment’s networks are made again with it off at its next start and the fabric bridge is replaced on a drained node |
X409430PODDNR | 409 | {deployment} is not started on this podman node: its compose would have podman-compose create network {networks} with the engine’s resolver on, which this node does not run, so its containers would have no resolver; it was rendered before SHC turned the engine’s resolver off, run shc update for it |
X409431PODINC | 409 | {deployment} is not started on this podman node: its compose document has a top-level include, and a network an included file creates would have the engine’s resolver on and leave its containers without one, inline what it includes |
X409440LEFTOV | 409 | {consumer} not bound: {leftovers}, which this deployment did not make; a new deployment never takes over what an earlier one left. Delete them, or bring the earlier deployment back with shc recover -b and its backup. An uninstall without --keep-data drops them, as does {cleanup} |
X409459STKCUT | 409 | the {operation} of {deployment} was cut off when shcd stopped and did not finish; {command} runs it again |
X409463INTPRB | 409 | the {plug} plug of {deployment} is already on {provider}, provision prepares a provider the plug is not on |
X409464INTPRJ | 409 | {provider} serves {plug} through its {socket} socket, which declares no provision job, so nothing can prepare it for {deployment} before the edge moves there |
X409465INTDSC | 409 | the {plug} plug of {deployment} is on {from}, whose {socket} socket declares no describe job, so provision cannot read what {deployment} holds there to match it on {provider} |
X409556UPDSRK | 409 | the rollback of {deployment} did not put back {served}, the spec it served before the move: {began} was current when the move began and {current} is now, so that newer update stays |
X409741PLGCLASH | 409 | stored integration {plug} cannot be renamed to {target} because that plug already has an edge, remove the unwanted edge with shc update |
X409783DNTCHG | 409 | network {network} of {deployment} runs on node {node} with subnet {was}, and this render would give it {now}; no runtime changes an existing network’s subnet in place, so the render is refused: uninstall the deployment from the node, or restore the deployment_network row that holds {was} |
X409846CPYMNT | 409 | a volume is still mounted, or its mount could not be read, at {mounts} |
X409908DEPAMB | 409 | stack {name} is deployed in more than one environment in tenant {tenant} ({environments}). A stack name is one coordinate of three and cannot address a deployment, name one with ?environment= |
X409912HKNDEF | 409 | update of {tenant}/{stack}/{environment} refused before it changed anything: {what} cannot wait for its next start and needs {services}, stopped by its operator; run shc start {stack} -t {tenant} -e {environment} and update it again |
X409913GATHST | 409 | refusing to gate {stack}, the cluster has no serving host for the SSO login to start under, so a browser would get 502; set one with shc cluster host set |
X409915GATIDP | 409 | refusing to gate {stack}, the system ingress has no SSO gate until its SSO provider {provider} is up and bound to it, so the route would not be served, install {provider} in the master tenant if it is missing, else retry within a minute, nothing was changed |
X409946UNIRMT | 409 | node {node}, which the deployment row of {tenant}/{stack}/{environment} records, answered its teardown with an error ({error}); the deployment row stays at removing, fix what that error names and retry the uninstall |
X409949UNIRUN | 409 | deployment {tenant}/{stack} ({environment}) is already being uninstalled on node {node}, as operation {operation} issued on node {origin}; nothing was started, follow that operation or run the uninstall again once it has ended |
X409950UNIELS | 409 | deployment {tenant}/{stack} ({environment}) is recorded on node {node}, which holds no directory for it, while several nodes hold one: {holders}; nothing was started and the record was not changed, because which of them is the deployment and which a leftover copy cannot be told apart. Once only the deployment’s own directory is left, run the uninstall again |
X409951UNIMOV | 409 | deployment {tenant}/{stack} ({environment}) is recorded on node {holder}, not on node {node}, which started nothing; the uninstall asks again on {holder} once and ends with this answer only when that ask got it too: run the uninstall again |
X409953OPRRUN | 409 | deployment {tenant}/{stack} ({environment}) is already being changed by {kind} {operation} on node {node}, since {since}; nothing was started or written, run this again once it has ended: shc operation ls lists what is in flight |
X409956CMPWTH | 409 | plug {plug} of {consumer} was placed in {field} {requested}, and tenant {requested} no longer lists this deployment in {key}; the update is refused rather than moving the edge to another {field}, so ask tenant {requested} to list it again, or unbind the plug first |
X409958BNDREF | 409 | the {plug} edge to {provider} was refused by its job {job}, which changed nothing: {error} |
X409961UPDSRC | 409 | update of {stack} would resolve a different source than the deployment runs: recorded {recorded}, resolved {resolved}, and it refuses to swap silently |
X409962SECSTG | 409 | {deployment} was asked to start containers while the secrets its render staged are not its own yet; the engine is asked only once the render can no longer be refused |
X409963UPDVER | 409 | update of {stack} names version {version}, but the deployment runs the app from {source}, not the catalogue; write |
X409965SECBSY | 409 | {deployment} is being rendered by another operation, which holds its secrets until the engine has answered; run this again when that one has finished |
X409970INSEXS | 409 | deployment {stack} already exists in tenant {tenant}, in {environments}, and an install role only creates new deployments, so changing it needs stack:{stack}:manage |
X409971APPRBV | 409 | update of {stack} moves {app} from {from} to repo {to} at {version} but {why}, and a rebind keeps the version and the bytes or upgrades to a newer version |
X409972APPRWD | 409 | update of {stack} moves {app} from {from} to repo {to} at {target}, which is not newer than the {installed} the deployment runs, and a rebind never rewinds, so rebind at the installed version first with {rebind} and then upgrade inside repo {to} |
X409973APPMOV | 409 | {app} is no longer in repo {from} and repo {to} serves it, so rebind with {rebind} |
X409994DLGTWO | 409 | domain {domain} has {count} device_login declarers ({declarers}), so it publishes none of them |
X409995DLGTNT | 409 | device_login for tenant {tenant} is not published on {domain}: the domain’s tenant is {domain_tenant} |
X500009INTJOB | 500 | integration job {job_name} failed during {phase} with {error} |
X500011JSNENC | 500 | json encode failed for {context}, {error} |
X500012JSNDEC | 500 | json decode failed for {context}, {error} |
X500013AGNPRS | 500 | failed to parse autogen store {path}, {error} |
X500014AGNMAR | 500 | failed to marshal autogen store, {error} |
X500015INTNET | 500 | attach integration networks failed, {error} |
X500016SOKALI | 500 | alias socket hostname failed, {error} |
X500017INTNST | 500 | integration binding not stored{error} |
X500018VOLDEC | 500 | auto-declare volumes failed, {error} |
X500030VOLPRP | 500 | resolve and prep volumes failed, {error} |
X500031NETDEC | 500 | auto-declare networks failed, {error} |
X500035BNDCPY | 500 | copy bind {rel} failed, {error} |
X500039LDVARS | 500 | load vars failed, {error} |
X500045VLTRSV | 500 | resolve vault autogen failed for stack {stack}{error} |
X500047CMPRND | 500 | render compose failed, {error} |
X500048CMPPRS | 500 | parse compose failed, {error} |
X500051INGRSS | 500 | traefik ingress enrichment for stack {stack} failed, {op}{error} |
X500058SOKPRS | 500 | parse socket {path} failed, {error} |
X500059DCKCMP | 500 | docker {subcommand} failed, {error}, output {output} |
X500067APPSSE | 500 | sse stream closed without terminal frame |
X500068SCHCYC | 500 | module deploy scheduler dependency cycle among {stacks} |
X500069SCHBLK | 500 | module {stack} not deployed, a dependency failed fail-closed |
X500089UNISHP | 500 | unintegration job {job} of edge {plug} was not run, {reason}, and the state it undoes is still live |
X500093CMPMAR | 500 | compose re-marshal produced unparseable yaml {error} |
X500106DEPRCF | 500 | deployment {project}: {dependents} depend on a service this deploy recreated and could not be restarted, {output}. They may still hold the recreated service’s old address, restart them by hand with docker compose -p {project} restart {dependents} |
X500109DPLVDT | 500 | deployment {stack} in tenant {tenant} environment {environment} never reached a health verdict within {budget}, {detail}, inspect with: shc status {stack} -t {tenant} -e {environment} |
X500110JOBTMO | 500 | plug post_deployment job {job_name} was cut off at its {timeout}s timeout before it finished, so the consumer-side reconcile did not complete; the app is up either way. Its time: {phases}. Its output ends: {output}. The whole run: {run} |
X500111VLTUNR | 500 | deployment {stack} in tenant {tenant} environment {environment} rendered without {keys}, so {paths} left empty rather than shipping the literal ref+vault URI as a password{error}, restore the vault with shc vault unlock, or shc vault set for a key SHC cannot mint, and re-run shc update {stack} |
X500112CLHUNK | 500 | the cluster host could not be determined on this node ({reason}), work that reads it is refusing rather than treating the unknown value as operator intent |
X500113KCHBLD | 500 | keycloak reconcile refused: the desired issuer host resolved empty on this node while the deployment serves {deployed_host} at {deployed_base_path}, recreating would move the OIDC issuer to root for the whole estate, skipped this sweep |
X500114CLHDIS | 500 | the estate’s replicated cluster host is {stored} but this node’s node_bootstrap.json says {local}, the replicated value wins and nothing was overwritten |
X500115CTRUNH | 500 | container {container}, service {service} of {subject}, has failed its healthcheck {streak} consecutive times, about {elapsed} of continuous failure: it is Up and serving nothing; the healthcheck said: {evidence} |
X500116DEPRCU | 500 | deployment {project}: {what}: {detail}, so whether this deploy recreated a container, and whether anything depends on one that moved, is unknown; no dependent was recycled, check by hand with docker compose -p {project} ps and restart any service that proxies to a sibling |
X500117CVGRSF | 500 | deployment {project}: the failed converge stopped {casualties} and {still_down} are still not running after the restore{output}, start them by hand ({command}) |
X500118INGDRK | 500 | System ingress down: deployment {project} {services} not running after a failed converge and could not be started back. Every deployment on every host behind this ingress is unreachable until the ingress runs again, run: {command} |
X500119CVGJRN | 500 | the converge before-image record could not be {op}, {what}: {detail}. The before-image is what lets a boot reconciler start back what a killed converge stopped, so a converge that cannot record one does not start |
X500120STKPRK | 500 | deployment {subject} is parked at status {status} with no operation behind it: {detail} |
X500121STKPRF | 500 | deployment {subject} was parked at {status} and the boot reconciler refused to act: {reason}. The row is marked unknown so it is no longer frozen at an operational word, and needs an operator |
X500122DEPIMU | 500 | deployment {project}: superseded-image cleanup removed nothing: {detail} |
X500124SKTTMO | 500 | socket job {job_name} did not end within {backstop}s of its dispatch, the backstop over its bring-up and its {timeout}s timeout, which counts from its command’s start, so the node that runs it stopped answering. Its time: {phases}. Where it stood: {error} |
X500125SPCREC | 500 | deployment spec for {tenant}/{stack} not recorded{error}, the deployment is up but a rollback, a rebuild and its start check still read the spec before this one, run the update again |
X500126HKMINT | 500 | hook {hook_type} of {deployment}: job {job} minted {key}, which its mints: does not declare; update an app revision from before mints:, or declare the key under mints: in {job}.job.yaml |
X500127HKRSTU | 500 | {where} of {deployment}: job {job} asked to restart {service}, which its restarts: does not declare; declare it under restarts: on the job |
X500135SPCSTG | 500 | deployment spec for {tenant}/{stack} not recorded before its start{error}, nothing was started, run the update again |
X500139PUBREC | 500 | published ports of {tenant}/{stack} not recorded{error}, listener state may be stale, run the update again |
X500140RNDOPN | 500 | the sealed rendered documents of {deployment} could not be opened with this node’s vault: {error}, so the seal was dropped and it starts again only at its next update |
X500145RNDFIN | 500 | {deployment} could not be finished for node {node} from its stored render: {error} |
X500150RFNDEP | 500 | {deployment} was not re-finished for shcd {version}, so its replicas run what an older shcd finished: {error} |
X500151RFNPRP | 500 | the re-finish prep {prep} failed for shcd {version}, so no stored render is re-finished until it succeeds: {error} |
X500159OPRACC | 500 | the daemon named no operation to follow, check shc operation ls before retrying |
X500238UPDRBN | 500 | the update of {deployment} failed ({cause}), and its rollback to {spec} did not finish{error} |
X500304VOLRDS | 500 | volume sizes for {tenant}/{environment}/{stack} could not be read: {error} |
X500338VOLUNF | 500 | uninstall of {tenant}/{stack} ({environment}) could not release its block volumes{error}, the deployment directory is kept so a retried uninstall can finish |
X500340VOLKPF | 500 | uninstall of {tenant}/{stack}/{environment} could not unmount the block volumes it keeps{error}, the deployment directory is kept so a retried uninstall can finish |
X500355OOPWRC | 500 | the system openobserve’s new admin password could not be put on record, {reason}, so the live password was changed back and nothing was changed |
X500356OOPWST | 500 | the system openobserve holds a new admin password that could not be put on record, {reason}, and could not be changed back, {undo}: the platform’s readers are refused until shc vault set -t master -s openobserve password records the new password{generated} |
X500357OOPWUP | 500 | the system openobserve’s admin password is changed and on record, and the update that hands it to the container failed, {reason}; run shc update openobserve -t master |
X500474APPPCK | 500 | the app at {path} could not be packed to send to the daemon at {daemon}: {error} |
X500558INGMOV | 500 | {deployment} was not moved off the ingress unit {unit} of node {node}{error} |
X500703CATRSTS | 500 | no host public CA bundle found in {searched}, so the node trust bundle carries the SHC anchors only, so containers pointing SSL_CERT_FILE at it will not trust any public CA |
X500707CATRNOA | 500 | node trust bundle {path} was not written: no SHC global root and no estate edge CA anchors could be collected on this node. Containers that mount it get no SHC trust at all, and anything verifying the estate’s own edge fails with an unknown-authority error |
X500728UNIREP | 500 | the uninstall of {tenant}/{stack}/{environment} left {left} on node {node}, {error}, run the uninstall again once that node’s replica runner is free |
X500784DNTSPC | 500 | the stored spec of {deployment} could not be read to check its deployment networks’ subnets, {error} |
X500821INTMOV | 500 | the {plug} edge was not moved from {from} to {to}: {error} |
X500825INTEDG | 500 | the {plug} edge to {provider} failed its socket job, so this update was not applied: {error} |
X500827INTBCK | 500 | the refused move of {stack} could not be put back on the providers it runs on, so its record may name the one it was moving to: {error} |
X500852DPLSTK | 500 | {failed} of {total} deployments failed{failures} |
X500853DPLSET | 500 | {failed} of {total} deployments failed{failures} |
X500854DPLNST | 500 | {count} of {total} deployments did not start |
X500907STKFAL | 500 | deployment operation failed with {error} |
X500908HKFAIL | 500 | hook {hook_type} failed with {detail}{error} |
X500909HKHTTP | 500 | webhook hook returned HTTP {status} {body} |
X500925KCPWRS | 500 | system keycloak admin password reset failed at {step}{error} |
X500927UNILEK | 500 | unintegration job {job} for edge {plug} of {tenant}/{stack}/{environment} failed{error}, the provider-side state it revokes is still live. Revoke it by hand, the deployment was removed anyway |
X500928HKOOMF | 500 | job {job} on service {service} was oom-killed inside the container {detail} |
X500931HKOOMS | 500 | job {job} on service {service} reported success but was oom-killed inside the container {detail} |
X500933VAPMAT | 500 | plug {plug} vapp instance {instance} failed to materialize on {stack}{error}, the deploy continues without it and the plug’s own jobs may fail |
X500934VAPRST | 500 | instance {instance} installed but restarting host project {project} failed{error}. Restart it by hand with docker compose -p {project} restart; until then the host may serve mixed imports |
X500942SECRAM | 500 | secrets directory {dir} is not on tmpfs, and a secret is never staged onto disk{remedy} |
X500943SECUNR | 500 | secret {secret} names vault key {key}, which did not resolve, so nothing was staged for it |
X500943TMBWRT | 500 | could not record the uninstall tombstone for {tenant}/{stack}/{environment} ({error}), so its deployment row stays at removing; retry the uninstall, because without the tombstone a leftover manifest on any node is re-imported at that node’s next daemon start |
X500944SECVLT | 500 | secret {secret} needs the vault and none is reachable, so nothing was staged; a secret is never resolved through the offline store, which is a file on disk |
X500944TMBRED | 500 | could not read the uninstall tombstones for {tenant}/{stack}/{environment} ({error}), so the manifest at {path} was not imported this boot; the next daemon start tries again |
X500945PROMIV | 500 | deployment sidecar {path} holds an unreadable protection flag, {reason}, protection state is indeterminate |
X500946PROCLR | 500 | deployment {stack} deployed but its protection flag could not be cleared{error}, the deployment is still protected and will refuse destroy |
X500947VAPCLA | 500 | vdeployment {stack} uninstalled but its cleanup jobs {jobs} failed{error}, reclaim what they owned by hand, the instance record is gone |
X500948VAPCLN | 500 | vdeployment {stack} cleanup job {job} failed{error}, the resource it destroys may still exist |
X500949TKYRAM | 500 | traefik key directory {dir} is not on tmpfs, and a private key is never staged onto disk{remedy} |
X500953APPYRD | 500 | app.yaml read failed for app {name} {error} |
X500961NETPRF | 500 | shared network {network} could not be created{error} |
X500963NETUNR | 500 | provider network {network} not reachable for the integration job |
X500963SECRST | 500 | {deployment}: {secret} could not be put back as it was before the update: {error}; a container that reads it gets what the failed update staged until the next update |
X500964JOBYML | 500 | hook job {name} yaml {op} failed{error} |
X500964SECPRM | 500 | {deployment}: {secret} could not be switched to what its render staged: {error}; what had been switched was put back and nothing was started |
X500966PODNET | 500 | podman shared network {name} create failed{output} |
X500966SECFIN | 500 | {deployment}: a switch of its secrets that an earlier render began could not be finished at {secret}: {error}; its secrets are part way between two sets and the staged set stays in {dir}, so every render of the deployment is refused until the switch finishes; make the file there writable on this node, since a secret is never written through a link, or uninstall the deployment, which takes its secrets off this node |
X500967SECMNT | 500 | secrets directory {dir} could not be made an in-memory filesystem: {error}; shcd mounts it with /sbin/mount_tmpfs when it starts on a Mac, and nothing secret is staged on this node until it is one; fix what mount_tmpfs reported and restart shcd: sudo launchctl kickstart -k system/org.selfhostedcloud.shcd |
X500969DEPSTU | 500 | deployment state for {tenant}/{stack} exists but could not be read{error}, refusing, an unreadable manifest is not an absent one |
X500973HKDREC | 500 | deployment {tenant}/{stack}/{environment}: this update left {jobs} for its next start and could not record them, so no start runs them; run shc start {stack} -t {tenant} -e {environment} and then shc update {stack} -t {tenant} -e {environment}{error} |
X500976PROPTH | 500 | deployment sidecar could not be located, {reason} |
X500977PROARM | 500 | deployment {stack} deployed but its protection flag could not be armed on this node{error}, the deployment is not protected |
X500979DNSRMV | 500 | managed dns records for host {hostname} could not be removed on uninstall{error} |
X500980PROVAL | 500 | config {key} holds a non-boolean value, protection state is indeterminate |
X500981PRXEDG | 500 | proxy edge declarations unreadable, refusing to render without them, {cause} |
X500981PRXFWD | 500 | the Macs’ published-port forwarder sources are unreadable, refusing to render the system Traefik without them, {cause} |
X500981PRXUNT | 500 | the networks a PROXY v2 header is never trusted from are unreadable, so nothing is trusted without them, {cause} |
X500981RSTSEL | 500 | restore seal {op} failed for stack {stack}: {detail}. The seal is what keeps an app’s first-boot seed job off data that came out of an archive, so a deployment without one is not protected from being re-seeded |
X500982DNSPUB | 500 | no managed dns record was published for newly bound host {hostname}{error}, the deployment is up but that hostname does not resolve, re-run the deploy or check the dns connection owning its zone |
X500983NETPOL | 500 | docker local bridge address pool is exhausted{output}, this is not a missing network, compose reported network-not-found because a new default bridge could not be allocated, do not prune live networks as incident response, the remediating pool change is a scheduled dockerd restart |
X500989PRTBND | 500 | port {mapping} needs node {node}‘s private ipv4 to bind its load-balancer publish to, {cause} |
X500993LSEGUP | 500 | lease reap for {tenant}/{stack}/{environment} abandoned after {attempts} failed attempts, {detail}; the deployment is left in place with an expired lease. Fix the failure and shc lease renew, or uninstall it by hand |
X500995PRXREL | 500 | connection {conn} still publishes for deployment {stack}, its release failed{error} |
X502358OOPWHO | 502 | the system openobserve admin password change was handed to {node}, which runs openobserve, and no answer of it could be read here, {reason}; the change may have completed there, shc vault get password -t master -s openobserve prints the password on record and {node}‘s journal says how it ended |
X502739DMNLST | 502 | daemon listing failed: {cause} |
X503117VLTRFD | 503 | refusing to deploy {stack} in tenant {tenant} environment {environment}, vault secrets {keys} did not resolve so credential fields {paths} would render empty{error}, nothing was rendered, written or converged, restore the vault with shc vault unlock or shc vault set for a key SHC cannot mint, then re-run |
X503148TRFREQ | 503 | Traefik is failed or missing after module installation; nodes cannot join this cluster on 443; re-run shc init |
X503160RFNINP | 503 | {deployment} is not re-finished for node {node} yet: this leader cannot read {unread} yet, and a finish without it renders a spec the node never ran |
X503174RULGTE | 503 | a placement rule needs the daemon’s fence store to admit it, and none is wired here |
X503178PLCDSP | 503 | placement put {stack} on {node}, and this process has no install dispatch to run it there; install through the daemon |
X503275RSVDWN | 503 | refusing to render {tenant}/{stack}/{environment}: its services call their providers by names only the DNS of node {node} answers, and that DNS is not answering, nothing was started or changed, retry once it answers; resolver.revision in shc doctor says why |
X503356OOPWUN | 503 | the system openobserve could not be asked to change its admin password, {reason}; nothing was changed |
X503429PODDNQ | 503 | {deployment} is not started on this podman node: podman could not say which networks have the engine’s resolver on ({error}), and a container on one would have no resolver |
X503430PODDOC | 503 | {deployment} is not started on this podman node: its compose document {path} could not be read ({error}), so the networks its containers would join cannot be checked for the engine’s resolver |
X503738DMNREQ | 503 | shc {verb} requires shcd, but shcd is not reachable; start it with {start} and run shc doctor to find out why it is down |
X503901BNDNOS | 503 | {work} for {tenant}/{stack}/{environment} could not run: the deployment’s bindings are in the daemon’s store and this process, a CLI with no daemon up, holds none; start the daemon, or point the CLI at a node running it with shc ctx, and run it again |
X503910CONMSK | 503 | connection mint seam not wired for connection {connection} |
X503916HKSTOP | 503 | update of {tenant}/{stack}/{environment} refused before it changed anything: which of its services its operator stopped could not be read, so the update cannot tell which of its hooks would wait for them{error} |
X503941UNIOWN | 503 | uninstall of {tenant}/{stack}/{environment} must run on node {node}, which holds its deployment directory, and it could not run there ({error}); the deployment row stays at removing, retry once {node} answers |
X503942UNIIND | 503 | the teardown of {tenant}/{stack}/{environment} was sent to node {node} and no answer came back ({error}); it may still be running there, so the deployment row stays at removing; check {node} before you retry, because a second teardown would race the first |
X503943RNDLCK | 503 | the rendered documents of {deployment} are sealed and this node’s vault is locked, so they are not back in RAM yet and the node agent starts nothing until they are |
X503947HLDDWN | 503 | {verb} needs node {node}, which holds the deployment, and that node is not answering, {detail}; nothing was run and nothing was changed, retry when {node} is back, which shc node ls shows |
X503948DEPNOR | 503 | the safety backup of {tenant}/{stack} could not be recorded, so the uninstall did not start: nothing was stopped or removed ({error}), run the uninstall again once the store answers, or pass --no-backup to tear down without an archive |
X503950UNIASK | 503 | deployment {tenant}/{stack} ({environment}) is recorded on node {node}, which holds no directory for it, and the search for other holders could not run ({error}); nothing was started, run the uninstall again once the holder search is available |
X503954OPRCLU | 503 | the operation claim of {deployment} could not be read or written, {error}; nothing was started or written |
X503957DPFASK | 503 | deployfile {path}: the dry run could not ask {cluster} whether this deployment exists, {cause} |
X503987DNSSKW | 503 | dns socket edge {plug} cannot write: no dns service is wired in this process |
X504102OPRFOL | 504 | the {action} goes on as operation {operation}, shc operation follow {operation} waits for it again and shc operation ls lists it while it runs |
X504126JOBADM | 504 | job {job_name} did not start: its node spent the {allowance}s it allows before a job’s command, {error} |
X504258ROUSTL | 504 | deployment {deployment} did not converge: routing nodes {nodes} applied no newer routing revision for {stalled}, and routing its replicas needs revision {revision} |
X504259VIPNBK | 504 | deployment {deployment} did not converge: its replicas are ready, and service VIPs {services} had no ready backend for {stalled} |
X504260HLTWAT | 504 | deployment {deployment} service {service} did not settle after waiting {waited}: last replica status {status}; {reason} |
X504541CTRRTO | 504 | the liveness restart of container {container} did not return within {budget}, and no other restart of it begins until it does |
X504557UPDSRW | 504 | the rollback of {deployment} put back {served}, the spec it served before the move, but after {wait} its replica rows did not all name it ({rows}) |
X504654CLHKCW | 504 | the cluster host is {host}, but the system Keycloak did not serve under it within {waited}; the host stands and the system Keycloak keeps converging |
X504740DMNTKN | 504 | shcd took the request of shc {verb} and did not answer in time; the {verb} may still be under way, read it with {read} before you run it again |
X507296PLCRCL | 507 | {deployment} refused before any image was pulled: {node} needed {short} more disk for its images and removing its unused images gave back {reclaimed}: {why} |
X507360PLCSTR | 507 | {project} refused before node {node} pulled anything: {disk} is {used} used, {free} free of {total}; the images it lacks need {need} there, starts in flight hold {inflight}, and scheduler.disk_mark {mark} keeps {keep} free, so {short} more must be freed there once its unused images are removed; nothing was pulled |
apparchive
Section titled “apparchive”Source: modules/apparchive
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X413737PKGBIG | 413 | the app archive of {deployment} is {size} bytes, over the {limit} byte limit a failover keeps in the cluster |
X500736PKGSTR | 500 | the app archive of {deployment} could not be stored in the cluster: {error} |
X500738PKGARC | 500 | deployment {deployment} cannot be delivered from its stored app archive, archive digest {digest}: {why} |
Source: modules/audit
Count: 6
| Code | HTTP | Message template |
|---|---|---|
X400900INVDAT | 400 | invalid date format {value} |
X400901AUDLMT | 400 | invalid --limit value {value} |
X403987AUDEEO | 403 | the {surface} compliance surface requires SHC EE with the audit entitlement, the community edition keeps writing and reading the tamper-evident chain but does not serve the compliance artifacts, {remedy}, see shc license status to activate a license that includes audit |
X404100AUDNOF | 404 | audit record {id} not found |
X500904AUDPRN | 500 | audit retention prune failed {op} {error} |
X500905AUDCAP | 500 | audit row truncated by the containment cap, code {code}, {detail} |
Source: modules/auth
Count: 116
| Code | HTTP | Message template |
|---|---|---|
X200929KCRLMW | 200 | keycloak realm {tenant} was provisioned with a setting not written: {what} |
X200943OIDWAT | 200 | oidc provider at {endpoint} answered {answer}, asking again in {wait}, for up to {bound} in all |
X200944KCPRED | 200 | keycloak predates SHC’s admin service client, so this admin call minted with the master admin’s password; run shc update keycloak -t master |
X400058LGOTOK | 400 | back-channel logout token rejected: {reason} |
X400059LGOSUB | 400 | back-channel logout token names neither a session nor a subject |
X400131JWKCFG | 400 | jwks missing kcURL or realm |
X400137STKTWO | 400 | the request names more than one stack ({stacks}); name the deployment once |
X400166TRSENT | 400 | auth.trusted_realms entry {entry} must be |
X400861PADUID | 400 | auth.platform_admins entry {entry} must use |
X400910DEVCFG | 400 | auth login configuration invalid {detail} |
X400911TLSCFG | 400 | auth login tls configuration invalid {detail} |
X400912CAPINF | 400 | ca fingerprint invalid {detail} |
X400921PADENT | 400 | auth.platform_admins entry {entry} must be |
X400923SVCCLN | 400 | service client request invalid {detail} |
X400925LDBREQ | 400 | ldap bind request invalid, {detail} |
X400939CCLCFG | 400 | client credentials login configuration invalid {detail} |
X400940CCLHTP | 400 | client credentials login refused: {endpoint} is not https, and the client secret would travel to it in clear |
X400941CCLPIN | 400 | client credentials login refused: no public CA signed {endpoint}‘s certificate, and an unattended login does not pin the CA an endpoint serves on first contact; pass --ca |
X400946OIDREQ | 400 | OIDC client request invalid: {detail} |
X400957IDPREQ | 400 | identity provider request invalid: {detail} |
X400958IDPSEC | 400 | identity provider secret reference {ref} did not resolve to a value |
X401004JWTMAL | 401 | malformed JWT |
X401005JWKKID | 401 | jwks token missing kid |
X401006JWKKNS | 401 | jwks kid {kid} not in keyset |
X401058OIDCSIDE | 401 | forward-auth sidecar credential required |
X401060SESREV | 401 | session has been revoked, sign in again |
X401214KCPWST | 401 | keycloak rejected the recorded admin credential for {username}, the recorded admin password no longer matches the live keycloak database |
X401900NOAUTH | 401 | not authenticated, run shc auth login |
X401901TOKINV | 401 | invalid or expired token, run shc auth login to re-authenticate |
X401903NOSESS | 401 | not logged in to tenant {tenant}: {reason}, run shc auth login --tenant {tenant} |
X401910DEVAUTH | 401 | device authorization failed {status} {body} |
X401911DEVDEN | 401 | auth login was denied at the browser consent screen |
X401912CCAUTH | 401 | client credentials grant rejected {status} {body} |
X403000AUTHZF | 403 | authorization failed, no context available |
X403900NOPERM | 403 | permission denied for {scope} on {resource} |
X403903NOUSER | 403 | authorization failed, no authenticated user |
X403904NOTENT | 403 | authenticated user is not authorized for tenant {tenant_name} |
X404916AUTRLM | 404 | realm {realm} does not exist in keycloak yet |
X404922SVCNOF | 404 | service client {name} does not exist, run shc auth list-service-clients to list them |
X404926LDBNOF | 404 | ldap bind {name} does not exist in tenant {tenant}, run shc auth list-ldap-binds -t {tenant} to list them |
X404951OIDNOF | 404 | OIDC client {client_id} does not exist in tenant {tenant} |
X404957IDPNOF | 404 | identity provider {alias} does not exist in tenant {tenant} |
X408910DEVEXP | 408 | auth login timed out, the device code expired before login completed |
X409910CAPINM | 409 | cluster ca fingerprint mismatch expected={expected} got={got} |
X409911CAPINC | 409 | the CA pinned for {cluster} changed, it now answers with {got} and SHC does not re-pin on its own. If this cluster was rebuilt under the same name, run shc ctx logout {cluster} to forget the old CA and log in again. If it wasn’t, find out why before you trust it |
X409924SVCKND | 409 | client {name} is not a service client, so it is not deleted here |
X409927SVCSCP | 409 | service client {name} already exists with rights other than {scope}; delete it with shc auth delete-service-client {name} and create it again |
X409928LDBAPP | 409 | ldap bind {name} in tenant {tenant} is held by deployment {app} through its ldap plug: it is not handed out or removed here, uninstall the app to remove it, or choose another name for a consumer of your own |
X409930LDBEXS | 409 | ldap bind {name} is already there in tenant {tenant} and its password is not read back, pass --rotate-secret to regenerate it |
X409944KCPRED | 409 | keycloak runs without SHC’s admin service client env and still needs shc update keycloak -t master |
X409945SVCADM | 409 | service client {name} is SHC’s own admin client and is not managed through shc auth; the platform rotates it: its vault value, then shc update keycloak -t master |
X409947OIDMST | 409 | OIDC client management refuses realm master; choose a tenant realm |
X409948OIDRES | 409 | OIDC client {client_id} is reserved for the platform or Keycloak |
X409949OIDPLG | 409 | OIDC client {client_id} in tenant {tenant} is owned by deployment {deployment} through plug {plug}; change that deployment |
X409952OIDEXS | 409 | OIDC client {client_id} already exists in tenant {tenant}; import it instead of creating it |
X409953OIDKND | 409 | client {client_id} in tenant {tenant} is not a supported standalone OIDC client: {reason} |
X409956OIDAUT | 409 | OIDC client {client_id} in tenant {tenant} cannot change authentication in place; delete and create it, or import the new one |
X409957IDPMST | 409 | on realm master an identity provider links existing users only; first_login must be link-only, because every master identity is platform root |
X409959IDPRES | 409 | identity provider alias {alias} is reserved for the vendor portal |
X409963IDPEXS | 409 | identity provider {alias} already exists in tenant {tenant}; import it instead of creating it |
X409964IDPKND | 409 | identity provider {alias} in tenant {tenant} is not an OIDC provider |
X409969IDPFLW | 409 | the SHC link-only first login flow in tenant {tenant} is incompatible or could not be made exact |
X410059RLMGON | 410 | the realm lookup routes are retired, forward-auth reads the realms from its node’s auth section |
X413137STKBIG | 413 | the request body is larger than any stack route accepts: {limit} bytes |
X500050KCRLMP | 500 | realm provisioning failed for tenant {tenant} exit={exit_code} stderr={stderr} |
X500051KCRLMD | 500 | realm deprovisioning failed for tenant {tenant} exit={exit_code} stderr={stderr} |
X500052KCROLC | 500 | role create failed for tenant {tenant} role {role} exit={exit_code} stderr={stderr} |
X500053KCROLD | 500 | role delete failed for tenant {tenant} role {role} exit={exit_code} stderr={stderr} |
X500054KCROLB | 500 | batch role create failed for tenant {tenant} roles={role_count} exit={exit_code} stderr={stderr} |
X500057FWDSEC | 500 | forward-auth login client secret unresolved {reason} |
X500062FWDENUM | 500 | forward-auth redirect-uri enumeration unresolved {reason} |
X500063FWDRMIS | 500 | forward-auth completed login on host {host} outside the enumerated redirect-uri set, {redirect_uri} was admitted by the wildcard, {stamped_count} stamped at {stamped_at} |
X500064FWDRSTP | 500 | forward-auth redirect-uri restamp failed for trigger {trigger} {reason} |
X500138STKSPL | 500 | the stack-scoped request gate could not spool the request body: {error} |
X500200JWKDEC | 500 | jwks decode failed, {error} |
X500201JWKEMP | 500 | jwks fetch empty keyset |
X500202JWKNUS | 500 | jwks fetch no usable signing keys |
X500203JWKRSN | 500 | jwks rsa {param} decode failed, {error} |
X500204JWKECC | 500 | jwks ec unsupported curve {curve} |
X500205JWKECP | 500 | jwks ec {param} decode failed, {error} |
X500206JWKKTY | 500 | jwks unsupported kty {kty} |
X500207JWKCLM | 500 | jwks claims are not a JSON object |
X500209AUNTRN | 500 | auth no http transport wired |
X500210KCADMF | 500 | kcadm {operation} failed in {tenant} for {subject} stderr={stderr} |
X500211KCADPS | 500 | parse kcadm output for {operation} in {tenant} failed {error} |
X500906KYCLKC | 500 | keycloak not configured |
X500910DEVNET | 500 | auth login request to {endpoint} failed {error} |
X500911OIDPRS | 500 | auth login parse {stage} response failed {error} |
X500913CAPINF | 500 | ca pin fetch failed {detail} |
X500914SVCCLP | 500 | service client provisioning failed for {name} {detail} |
X500935SVCSEL | 500 | sealing service client {name} into vault key {key} failed: {detail} |
X500938SVCLED | 500 | recording service client {name} as scoped failed: {detail} |
X500939SVCLED | 500 | service client {name} was deleted but its scoped record was not dropped: {detail}, run shc auth delete-service-client {name} again |
X502001KYCERR | 502 | keycloak error {status_code} |
X502002JWKSTC | 502 | jwks fetch status {status_code} |
X502912OIDDISC | 502 | oidc discovery failed {detail} |
X502954OIDKCA | 502 | Keycloak OIDC client operation {operation} failed for {tenant}/{client_id}: {detail} |
X502957IDPKCA | 502 | Keycloak identity provider operation {operation} failed for {tenant}/{alias}: {detail} |
X502958IDPDSC | 502 | issuer {issuer} discovery failed: Keycloak could not read its OpenID configuration, or it names another issuer |
X503005KYCUNA | 503 | keycloak unavailable {error} |
X503061LGOREV | 503 | logout could not determine whether the credential is still live: {reason} |
X503900SVCKCN | 503 | system keycloak unavailable, cannot provision the service client |
X503913CARTNW | 503 | ca root provider not wired |
X503914CARTNA | 503 | global root ca not available {detail} |
X503915OIDPUB | 503 | keycloak public url not resolved {detail} |
X503927LDBKCN | 503 | system keycloak unavailable, cannot reach its ldap binds |
X503929LDBDEP | 503 | cannot tell whether an installed app holds ldap bind {name} in tenant {tenant}: {reason}, retry |
X503935SVCSEL | 503 | the vault is not available here, so the service client credential cannot be sealed |
X503936SVCLED | 503 | cannot read whether service client {name} is scoped: {reason}, so its token is refused, retry |
X503937SVCLED | 503 | the store of scoped service clients is not available here, so no scoped client was minted |
X503950OIDOWN | 503 | cannot establish ownership of OIDC client {client_id} in tenant {tenant}: {reason}; retry after repairing deployment state |
X503955OIDKCN | 503 | system Keycloak unavailable; cannot manage tenant OIDC clients |
X503958IDPKCN | 503 | system Keycloak unavailable; cannot manage identity providers |
X503959IDPGAT | 503 | identity provider entitlement gate is not wired |
X503960AUTNRD | 503 | the sign-in service is not ready yet, retry shortly |
X503961PRMDGR | 503 | permissions for {scope} on {resource} could not be read while the identity provider is degraded, retry shortly |
backup
Section titled “backup”Source: modules/backup/commands, modules/backup
Count: 338
| Code | HTTP | Message template |
|---|---|---|
X200043CNVFAL | 200 | converter {converter} did not complete for {stack_name}, {detail} |
X200045PRPFAL | 200 | preparation did not complete for {stack_name}, {detail} |
X200060RCVFBK | 200 | app archive extract did not succeed for {stack_name}, falling back to catalog, {detail} |
X200062VLTXSK | 200 | vault secrets export skipped for {tenant}/{stack_name}/{environment}, {detail} |
X200063BKPQSC | 200 | backup quiesce degraded for {stack_name}, {op} {error} |
X200064CFGCAP | 200 | deployment config capture skipped for {tenant}/{stack_name}/{environment}, {detail} |
X200065MAPRPL | 200 | mapping replay did not complete for {stack_name}, {detail} |
X200066RSTPRM | 200 | restore could not reapply captured permissions on {mount}, {detail} |
X200068HBDSKP | 200 | host bind {path} skipped from backup capture, {reason} |
X200070DPLREG | 200 | deployment re-registration did not complete for {stack_name}, {detail} |
X200071BKPARC | 200 | backup {backup_id} master archive build failed, {detail} |
X200072BKPFGT | 200 | backup {backup_id} row deleted but its backing data at {location} could not be removed, {detail} |
X200073MFSKIP | 200 | manifest dump skipped for backup {backup_id}, {detail} |
X200074BKPPRN | 200 | restic prune of {repo} did not complete after retention, {detail} |
X200075BKPSEL | 200 | backup {backup_id} could not be sealed into the configured repository, {detail} |
X200075MANSKP | 200 | manifest inventory check skipped for backup {backup_id}, {detail} |
X200076BKPLSE | 200 | reclaimed stale backup lease for {tenant}/{stack_name}, backup {backup_id} had not heartbeated for {stale_seconds}s and was blocking backup/uninstall |
X200077RSTJSK | 200 | restore job {job} skipped, this archive does not carry its {converters}, {reason} |
X200078BKPLIV | 200 | backup {backup_id} was not captured as a consistent point-in-time ({state}), restoring anyway |
X200080BKPQBR | 200 | the freeze did not survive the capture of {stack_name}, {detail}, the archive is stamped live |
X200081BKPSTP | 200 | backup {backup_id} held the freeze on {stack_name} for {held_seconds}s, past the hold deadline, {disposition} |
X200082BKPSTR | 200 | deployment {stack_name} is running again after backup {backup_id} stopped it for the capture, down {down_seconds}s |
X200083BKPNRS | 200 | the copy of {stack_name} ahead of its freeze failed in process ({why}) and this node’s runtime has no read-as-root sidecar, so the capture holds its freeze for the whole copy |
X200083RSTVUNR | 200 | restore verification could not read {path}, {detail}, proceeding as {taken} |
X200084BKPQRS | 200 | deployment {stack_name} is out of its backup quiesce and writable again, backup {backup_id} armed it and did not undo it, quiesced {quiesced_seconds}s |
X200085BKPPRS | 200 | deployment {stack_name} is out of its backup freeze and serving again, backup {backup_id} paused it and did not unpause it, frozen {paused_seconds}s |
X200086BKSDED | 200 | a stored backup schedule at {scope_key} in the {source} can never fire, {reason}. Re-state it with shc backup schedule set <cron> or remove it with shc backup schedule unset |
X200087BKPNOD | 200 | backup {backup_id} of {stack_name} carried no application data: all {skipped} data subjects were skipped, the archive holds deployment metadata only |
X200088BKPDED | 200 | released the backup claim on {tenant}/{stack_name}, backup {backup_id} was being run by a daemon on node {node} that is no longer running, and the row had held the deployment’s backup/move gate for {stale_seconds}s after its owner died |
X200089BKPSPW | 200 | backup free-space preflight skipped, {detail} |
X200089BKPSVL | 200 | backup captures plaintext credentials for {tenant}/{stack_name}/{environment}: secret vars [{keys}] could not be sealed into the vault, {detail} |
X200090BKPORF | 200 | backup {backup_id} left {size} bytes at {path} that its row did not name; reclaimed by id |
X200090BKPRTY | 200 | re-queued a backup of {tenant}/{stack_name} after backup {backup_id} was released without producing an archive, so the deployment is not left waiting for the next scheduled run |
X200091BKPCOW | 200 | backup coverage audit: {finding}. Every deployment here has a restorable archive, so this is a schedule that has slowed or stopped rather than an unprotected deployment. Check shc backup schedule ls |
X200092BKPSSW | 200 | swept abandoned scheduled-backup staging for {backup_id} at {path}; no live run owns it, a leftover of a crash or restart |
X200100RSTVPOP | 200 | restore job {job} target mount {mount} was already populated before the job ran, so finding it non-empty afterwards is not evidence the archive’s data landed, this mount is unverified rather than confirmed |
X200101RSTIDSC | 200 | restore did not replay the archive’s deployment identity sidecar onto {stack}, {taken} |
X200102SYNXTN | 200 | backup sync skipped {skipped} tagged for {foreign} while syncing as tenant {tenant}, a cache row is tenant-scoped so none was adopted |
X200104RSTDUW | 200 | deployment {stack}: the post-restore durability witness could not be recorded ({detail}), so this restore cannot say whether its data survived the bring-up |
X200105BKPPRW | 200 | backup protection audit ({check}): {finding}. shc doctor run --category backup reproduces this |
X200108BKPIDX | 200 | backup {backup_id} was sealed into the repository but its cache index row could not be written, so its consistency group is unqueryable until shc backup sync, {detail} |
X200110BKPCMP | 200 | backup {backup_id} composes with {detail}; restoring it alone replays the app’s volumes but none of those database rows. Restore the engine archive too, or use --with-connected, to replay the whole set |
X200110RSTLDR | 200 | restore did not replay {file} from the archive onto {stack}, {taken} |
X200111BKPSCP | 200 | backup of {deployment} reaches outside its own deployment, {signal}: {detail}. A deployment backs up what it owns or declares the exception under scope.external in its backup.yaml; shared-engine data is that engine’s backup, paired in one run with --with-dependants |
X200112BKPSTS | 200 | restic snapshot {snapshot_id} is recorded at its apparent size, because restic could not report what it stores, {detail} |
X200113BKPMKY | 200 | backup mirror {repo}: {detail} |
X200119IMPOWN | 200 | import of {archive} could not keep the captured owners and modes, a restore of it lands them as this daemon’s, {detail} |
X200124BKPMIX | 200 | backup {backup_id} is sealed without a member index, so browsing it copies the whole archive to staging, {detail} |
X200125MTSCPY | 200 | browsing backup {backup_id} copies the whole archive to staging because {reason} |
X200127RSTSOK | 200 | restore left out {sockets} of {mount} ({sample}), a socket holds no data and its app makes it again when it starts |
X200128BKPDBS | 200 | backup is taken without database {database} of plug {plug} on {provider}, {reason} |
X200297RCVRUM | 200 | recover of {stacks} runs without the disk check for its images on what could not be measured: {unmeasured} |
X200300BKPRAW | 200 | backup {backup_id} of {stack_name} holds raw mount bytes where converter {converter} did not complete, {detail} |
X200452BKPTHR | 200 | backup of {stack_name} found {replicas} stopped after the thaw and started it again |
X200478RSTINT | 200 | the restore of {deployment} from backup {backup_id} did not finish, {reason}; it reads restore-incomplete until shc backup restore {backup_id} -s {stack} finishes it |
X200498RLCCFG | 200 | backup.repo is {configured}, not {target}: new captures still go there |
X200657BKPVDR | 200 | mount {mount} of {deployment} is captured as its directory, the volume {volume} no node holds {why} |
X200659BKPVRL | 200 | the volume {volume} attached to {node} for the capture of mount {mount} stays attached there, {reason} |
X200683CNVEMP | 200 | converter {converter} of {stack_name} found no data in mount {mount}, which the capture’s frozen copy holds, so the mount’s raw bytes stand in, {detail} |
X200743RCVSHD | 200 | recovered {stack} reads vault key {key} from {answered_at} scope, its source {source} held it at {source_scope} scope, so the credential may differ, compare shc vault get {key} --scope {answered_at} with the source’s row before trusting the deployment |
X200744RCVSHA | 200 | the vault scope audit of recovered {stack} did not run, a vault key it reads may come from a broader scope than its source used, {detail} |
X200873RSTUPD | 200 | the update that follows the restore of {stack_name} did not complete, {detail}; run shc update {stack_name} |
X200874RSTSVL | 200 | restore of {tenant}/{stack_name}/{environment} left plaintext credentials at rest: secret vars [{keys}] could not be sealed into the vault, {detail} |
X200898RSTMAP | 200 | restore of {deployment} writes backup {backup_id}‘s mount {from} into {to} |
X200899RSTSTA | 200 | restore of {deployment} starts it: its operator had stopped it, and a restore ends with the deployment serving |
X400048RCVINP | 400 | invalid recover input {op} {error} |
X400049RCVMAN | 400 | failed to load manifest from {path}, {op} {error} |
X400077BKPSCD | 400 | refusing to create a backup schedule: backup.repo ({repo}) is configured but backup.password is not, so every scheduled archive would be written unencrypted to local disk instead of the repository; set it with shc config set backup.password <key> and retry |
X400078BKPSNR | 400 | refusing to create a backup schedule for {scope}: no backup destination is set and scheduled backups are restic-only, so every fire would be skipped. Connect a bucket and point backup.repo at it (https://selfhostedcloud.org/guide/operations/backup-destination/), and retry |
X400079BKPSKD | 400 | scheduled backup of {subject} skipped before capture: {reason}. Scheduled backups are restic-only and never land on the local disk. The next fire will capture and seal once that’s fixed |
X400105BKPSCR | 400 | refusing to create a backup schedule for {scope}: the {backend} repository {repo} needs credentials this estate has declared and cannot resolve: {detail}. Every fire would be skipped before it captured anything, leaving no archive and no failed row. Store the credential the ref+… row names, for example with shc vault set backup/aws_access_key_id, or point the row at a value that resolves, then retry |
X400106BKPSCG | 400 | refusing to create a backup schedule for {scope}: its repository {repo} names an s3 connection that yields no key for it: {detail}. Every fire would be skipped before it captured anything. The key comes through the s3 grant of tenant {tenant}: grant it the bucket with shc connection grant {connection} -t <owner> --capability s3 --grantee {tenant} --boundary '{"buckets":["{bucket}"]}', or point backup.repo at an s3 connection that exists, then retry |
X400107BKPMRF | 400 | backup mirror refused before it copied anything: {reason} |
X400116RLBKTO | 400 | rollback requires --to backup id or relative time |
X400134BKPRTM | 400 | restore runtime {runtime} is not a runtime, the runtimes are docker, podman, incus and apple |
X400146BKPWRT | 400 | restic mounts are read-only, use shc backup mount without --writable |
X400258BKPSEL | 400 | {file} sets {key}:, which backup.yaml does not take; a group backup reads one member by its converter’s from: |
X400402BKPPTH | 400 | backup verify takes a backup ID, not a path, and {path} is a path. Use shc backup inspect {path} to read an archive file, or shc backup ls to find the ID |
X400402BKPRUN | 400 | backup already running for stack {stack_name}, held by {holder} |
X400403BKPFAL | 400 | backup failed {op} {error} |
X400404RSTRFL | 400 | restore failed {op} {error} |
X400405BKPINV | 400 | backup {backup_id} is invalid {op} {error} |
X400407BKPIDR | 400 | at least one backup_id is required |
X400415IMPFAL | 400 | import failed {op} {error} |
X400416IMPCNT | 400 | import of {path} refused, the archive’s container is not sound, {evidence}: {remedy} |
X400417BKPOUT | 400 | {verb} needs a destination, there is no default folder for one-off archives. Name one with {flag}: a directory, or a full path ending in the archive name |
X400426RSTRWP | 400 | backup.repo {repo} is not writable by the daemon ({cause}), shcd runs under systemd ProtectSystem=strict and writes only the paths in its unit’s ReadWritePaths, so the first backup there would fail, set a path it can write such as {suggestion} |
X400430BKPMUT | 400 | exactly one of --id, --file, or --before is required |
X400431BKPCDP | 400 | cannot use both --all-connected and --with-dependants |
X400432BKPCRF | 400 | backup.repo {repo} names a connection but is not {form}, with a bucket of 3 to 63 lowercase letters, digits, dots and hyphens |
X400433BKPGRF | 400 | cannot use --file with graph flags |
X400434BKPIDS | 400 | at least one --backup id or -b |
X400435BKPMTI | 400 | one of --id or --file is required |
X400437BKPSTK | 400 | --stack required |
X400438BKPSTH | 400 | SHC_STATE_HOME not set |
X400440RCVPRT | 400 | recover plan port conflict {detail} |
X400441BKPSGO | 400 | cannot combine -s/--stack with --with-connected/--with-dependants, a group restore targets each member’s own recorded deployment |
X400442BKPHLD | 400 | backup of {stack_name} aborted, the freeze reached its hold deadline after {held_seconds}s and --fail forbids stopping the deployment to finish the capture |
X400442RSTPTH | 400 | restore --paths named {unknown} which this archive does not carry, it carries {subjects}, nothing was stopped or replayed |
X400443BKPNDD | 400 | nothing to back up for {stack_name}: no node in the cluster holds its deployment directory {deployment_dir}, so this deployment was never materialized and no archive of it is possible anywhere |
X400443RSTCKM | 400 | backup {backup_id} failed its integrity check for {subject}, {detail}, nothing was replayed, restore from another copy or re-run shc backup verify --deep {backup_id} to see what else this archive has lost |
X400444BKPNVE | 400 | nothing to back up for {stack_name}: no node holds a render of it, node {node} holds no mount, edge or vdeployment of it, no other node holds a directory of it and the store holds no integration, volume or deployment secret of it that a reinstall cannot derive again; shc uninstall skips the safety backup for this case and tears it down |
X400449RCVOLD | 400 | {flag} {value} is the retired spelling, write {flag} {now} |
X400486BKPNRP | 400 | backup of {subject} refused before capture: {reason}. Every archive is sealed into a restic repository and none is kept on local disk. To take one without a repository, name an output file with shc backup create --file |
X400487BKPPAT | 400 | backup of {stack_name} cannot capture {path}: a backup captures its deployment, so --paths takes the deployment directory, a directory under its mounts, or a mount or converter name |
X400489BKPART | 400 | invalid hook_artifacts entry {artifact}; use a literal relative mount/path |
X400491BKPFLR | 400 | backup create --{flag} was removed in 0.1.28: {why}. Drop it from the command |
X400494RLCARG | 400 | backup relocate: {detail} |
X400719BKPASX | 400 | backup restore --as restores a backup id as a new deployment and cannot be combined with --{flag} |
X400800BKNOMN | 400 | invalid backup archive, missing manifest.json {error} |
X400801BKINVJ | 400 | corrupt manifest {error} |
X400802BKGCNF | 400 | consistency id mismatch, expected {expected}, found {mismatched} |
X400803BKGINV | 400 | invalid .bkg file {op} {error} |
X400804BKGEMT | 400 | .bkg file contains no backups |
X400805EXPFAL | 400 | export from restic failed {reason} |
X400806IMPFAL | 400 | import to restic failed {reason} |
X400817MTSNWR | 400 | mount session {session_id} is not writable |
X400818MTSPTH | 400 | invalid path {path} in mount session {error} |
X400822MTSSRC | 400 | invalid mount source {source} {detail} |
X400830MTSPRC | 400 | restic mount subprocess failed to start {detail} |
X400837MTSDNG | 400 | refusing to edit {path}: it is {class} state, matched by {match}: {why}. Editing it here produces a torn, unrestorable database far more often than a useful fix. Restore the backup first, then change the running system |
X400844MTSLOC | 400 | backup {backup_id} of {deployment} cannot be restic-mounted: location {location} is not a restic repository and snapshot; .bak files cannot be restic-mounted |
X400850BKMARH | 400 | invalid AR archive header |
X400851BKMARS | 400 | invalid AR header size {size} |
X400852BKMART | 400 | invalid AR header terminator |
X400853BKMARZ | 400 | AR member {name} is {size} bytes, past the {limit} the container size field can express |
X400854BKMIDX | 400 | empty backup index |
X400860VLMREQ | 400 | invalid volume mount request {detail} |
X400862PDMREQ | 400 | pod mount request requires a container id |
X400865VOLSOV | 400 | restore storage override {storage} cannot be honored {reason} |
X400867RSTEMPT | 400 | restore verification failed for mount {mount}, backup had data but the restored volume is empty, replay did not land |
X400868RSTJOBM | 400 | restore verification failed for job {job} target mount {mount}, the converter snapshot had data but the target is empty, restore job did not land it |
X400869RSTMISM | 400 | restore verification failed for backup {backup_id}, {detail} |
X400870CNVIMG | 400 | backup job {name} image template {template} rendered empty, the deployment vars context could not resolve it, refusing to invoke docker |
X400871VLTRSF | 400 | vault secrets not restored for {tenant}/{stack_name}/{environment}, the deployment’s startup credentials are missing, {detail} |
X400872RSTVSRC | 400 | restore verification for {mount} could not read the staged snapshot, {detail}, whether the replay landed cannot be proven |
X400873RSTWIPE | 400 | restore emptied mount {mount} and could not measure what replaced it, {detail}, the replay cannot be proven to have refilled what the wipe removed |
X400874RSTJREF | 400 | restore job {job} refused, {detail}, the restore is stopped rather than reported complete over data it did not land |
X400875RSTSTGP | 400 | restore refused before dispatching the replay, the staged converter artifact {converter} at {path} is not readable by the uid the replay job runs as, {detail}, a replay that cannot open its input cannot land the archive’s data and would report success over an empty datastore |
X400876RSTNOFB | 400 | restore stopped, {jobs} failed and this archive carries no raw bytes for the mounts the replay writes, so nothing landed and nothing can fall back, {detail} |
X400879RSTDUR | 400 | restore of {backup_id} failed after the bring-up, {detail} |
X400880EXPNAT | 400 | native export is not available for app {app}, {detail} |
X400881EXPCMP | 400 | native export of {backup_id} cannot locate the engine archive holding its database, {detail} |
X400882EXPDBS | 400 | native export needs a per-database dump of {database} and engine archive {engine_backup_id} carries none, {detail} |
X400884BKPRND | 400 | backup job {name} was not run, it could not be rendered against the deployment’s render context: {detail} |
X400885RSTLNK | 400 | restore refuses to write {entry} through a symbolic link |
X400886RSTUNR | 400 | restore of {stack} refused, {artifacts} {why}, so the restore would report complete without that data |
X400890VLMTTL | 400 | mount lease {ttl} is not between one second and {max} |
X400895RSTHLD | 400 | restore cannot safely replay {entry}, {detail} |
X400898RSTMAP | 400 | restore of {deployment} refused before anything was stopped: --map {from}={to} {reason} |
X400951VLFPTH | 400 | path {path} refused, {reason} |
X400955BKPSPR | 400 | backup.secrets_password takes a secret reference such as ref+vault://shc/system/backup/old-unlock-key, never the key itself: put the key in the vault and point this key at it |
X400956VLFKND | 400 | {path} is {what} |
X400959VLFROT | 400 | {op} of {path} refused, it is the volume itself |
X400961VLFREQ | 400 | missing {what} |
X400966BKPSKR | 400 | backup.secrets_key takes a secret reference such as ref+vault://backup/secrets-key, never the key itself |
X400972INVCRN | 400 | invalid cron expression {detail} |
X400973RLBKTM | 400 | invalid time format {time} |
X401946BKPIRL | 401 | backup repository {repo} named at {scope} is locked: {detail} |
X404050OPRNOF | 404 | operation {operation_id} not found |
X404400BKPNOF | 404 | backup {backup_id} not found |
X404401STKNOF | 404 | stack {stack_name} not found |
X404403BKFNOF | 404 | backup file not found {path} |
X404410BKPCST | 404 | no backups found with consistency_id {consistency_id} |
X404413RSTNOF | 404 | restic snapshot {snapshot_id} not found |
X404415REPONF | 404 | repository not found {repo} |
X404424RSTGON | 404 | restic repository {repo} is gone: {detail} |
X404439BKPNOB | 404 | no backups found |
X404446BKPNSC | 404 | backup of {tenant}/{stack_name}/{environment} refused, no deployment exists in that scope: {path} is absent, and snapshotting an absent path writes an empty archive that reports completed |
X404447BKPGSC | 404 | {flag} for {tenant}/{stack_name}/{environment} refused, that deployment is not visible in the scope searched, so its integration peers are unknown rather than none, and a single-stack archive here would read as a complete group |
X404800RLBKNF | 404 | no backup found for stack {stack_name} before {before} |
X404816MTSNOF | 404 | mount session {session_id} not found |
X404819MTSFNF | 404 | file {path} not found in mount session |
X404831MTSNOH | 404 | no active mount handle for {handle} |
X404887BKPREP | 404 | this node holds no replica of deployment {deployment}, so backup job {job_name} has no project to run in |
X404951BKPOTN | 404 | backup restore target tenant {tenant} not found |
X404952BKPONF | 404 | orphan backup {backup_id} not found |
X404952VLFNOF | 404 | {path} is not in the volume |
X404953BKPIRN | 404 | orphan backup {backup_id} is in a repository no backup.repo names now: run shc backup orphan scan |
X404954BKPFNO | 404 | backup file {path} is not on {node}, the node that reads it |
X404957VLFNLO | 404 | volume {volume} is not laid out on this node |
X408419RSTTMO | 408 | restic operation timed out after {elapsed}, on {limit} |
X408821MTSEXP | 408 | mount session {session_id} has expired |
X409054OPRNCN | 409 | operation {operation_id}, the {kind} of {stack_name}, cannot be cancelled: {reason} |
X409080VFYUNP | 409 | backup {backup_id} of {deployment} is unproven since {since}: {elapsed_seconds} s of its {size_bytes}-byte deep read ran before the verify sweep’s {budget_seconds} s budget ran out, last proven {last_proof}, raise SHC_BACKUP_VERIFY_BUDGET_SECONDS |
X409104BKPRUN | 409 | operation {operation} already holds this backup scope, wait with shc operation follow {operation} before retrying |
X409107BKPMRR | 409 | a backup mirror is already running on this node |
X409409BKPCST | 409 | backups have different consistency ids and cannot be grouped |
X409445BKPNVR | 409 | no safety backup of {stack_name}: no node holds a render of it, so no backup can say what it holds; its mounts on node {node} would be discarded: {mounts}. shc uninstall --no-backup tears it down without an archive |
X409447BKPNAM | 409 | {name} names more than one backup: {backups}. Name the deployment with -s, or give the backup’s ID |
X409470BKPKLK | 409 | another backup key rotation or removal is in progress ({error}); nothing was changed, try again when it finishes |
X409487BKPCRS | 409 | deployment {stack} cannot restore a crash image; start it and back it up again |
X409488BKPSTR | 409 | deployment {stack} was not confirmed stopped for the whole capture, the archive was discarded; back it up again |
X409495RLCREF | 409 | backup relocate refused, nothing was rewritten: {repo} {detail} |
X409499BKPHLD | 409 | mount {mount} is on node {node}, which is not held for this stopped backup |
X409527CNVLIV | 409 | backup converter {name} refused after the scale window, {detail} |
X409658BKPVDT | 409 | mount {mount} is on the volume {volume}, which no node holds and which keeps what it was last written, and {reason} |
X409691CNVNDT | 409 | backup of {stack_name} failed: converter {converter} found no data to capture and the capture’s frozen copy holds none either, {detail} |
X409716BKPRNE | 409 | deployment {tenant}/{stack}/{environment} already exists, so no backup is restored as a new deployment under that name |
X409732BKPELS | 409 | backup {backup_id} is in {repo} on node {node}‘s own disk, which this node cannot read: {detail} |
X409839MTSCKS | 409 | derived backup {backup_id} failed checksum verification: recorded {want}, recomputed {got} |
X409843MTSDUP | 409 | backup {backup_id} is already mounted on this node at {mount_path} as mount {mount_id}: use that path, or shc backup umount {mount_id} first |
X409866HBDCON | 409 | host bind restore conflict for {path}, {detail} |
X409867HBDATT | 409 | host bind restore refused to wipe {path} for stack {stack}, {detail} |
X409876RSTHKR | 409 | restore of {deployment} refused by its pre_restore hook before anything was stopped or written, {reason} |
X409884VOLPER | 409 | backup of {stack_name} refused, {mounts} is a volume attached to another node, and shc backup create snapshots only this node’s disk, where that volume’s mountpoint holds none of its data; the scheduled path routes the capture to the node that holds it, so give this deployment a schedule with shc backup schedule set <cron> |
X409886VLMNMT | 409 | volume {volume} is attached to this node but nothing is mounted at {path}, so there is none of its data to show |
X409888BKPENT | 409 | backup job {job_name} cannot run as compose service {service} in replica project {project}, that name is one of the replica’s entries |
X409889BKPKEY | 409 | backup job {job_name} names {kind} {key}, which no replica of deployment {deployment} on this node declares, so the job would create it under the replica project |
X409890RSTFRN | 409 | restore of {deployment} from {file} refused before anything was stopped: node {node} renders it, and a recovery’s restore runs on the node that holds the deployment; run it on {node} |
X409891RSTNRH | 409 | restore of {deployment} refused before anything was stopped: node {node} renders it and holds none of its replicas, and the replicas on {holders} hold data a restore here cannot reach |
X409892RSTORN | 409 | restore of {deployment} refused: pod {pod} ordinal {ordinal} runs on node {node}, and its restore could not be routed there |
X409893BKPOHN | 409 | {operation} of {deployment} refused: {mount} is the directory of no group member a replica on this node holds |
X409894BKPCLN | 409 | backup {backup_id} is kept, a clone operation still needs its archive or the clone state that would free it cannot be read, {reason} |
X409895BKPGRP | 409 | backup of {deployment} refused: it reads one member of group {group} and none can be read, {reason} |
X409896VLMHLD | 409 | volume {volume} is held by {holder}, so it cannot be mounted on this node |
X409897RSTMNT | 409 | restore of {deployment} refused before anything was stopped: backup {backup_id} carries {mounts}, which {deployment} does not mount; its mounts are {declared}; name the one each belongs in with --map |
X409898RSTORD | 409 | restore of {deployment} refused: the archive carries pod {pod} ordinal {ordinal}, which is no group member of the target |
X409899BKPRPL | 409 | backup of {deployment} refused: it cannot capture the data of replica {replica} on node {node}, {why} |
X409948BKPOLK | 409 | backup {backup_id} is locked: it needs {needs} at {scope} |
X409953VLFEXI | 409 | {path} is already in the volume and was left as it is, replace it with overwrite |
X409954BKPKFE | 409 | not rotating: repository {repo} holds {count} that another estate wrote ({clusters}), and a rotation removes the key that estate may still open it with; restore what you need, delete those orphans with shc backup rm <id> -y or point backup.repo elsewhere, then rotate again |
X409954VLFDTC | 409 | volume {volume} is detached, so no node holds its files |
X409955VLFNEM | 409 | folder {path} is not empty, delete it with recursive to remove what is in it |
X409958BKPSNO | 409 | backup {backup_id} is locked: no secrets key or password set at {scope} or given here opens its secrets, and a backup made without backup.secrets_key or --secrets-password opens only on the cluster that made it |
X409958VLFMNY | 409 | volume {volume} is laid out on nodes {nodes}, name one of them with node |
X413425RSTOUT | 413 | restic {command} printed more than {limit} bytes of metadata; command stopped |
X416962VLFRNG | 416 | range {range} names no bytes of a {size}-byte file |
X499052OPRCNL | 499 | operation {operation_id}, the {kind} of {stack_name}, was cancelled by {actor} |
X500042RCVFAL | 500 | recovery failed for {stack_name}, {op} {error} |
X500045RCVCYC | 500 | recover deploy scheduler dependency cycle among {stacks} |
X500047RSTJOB | 500 | restore {phase} job failed {error} |
X500051SSEFAL | 500 | sse stream failed {detail} |
X500065BKPQAB | 500 | backup capture aborted for {stack_name}, consistency-expected pause failed {error} |
X500160BKPLNG | 500 | backup work failed for {items}, correct the reported failures before retrying those items |
X500173RLBSTP | 500 | the rollback of {stack} failed in {step}, which left the deployment {state} |
X500204BKSCSK | 500 | scheduled backup fire for {scope_key} at cron {cron} was skipped: the previous fire has not returned, so this scope captured nothing tonight; check what that fire is waiting on with shc backup ls --all-tenants and shc doctor run --category backup |
X500205BKSCTO | 500 | scheduled backup fire for {scope_key} exceeded its {budget} budget and was cancelled: the sweep did not reach every deployment in scope; shc backup ls --all-tenants shows how far it got |
X500380BKPATM | 500 | backup of {stack_name} read nothing: its application quiesced for one atomic snapshot and {detail} |
X500410RSTERR | 500 | restic command failed {detail} |
X500411EXPFIL | 500 | export failed {op} {error} |
X500412RSTLCK | 500 | restic repository is locked {detail} |
X500414RSTPAS | 500 | restic authentication failed {detail} |
X500415RSTBKN | 500 | failed to connect to restic backend {detail} |
X500416RSTENV | 500 | backup credential {key} did not resolve, {detail} |
X500417RSTPRN | 500 | restic prune failed {detail} |
X500418RSTRST | 500 | restic restore failed {detail} |
X500420CACHSY | 500 | failed to sync backup cache {detail} |
X500421RSTINT | 500 | restic {op} was interrupted before it finished, {detail}. This says nothing about the archive: the read was stopped by a daemon restart, a shutdown, a client hangup or a cancellation, not answered. Nothing is proven either way; re-run when the daemon is settled |
X500430BKPCMR | 500 | read compose failed {error} |
X500431BKPMKD | 500 | mkdir backup dir failed {error} |
X500432BKPSNV | 500 | snapshot volumes failed {op} {error} |
X500433BKPUNT | 500 | untar failed {error} |
X500434BKPCUP | 500 | post-restore docker compose up failed {error} |
X500435BKPSNS | 500 | snapshot {volume} failed {error} |
X500436BKPGSF | 500 | refusing to restore the consistency group {consistency_id}: {stack} cannot be protected first: {reason}. Nothing has been restored. {kept} |
X500437BKPRPB | 500 | refusing to roll {stack} back: {reason}. Nothing has been changed |
X500437BKPVRS | 500 | restore {volume} failed {error} |
X500438RSTRLX | 500 | restore could not loosen mount {mount} for the replay, {detail} |
X500439BKPNDR | 500 | no backups dir for the deployment, {error} |
X500440BKPDKR | 500 | docker {args} failed {error} {output} |
X500440BKPSDR | 500 | docker sidecar operation failed {error} {stderr} |
X500441BKPRSC | 500 | restic exited {error} |
X500442BKPSQL | 500 | {operation} failed {error} |
X500443RSTPBK | 500 | restore could not put back the modes it loosened on mount {mount}, {detail} |
X500444BKPDCL | 500 | backup daemon client {op} failed {error} |
X500446BKPDHT | 500 | backup daemon response status {http_status} {error} |
X500452BKPFRZ | 500 | backup of {stack_name} may have left the deployment paused, {detail} |
X500452BKPTHD | 500 | backup of {stack_name} left {replicas} down: it stopped at the thaw and did not start again, start it |
X500453BKPSTF | 500 | backup stop/start of {stack_name} did not complete, {detail} |
X500454BKPKRT | 500 | backup key rotation failed {detail} |
X500455BKPKRP | 500 | backup key rotation refused, --repo {requested} is not a repository the stored key opens ({configured}), and SHC stores one key with no repository dimension, so re-keying it would overwrite the key for those, leave --repo off or name one of them |
X500456BKPKPT | 500 | backup key rotation left {survivors} still able to open their repository, {detail} |
X500457BKPKST | 500 | backup key could not be recorded {detail} |
X500458BKPHOM | 500 | {job} on service {service} reported success but was oom-killed inside the container {detail} |
X500458BKPQJL | 500 | backup of {stack_name} could not journal its quiesce, so a daemon death mid-capture would leave the deployment quiesced with nothing to undo it, {detail} |
X500459BKPUNQ | 500 | backup of {stack_name} could not un-quiesce the deployment, it may still be read-only, {detail} |
X500460BKPEOM | 500 | {job} on service {service} was oom-killed inside the container {detail} |
X500460BKPPJL | 500 | backup of {stack_name} could not journal its pause, so a daemon death mid-capture would leave the deployment frozen with nothing to unpause it, {detail} |
X500465BKPCRP | 500 | backup of {stack_name} has data subjects with no bytes behind them: {subjects} |
X500466BKPPLC | 500 | backup of {stack_name} cannot run on this node: its deployment directory {deployment_dir} is not on this filesystem, so the capture would read nothing; run the backup on the node that holds the deployment |
X500467BKPHKF | 500 | backup hook {phase} of {stack_name} did not complete, so whatever it was responsible for staging is not in this archive: {detail} |
X500468BKPQAW | 500 | backup of {stack_name} aborted, its pause could not be acquired within the {window_seconds}s quiesce window set by {window_source}, and capturing unfrozen while the app is held quiesced would cost the outage without earning a trustworthy archive |
X500469BKPABN | 500 | backup {backup_id} of {tenant}/{stack_name} was abandoned by the daemon that is still running: the row was opened by this process, no process is executing it, and it was left non-terminal for {stale_seconds}s. No daemon restarted: the run returned without recording its own outcome, so the real cause is only in the daemon log. The claim is released and the backup did not happen |
X500469BKPQSK | 500 | backup of {stack_name} has now been skipped {consecutive} runs in a row: its pause could not be acquired within the {window_seconds}s quiesce window set by {window_source} on any of them, so this deployment has NO archive since {since}. Raise its window or fix what is holding the freeze |
X500470BKPCOV | 500 | backup coverage audit: {finding}. Deployments listed here cannot be restored from. shc doctor run reproduces this through its backup.coverage diagnosis, and shc backup ls --all-tenants --status=failed shows each failure’s recorded cause |
X500472BKPUNV | 500 | backup {backup_id} was not recorded completed: the repository would not give its snapshot back after the capture wrote it, {detail}. Restic exiting is not evidence the bytes are retrievable, and a row that says completed over an archive nothing can read is worse than no row at all. Re-run the backup; if it keeps failing here, check the repository with shc backup verify --deep <id> on a known-good archive and the credentials with shc config get backup.repo |
X500473BKPNOA | 500 | backup {backup_id} of {stack_name} captured data but produced no archive any restore could open, {detail}. It is recorded failed rather than completed with an empty location, because a row with no location is a row shc backup restore, shc backup export and shc backup rm alike can do nothing with. Nothing of the failed capture is kept: its staging tree goes with the run |
X500474BKPSRQ | 500 | scheduled backup {backup_id} of {stack_name} captured data but could not be sealed into the configured restic repository, {detail}. The run is failed and its transient staging, the plaintext .bak included, was discarded, because a scheduled backup never keeps a standing local archive. The next scheduled fire retries the whole capture; check the repository with shc config get backup.repo and the key with shc config get backup.password |
X500475BKPUNU | 500 | could not {op} the unusable stamp for {stack}: {reason} |
X500476BKPUNS | 500 | refusing to back {stack} up: {reason}. This deployment’s data is not the archive’s data, and backing it up would age the real archive out. Nothing has been paused or written. Restore it, which clears the stamp, or run shc backup clear-unusable --stack {stack} if you have repaired it by hand |
X500477RSTJNL | 500 | restore of {stack} refused before anything was stopped or written: its restore journal could not be written, {reason} |
X500478BKPPRO | 500 | backup protection audit ({check}): {finding}. shc doctor run --category backup reproduces this |
X500479BKPSTM | 500 | backup {backup_id} was restored, but no backup row {backup_id} in tenant {tenant} took its restored_at |
X500480BKPNSL | 500 | backup {backup_id} of {stack_name} captured data but could not be sealed into the configured restic repository, {detail}. The run is failed and its staging, the plaintext .bak included, was discarded: no archive is kept on local disk. Check the repository with shc config get backup.repo and the key with shc config get backup.password, then take the backup again |
X500497RLCFAL | 500 | backup relocate failed at {step}: {detail}; rows already rewritten stay rewritten, run it again to finish |
X500718BKPRNL | 500 | restoring backup {backup_id} as {stack} failed and left {tenant}/{stack}/{environment} installed, shc uninstall {stack} -t {tenant} -e {environment} -y removes it: {error} |
X500793CNVACC | 500 | converter {converter} of {stack} cannot inspect expected input {entry}: {detail} |
X500820MTSOPF | 500 | mount operation failed {op} {error} |
X500823MTSCMT | 500 | mount commit failed {op} {error} |
X500833MTSUMT | 500 | umount failed for {path} {detail} |
X500834MTSDEP | 500 | fuse mount prerequisite {binary} is not installed on this node, {hint} |
X500835MTSRDY | 500 | restic mount at {path} never became ready, {detail} |
X500836MTSVIS | 500 | mount at {path} is not browsable by the caller, {detail} |
X500837BKPSCP | 500 | {child} was not started: backup children run in their own scope in system-shcbackup.slice, outside the daemon’s memory budget, and the scope could not be made, {detail} |
X500838MTSMAT | 500 | materialising the edited tree failed {op} {error} |
X500846MTSPAS | 500 | backup mount for {deployment} refused: no restic password configured for this deployment |
X500847MTSREP | 500 | backup mount for {deployment} refused: no restic repository resolved for this deployment |
X500848BKPDBD | 500 | backup could not dump database {database} of plug {plug} on {provider}, {error} |
X500861VLMRMT | 500 | remote volume on node {node} could not be exposed {error} |
X500862VOLCAP | 500 | volume backed capture failed for {mount} on node {node} {reason} |
X500863PDMSNP | 500 | container filesystem snapshot failed {detail} {error} |
X500864VOLPRV | 500 | provision before restore failed for {mount} provider {provider} {reason} |
X500883VOLDIR | 500 | volume backed mount {mount} has no directory on {node} at {path}, so its capture would be an empty archive; the volume attachment names a node that does not hold this mount |
X500886RSTNFN | 500 | restore of {deployment} replayed its data and did not finish, {step} failed, {detail} |
X500891VLMBND | 500 | could not bind {source} at {path}, {detail} |
X500897VLMATT | 500 | volume {volume} is detached and could not be attached to {node} to mount it, {reason} |
X500934RLBKPR | 500 | failed to create pre-rollback backup {error}; nothing has been restored and the deployment is untouched. A deployment that is already stopped or already lost its data cannot be snapshotted, which is exactly when this fires during a rescue, and it is also when there is nothing left worth rolling back to. Re-run with --no-rollback to restore without a rollback point |
X500935RLBKRS | 500 | rollback failed during restore of {stack_name} {error} |
X500960VLFIOE | 500 | {op} {path} failed: {error} |
X501400UNGFIL | 501 | ungroup endpoint requires file upload |
X501832MTSPLT | 501 | fuse mount unsupported on platform {platform} |
X502107BKPMRI | 502 | backup mirror incomplete: {repos}; each copy is still a valid, older repository |
X502112BKSFWD | 502 | backup schedule leader relay failed for {op}, {detail} {error}, nothing was changed; retry, or run the command on the leader node |
X502300RCVSHP | 502 | recover of {stacks} lands on node {node} and could not run there: {reason} |
X502496RLCOPN | 502 | backup relocate could not open {repo} with the configured backup credentials, nothing was rewritten: {detail} |
X503053OPRLKP | 503 | operation {operation_id} is not on this node and not every other node could be asked for it, {detail}, ask again |
X503479BKPROW | 503 | backup {backup_id} of {tenant}/{stack_name} was refused, its row could not be written to the ledger ({detail}); nothing was captured or staged, run it again once the store answers |
X503489BKPDMN | 503 | shc backup create runs on the daemon, and this CLI reaches none: no daemon runs in this process and no daemon endpoint is configured. Start shcd on this node or point the CLI at one with shc ctx |
X503890BKPREM | 503 | backup job {job_name} in project {project} was interrupted, the replica it ran in was removed from this node, retry the job |
X503941BKPINW | 503 | the orphan index is not wired in this process: no repository list resolves here |
X503947BKPIRU | 503 | backup repository {repo} named at {scope} is unreachable: {detail} |
X503956BKPIRF | 503 | {count} could not be read: {repos} |
X507295RCVROM | 507 | recover of {stacks} refused before any image was pulled: it lands on {node}, the node it runs on, which has {free} free where their images need {need} and {floor} is kept free; nodes with room: {fits}; copy the archive to one of them and run shc recover there |
X507299RCVNRM | 507 | recover of {stacks} refused before any image was pulled: no node has disk for their images on one node; the closest, {node}, has {free} free where they need {need} and {floor} is kept free |
X507460BKPSPC | 507 | refusing the backup: {target} has {free} free but the run needs an estimated {required}, {estimate} of deployment data plus staging and margin, so nothing has been quiesced or written; free space or point the backup at a larger filesystem |
X507559BKPPSP | 507 | refusing to pull the capture of {capture} from {node}: {target} has {free} free but it needs {required}, the {size} the holder reported plus staging and margin, so none of it was written here; free space or point the backup at a larger filesystem |
X507826MTSSPC | 507 | not opening backup {backup_id} to browse: {target} has {free} free but its copy needs {required}, the {size} archive plus margin, so nothing was written; free space there and open it again |
branding
Section titled “branding”Source: modules/branding
Count: 14
| Code | HTTP | Message template |
|---|---|---|
X200880BRDUNB | 200 | branding edge {plug} resolves unbranded with {reason} |
X400880BRDNAM | 400 | invalid brand name {name} must match {pattern} |
X400881BRDFIL | 400 | invalid branding file {file} with {reason} |
X400882BRDSIZ | 400 | branding file {file} too large {size} bytes exceeds {limit} |
X400883BRDENC | 400 | branding file {file} is not valid base64 {error} |
X403880BRDENT | 403 | brand management needs the {feature} entitlement, which this estate’s SHC license does not include, {feature} is carried by the Pro and Enterprise tiers, see shc license status |
X403881BRDWLB | 403 | brand {name} needs the {feature} entitlement, named per-tenant brands are Enterprise-only, the branding entitlement alone manages only the brand named default, see shc license status |
X403882BRDDEN | 403 | the s3 connection {connection} rejected the brand store credentials with {detail} |
X404881BRDNOF | 404 | brand {name} not found |
X404882BRDCON | 404 | branding requires an estate connection with an s3 provider and {which} is visible to the master tenant |
X404883BRDBKT | 404 | branding bucket {bucket} does not exist on the s3 connection {connection} |
X409881BRDAMB | 409 | multiple estate s3 connections could hold the brand store {names} and branding will not guess |
X502880BRDOBJ | 502 | brand store S3 operation failed while {op} with {detail} |
X503880BRDNAV | 503 | branding not available with {reason} |
Source: modules/ca/caapi, modules/ca
Count: 24
| Code | HTTP | Message template |
|---|---|---|
X200106CAESCD | 200 | best-effort delete of pfSense-side CA copy failed for tenant {tenant} ref {ref}, remove it manually |
X200107CAKEYT | 200 | keyType is advisory for key-escrow and was ignored for tenant {tenant} so the backend chose the algorithm |
X200109CAINTX | 200 | tenant CA {tenant} intermediate nears expiry on signer connection {conn}, reprovision before it lapses |
X200110CARPRV | 200 | tenant {tenant} CA re-provisioned, clients trusting the old root must install the new one |
X200114GRTRMT | 200 | global root re-minted to recover a keyless trust anchor, clients trusting the old root must install the new one |
X200118CASPLT | 200 | tenant {tenant} CA intermediate key did not pair with its certificate, re-derived it from the global root |
X400102CAMANL | 400 | manual CA import invalid {op} {error} |
X400111CARPSR | 400 | invalid reprovision source {detail} |
X400113CARSVD | 400 | tenant ca name {name} is reserved for a system ca |
X404112CACRTN | 404 | no certificate found for name {name} |
X409112CARPRN | 409 | operation {operation} already reprovisions the CA of tenant {tenant}, wait with shc operation follow {operation} before retrying |
X500096CAGENM | 500 | failed to mint CA material {op} {error} |
X500097CALEAF | 500 | failed to sign leaf certificate {op} {error} |
X500098CASTOR | 500 | failed to store CA for tenant {tenant} {op} {error} |
X500099CALOAD | 500 | failed to load CA for tenant {tenant} {op} {error} |
X500100CAVLTU | 500 | vault is not available so CA private keys cannot be stored or read |
X500103CASGNU | 500 | ca-signer backend not available for tenant {tenant} connection {conn} |
X500104CASIGN | 500 | failed to csr-sign intermediate for tenant {tenant} {op} {error} |
X500105CAESCR | 500 | key-escrow CA operation failed {op} {error} |
X500108CAWEDG | 500 | tenant CA {tenant} is wedged with keys absent for provenance {provenance}, run shc ca reprovision |
X500175CARPLN | 500 | the reprovision of the CA of tenant {tenant} stopped on an internal fault {detail} |
X500176CARPST | 500 | the reprovision of the CA of tenant {tenant} failed in {phase} after {done} |
X503090GRTNRD | 503 | global root not ready {op} {error} |
X503113CANDNI | 503 | the per-node leaf listing is not wired in this process, run it against a daemon that has joined its cluster |
capabilities
Section titled “capabilities”Source: modules/capabilities
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X500211CAPFTC | 500 | capabilities no fetcher provided |
X503940CAPDIS | 503 | {command} requires the ‘{feature}’ feature, which is not available on this SHC instance. Deploy the backing module, e.g. shc install keycloak for user-management features, and try again. |
capacity
Section titled “capacity”Source: modules/capacity
Count: 10
| Code | HTTP | Message template |
|---|---|---|
X200195CAPROP | 200 | idle autoscale node {node} was cordoned, and a pending replica fits it, so it is returned to service |
X200196CAPUNC | 200 | autoscale cordoned node {node} and did not drain it, and it {why}, so it is returned to service |
X200197CAPDRN | 200 | autoscale node {node} has held no replica or volume since {since}, past the {cooldown} cooldown, so it is cordoned and drained |
X409193CAPRFS | 409 | {deployment} is pending, and run again it was refused: {refusal}; it stays pending and runs again each pass, uninstall it to cancel it |
X409195CAPDSP | 409 | {deployment} was held for capacity ({held}), and another install of it ({other}) took its place, so the held one will not run; run the install again if it is still wanted |
X409196CAPLFT | 409 | node {node} left the autoscale set drained, so it stays cordoned while the portal removes its server; if the server stays, uncordon the node to keep it or remove it from the cluster |
X409197CAPPND | 409 | {deployment} is pending: no node has room for {replicas} now: {nodes}; it runs when a node has room, and nothing changes until then; uninstall it or lower its scale to cancel it |
X500199CAPSTO | 500 | capacity store {op} failed{error} |
X503198CAPNST | 503 | the capacity store is not wired on this daemon |
X503199CAPDRF | 503 | the {step} of idle autoscale node {node} failed: {error}; the next capacity tick tries again |
catalog
Section titled “catalog”Source: modules/catalog
Count: 5
| Code | HTTP | Message template |
|---|---|---|
X400272INTOGN | 400 | --host is gone, write --into {value} |
X400960CATINP | 400 | catalog invalid input {reason} |
X404960CATNOF | 404 | catalog application {application} not found |
X409960CATAMB | 409 | catalog application {application} is ambiguous across repos {repos} with digests {digests} |
X500960CATOPF | 500 | catalog {operation} failed |
catalogbuild
Section titled “catalogbuild”Source: modules/catalogbuild
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400611CATBARG | 400 | invalid catalog build request {reason} |
X500611CATBLD | 500 | catalog build failed {reason} |
certbroker
Section titled “certbroker”Source: modules/certbroker
Count: 8
| Code | HTTP | Message template |
|---|---|---|
X200473CRTSTG | 200 | delivered {delivered} certificate for host {host} while its resolver requests {requested}, it will not validate against a public trust store |
X200477CRTROT | 200 | rotated delivered certificate for host {host} to serial {serial} class {class} reloading {reloaded} services |
X400470CRTDCL | 400 | invalid certs declaration in app {app} {detail} |
X403471CRTSCP | 403 | deployment {deployment} is not granted host {host} |
X404472CRTHST | 404 | no delivered certificate material for host {host} in tenant {tenant} |
X500474CRTSRC | 500 | certificate source failed {op} {error} |
X501476CRTNIW | 501 | cert-delivery broker is not wired, see docs/proposals/2026-08-06-cert-delivery-broker.md |
X503475CRTPND | 503 | certificate issuance pending for host {host} |
Source: cli
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X403219HUDREG | 403 | cannot read {path} for the active cluster {cluster}, make it readable by this user or run shc ctx --reset |
X404217HUDEDT | 404 | no editor found, set $EDITOR |
X501216HUDTUI | 501 | this build carries no hud tui, rebuild with make build |
Source: modules/clone
Count: 88
| Code | HTTP | Message template |
|---|---|---|
X200607CLNSRV | 200 | the rollback of {deployment} put back {served}, the spec it served on {node} before the move, in place of {current}: the update to {current} is rolled back, so run it again once {node} can start it |
X200628CLNARC | 200 | the pre-move backups are kept at {path}, {count} in all, and each comes under normal retention once the move releases it, or stays in the move’s staging until the move is recovered |
X200652CLNSCV | 200 | could not remove scratch volume {volume} of {tenant}/{environment}/{stack} on node {node}{error} |
X200656CLNMVK | 200 | the move of replica {replica} of {deployment} could not {step} its record that status reads, so status may read the deployment degraded while it moves; the move goes on: {cause} |
X200664CLNRKP | 200 | replica project {project} moved back to its source after node {node} was bound to it; that node’s copy of its volumes ({volumes}) is kept, labelled shc.move-operation={operation}, and nothing deletes it |
X200672CLNRAS | 200 | replica project {project}: the target’s copy from shc.move-operation={operation} {action} at {path}; it is kept and nothing deletes it |
X400600CLNCON | 400 | deployment {name} has connections, move the integration set together with --all-connections, add --closure when a peer has providers of its own, or leave it on its current node |
X400602CLNCAN | 400 | {operation} cancelled |
X400608CLNRNT | 400 | invalid runtime {runtime}, expected one of docker, podman, incus or apple |
X400620CLNDSC | 400 | a move off a dead node is not possible, {reason} |
X400626CLNBIG | 400 | the integration closure of {name} is {count} deployments, more than the {limit} a single move carries, this is an estate migration rather than a relocation, move the shared providers first or drain the node instead |
X400630CLNXSC | 400 | refusing to move {member}: it lives in {member_scope} while the move targets {op_scope}, and a scope-changing move recreates every member in the operation’s scope: which would create a second copy of {member} there and destroy the original. Move it on its own, or drop the scope change |
X400647CLNNOD | 400 | a clone does not name a node ({node}), the copy is placed by the source’s rules; add one with --where node={node} |
X400649CLNOLD | 400 | --rename {value} is the retired spelling, write --rename {now} |
X404600CLNSRC | 404 | stack {name} not found |
X404607CLNNOD | 404 | node {node} not found |
X409600CLNCOL | 409 | stack {name} already exists in {tenant_name}/{environment} |
X409601CLNAUF | 409 | could not generate unique name for {stack_name} after 100 attempts |
X409606CLNSRB | 409 | refusing to move {deployment} off node {node}: if the move failed, its rollback could not start it there again, since node {node} lacks {missing} and {disk}. Nothing was stopped. Make room on {node}, then move it again |
X409615CLNCAP | 409 | refusing to {verb} {stack}: replica {replica} on node {node} holds data the backup cannot capture, {why}; the source is untouched and nothing was written |
X409617CLNDND | 409 | node {node} is not dead, its cluster_state is {state} and not unreachable |
X409618CLNDPR | 409 | node {node} is not dead, it answered a probe at {addr} |
X409621CLNDUR | 409 | the surviving volume for mount {mount} on provider {provider} cannot attach to node {node}, change the rules to leave a node it reaches, or pass --restore-from-backup to restore it there from the latest backup with the surviving volume set aside |
X409623CLNPRO | 409 | teardown refused, deployment {tenant}/{stack} is protected, run shc unprotect {stack} first |
X409624CLNPRU | 409 | teardown refused, cannot determine whether {tenant}/{stack} is protected ({reason}), refusing rather than risk destroying protected data |
X409639CLNRLK | 409 | refusing to relocate {deployment}: a relocation on {node} {holds}, and nothing has been stopped or moved; {next} |
X409640CLNMNT | 409 | {dir} is left in place, never set aside, because {mount} beneath it is a mounted filesystem a later reclaim would delete through; unmount it, then move the directory aside by hand |
X409641CLNSTL | 409 | refusing to move {deployment}: it runs on {node}, not on {expected} where the move was planned from, and nothing has been stopped or moved; plan again |
X409642CLNRLL | 409 | the relocation of {deployment} no longer holds its lease, which another executor took over or its own executor recalled, so it stops here and changes nothing further |
X409643CLNUNR | 409 | the move of {deployment} failed while {node} may still be working on it or running it, so its sources stay stopped and its record is kept, which shc interrupted lists |
X409645CLNOCC | 409 | {deployment} may still be running on {node} from a move that did not finish, so it is not relocated again until that move is finished forward or reverted with shc interrupted on the node that ran it, or {node} is proven dead |
X409646CLNRLF | 409 | the relocation of {deployment} could not renew its lease for two thirds of its lifetime, so it stops here before anyone may take the lease over |
X409647RELDUR | 409 | deployment {name} cannot relocate, its durable volumes [{volumes}] are only on dead node {node} and cannot be reattached on {target}, pass --restore-from-backup to restore them from its latest backup |
X409648RELBKP | 409 | deployment {name} cannot relocate, it has no backup to restore its durable volumes [{volumes}] from |
X409650RELSHR | 409 | deployment {name} cannot be restored from backup, its mount {mount} survives on a share with no volume to set aside and the restore would write over it, change the rules to leave a node that reaches the share |
X409651RELCON | 409 | deployment {name} cannot be relocated off {node} alone, it is connected to {edges}, as shc integration ls -s {name} lists its connections; drop a connection first with shc update |
X409652CLNDIR | 409 | backup of {stack}/{environment} cannot run, {detail}; nodes asked: {nodes} |
X409654CLNRNR | 409 | the copy {deployment} runs and its rules are not recorded: {why}; record them with shc constraint set --scope deployment on {deployment} |
X409655CLNRLO | 409 | replica project {project} is not moved: the rollout of {deployment} to {spec} is {state}, and a replica moved before it ends is put back on that spec, which finishes it for the node it left; nothing was stopped |
X409657RELCNF | 409 | the relocation plan for {name} changed since it was confirmed and now moves {moves}, so nothing ran; plan it again and look at the new plan before you confirm it |
X409661CLNRST | 409 | replica project {project} cannot move: stop on {node} was not verified: {error} |
X409662CLNRVO | 409 | replica project {project} cannot copy: target volume {volume} already exists |
X409663CLNRMV | 409 | replica project {project} cannot move: {why} |
X409665CLNDHL | 409 | {deployment} cannot move off dead node {source}: volumes {volumes} are attached where no replica of it is bound, and a move off a dead node takes no volume a live node may hold; free them on that node, or rebind them to {target} with shc volume rebind once nothing there uses them |
X409668CLNSRG | 409 | deployment {deployment} cannot move bring-up-first: {why} |
X409669CLNCRT | 409 | {deployment} is not moved: its backup.yaml declares {mounts} critical, and its compose mounts none of them as data a move carries, so the move would leave them behind; nothing was stopped |
X409671CLNRWK | 409 | relocating {name} stopped at replica {replica}, which did not land on {node}: {error}; moved: {landed}; not moved: {unmoved}; the rule change is not recorded, run the update again once it is fixed |
X409672CLNROW | 409 | relocating {name} moved {landed} and its row did not move from {from} to {to}: {error}; the rule change is not recorded, run the update again once it is fixed |
X409673CLNRDY | 409 | relocating {name} moved {replica} to {node} and it did not read ready: {error}; moved: {landed}; not moved: {unmoved}; no other member leaves its node until {replica} reads ready, then run the update again |
X409674CLNWRT | 409 | relocating {name} moved {landed} and no member of {group} took its writer role back: {error} |
X409675CLNRNC | 409 | {name} cannot be renamed to {target}: {consumers} bind to it by name and the rename would leave them bound to {name}; nothing was stopped. Disconnect each with shc update |
X409680CLNSTG | 409 | deployment {deployment} cannot move its storage: {why}; nothing was stopped |
X409682CLNDRP | 409 | refusing to drop {operation_id} without restoring {stack}: the record is the only map of what the rename moved, so roll it back with shc roll-back {operation_id} or finish it with shc finish-forward {operation_id} |
X409690CLNRBK | 409 | refusing to roll {operation_id} back, {reason} |
X409692CLNFRC | 409 | deployment {deployment} moves to {to} only by copying {volumes}, which its storage does not follow; pass --force to copy them, nothing was stopped |
X500601CLNROL | 500 | rollback failed {reason} {error} |
X500602CLNBKP | 500 | backup failed during clone/move {op} {error} |
X500603CLNRCV | 500 | recovery failed during clone/move {op} {error} |
X500604CLNUNI | 500 | uninstall failed during move {reason} {error} |
X500605CLNRNM | 500 | rename failed {op} {error} |
X500609CLNRND | 500 | clone random suffix failed {error} |
X500610CLNFAL | 500 | {operation} failed {error} |
X500612CLNREQ | 500 | {operation} request failed for {source} |
X500613CLNRPF | 500 | {operation} reported failure |
X500614CLNDEG | 500 | refusing to move {stack}: the backup taken for it is degraded ({markers}), so the archive that would become its only copy is not known to carry its data. Take a clean backup and retry |
X500614CLNNWR | 500 | {operation} service not wired |
X500616CLNMOV | 500 | deployment move step failed {op} {error} |
X500622CLNDMV | 500 | move off a dead node failed at {op} {error} |
X500625CLNLND | 500 | move aborted before destroying the source, the recovery reported success but {reason} |
X500626CLNHLT | 500 | move aborted before destroying the source, the target is not proven healthy, {reason} |
X500627CLNSRV | 500 | the move failed and its rollback could not prove the source is serving again, {reason} |
X500629CLNDST | 500 | refusing the destructive step of the move, {reason} |
X500630CLNDAT | 500 | move aborted before destroying the source, the target’s data is not proven, {reason} |
X500630CLNJRN | 500 | the move journal could not be {operation}: {detail} {error} |
X500631CLNRCM | 500 | reclaim could not complete, {reason} |
X500631CLNRSM | 500 | the interrupted move {operation_id} of {stack} was not resumed automatically, {reason} |
X500632CLNRNF | 500 | the rename of {source} to {target} cannot be finished, {reason} |
X500633CLNJNF | 500 | no interrupted operation {operation_id} is recorded on this node: {detail} |
X500634CLNFWD | 500 | refusing to finish {operation_id} forward, {reason} |
X500636CLNNAR | 500 | moving {stack} by volume rebind with NO pre-move archive (--no-backup), its block volumes are detached and re-attached with nothing to recover from if one does not come back |
X500637CLNARF | 500 | refusing to move {stack} by volume rebind: no pre-move archive can be taken, {reason}. Nothing has been stopped and no volume detached. A rebind detaches each block volume, bumps its lease and re-attaches it on the target, and the archive is what you have if one does not come back. Fix the cause, or re-run with --no-backup to move without an archive |
X500638CLNRBF | 500 | the roll-back {operation_id} of {stack} stopped at the {step} step and is kept, {reason} |
X500639CLNUNS | 500 | relocating {stack} to node {node} did not settle, {reason}; the source is left stopped so {stack} never runs twice; check node {node} and bring {stack} up on exactly one node |
X500647RELRST | 500 | deployment {name} is installed on {node} and restoring its durable volumes from backup {backup} failed, {error}, restore it with shc backup restore {backup} |
X503181CLNRUL | 503 | a rule change that relocates needs the daemon’s fence store to place the move, and none is wired here |
X503640CLNRLU | 503 | the relocation lease on {deployment} is unavailable: {reason} |
X503644CLNPLC | 503 | refusing a move planned by {planner}: this node cannot check that the plan still stands, and nothing has been stopped or moved |
X507632CLNSPC | 507 | refusing to stage the archives: {staging} has {free} free but the operation needs an estimated {required}, {estimate} measured plus margin, so nothing has been stopped or copied; free space or move the staging dir to a larger filesystem |
cluster
Section titled “cluster”Source: modules/cluster/commands, modules/cluster
Count: 121
| Code | HTTP | Message template |
|---|---|---|
X200030JNSELF | 200 | enroll for {node} resolved the joiner’s own raft address {raft_addr} as its join address, dropping it, this node cannot see the cluster leader |
X200031VOTUNK | 200 | voter grant ledger unreadable while enrolling {node}, joining as a non-voter, which the suffrage pass promotes if the voter set needs it {error} |
X200032TKNREL | 200 | could not release the bootstrap token after a failed enroll of {node}, it stays consumed and the retry needs a freshly minted token {error} |
X200033CAPOVR | 200 | enrolling {node} left the estate over its licensed {limit}, holding {have} against {cap}, concurrent joins are measured against the roster as it stood before them |
X200034CAPREL | 200 | could not release the capacity slot claimed for {node} after a failed enroll, the estate still counts it and shc node forget is the remedy {error} |
X200035NODNMR | 200 | node name {name} was claimed by a simultaneous enroll, retrying with the next free suffix |
X200036CLSOVC | 200 | the drain placed {stacks} on {node}, which was already committed to {committed} against a measured {capacity}, capacity cannot refuse a drain destination because refusing would strand the workload on the node being emptied, so the placement stands and is reported instead, run shc rebalance --plan once the drain finishes |
X200044CRTCHK | 200 | cluster cert rotation check failed {op} {error} |
X200047CLSDLF | 200 | {stack} stays on {node}: its install failed, so nothing of it runs there, and the drain could not move it, {reason}, shc cluster rm {node} refuses until shc update {stack} repairs it or shc uninstall {stack} removes it |
X200048JNSTOR | 200 | store tier plan unreadable while enrolling {node}, joining as a store replica, which the tier pass moves to client if the plan says so {error} |
X200166LVRMVD | 200 | node {name} ({id}) was removed from the cluster by another node: its cluster services and deployment containers stopped and its membership state moved to {archive} |
X200216CLSSUC | 200 | suffrage {kind} of {node} done: {steps} |
X200218CLSSTC | 200 | store tier move of {node} to {role} cancelled, the plan now makes it a {planned}, it keeps the role it holds and the next pass starts the move the plan wants |
X200941CRTRNW | 200 | internal api mtls leaf renewed for {node} valid until {not_after} via {via} |
X200942CRTSGN | 200 | cluster ca signed an internal api mtls leaf for {node} valid until {not_after} |
X200948CRTRLD | 200 | internal api mtls leaf reload failed {error} |
X400017NODDEP | 400 | node {name} is still named by {count} deployment rows: {deployments}; {basis}. {remedy} |
X400021ALRCLS | 400 | this node is already part of a cluster, run shc node leave to leave it cleanly or shc node join --force <token> to wipe its local cluster state and rejoin |
X400022INVTKN | 400 | invalid or expired join token {reason} {error} |
X400042VLTLKD | 400 | vault is locked, unlock with shc vault then re-run shc init |
X400064VLTPWS | 400 | vault master password must be at least {min} characters |
X400136STRROL | 400 | store role {role} is none of voter, replica or client |
X400270INGHST | 400 | --host is gone, write --ingress-host {value} |
X400278JNSCHM | 400 | join endpoint {endpoint} is not https, the bootstrap token is only sent to the cluster’s HTTPS entrypoint |
X400291NODRSV | 400 | node name {name} is reserved, it is the name on the cluster’s join certificate |
X400292NODDNS | 400 | node name {name} is too long, its cluster dns label {label} is over {limit} characters |
X400384FBROLD | 400 | {end} is the retired spelling, write {now} |
X400400CLSDRN | 400 | invalid drain request for node {node} |
X400401CLSDRP | 400 | drain of {node} is refused because it would strand {count} deployments with placement pins {pins} naming this node, so {stacks} cannot move to another node, repin the deployment, drain a different node, or re-run with --force to stop it in place deliberately, nothing was changed, the node is still schedulable |
X400402CLSDRB | 400 | this drain would take the last serving copy of {detail}, a group with two or more members stays available only while one of them serves, and SHC’s relocation is a backup, a cross-node ship and a bring-up run serially, so {stacks} would be offline for the move rather than merely losing redundancy, bring up a replica on another node first, drain a different node, or re-run with --force to accept the outage deliberately, nothing was changed, the node is still schedulable |
X400421CLSCRD | 400 | invalid {verb} request for node {node} |
X400422CLSRUN | 400 | runtime {runtime} is not supported on the new line; use docker, podman, incus or apple |
X400423CLSDRM | 400 | drain of {node} is blocked because deploy.disruption is never for {stacks}, a drain may not move any of their replicas, set it to rolling with shc update |
X400589MSHMAC | 400 | mesh client up runs on macOS |
X400591MSHSUD | 400 | mesh client cannot tell which operator runs it, {reason} |
X400593MSHPKY | 400 | mesh client private key does not parse |
X400612INICFR | 400 | --connection-file {file} could not be read, {error} |
X400613INICFD | 400 | --connection-file {file} {problem} |
X400614INICON | 400 | connection {name} from {file} was not made, {error} |
X400615INISTO | 400 | --storage {name} is not a volume connection, the volume connections are {have} |
X400616INIREP | 400 | --repo {value} {problem} |
X401022TKNCNS | 401 | bootstrap token already consumed for node {node_name} |
X401023TKNEXP | 401 | bootstrap token expired for node {node_name} |
X401047CRTIDM | 401 | cert rotation rejected, caller identity does not match any registered node {reason} {node} |
X403003LDRNLY | 403 | operation requires the cluster leader, current leader is {leader} |
X403092ENRSIP | 403 | enrollment rejected, claimed physical_ip {claimed} does not match connection source {source} |
X403283CLSPSM | 403 | peer status refused: {caller} is not a node of this node’s signed membership table |
X403285ENRNAT | 403 | enrollment rejected, this node’s own address {claimed} is private and its request arrived from {source}, so it is behind NAT: run shc node join again with --public-address {source}, the address the cluster reaches it at |
X403590MSHCSU | 403 | mesh client up needs root to open a utun, run it with sudo |
X403991LVEEEO | 403 | leaving a cluster requires SHC EE, this binary carries no multi-node leave orchestrator |
X404020CLSNOF | 404 | cluster node {name} not found |
X404024CLSLOG | 404 | no logs for {service} on {node}, {path} is not there and the journal of unit {unit} has no entries{error} |
X404028NODNOF | 404 | node {name} not found in cluster |
X404201CLSNNF | 404 | cluster member {name} not found in raft membership |
X408400CLSDRT | 408 | drain timed out waiting for deployments to clear |
X408422CLSDRH | 408 | drain timed out waiting for deployments to clear, {held} is still on the node |
X409013STRVOT | 409 | {node} is outside the control plane, so it cannot be pinned a voter |
X409025LVDEPS | 409 | cannot leave, this node still hosts {count} deployments named {deployments}; {remedy} |
X409029CLSGEN | 409 | refusing to initialize a new cluster: this host’s node identity is gone but it still carries live cluster state ({findings}), a fresh genesis here would mint a second cluster over data the existing one still owns, rejoin it with shc node join, or run shc init --force to wipe the local cluster state and start over |
X409166LVRMNM | 409 | a removal notice for node {notice} reached node {local}, nothing was stopped |
X409200CLSQUR | 409 | refusing to demote, {voters_after}/{required} voters would remain |
X409201CLSRMQ | 409 | refusing to remove voter, {voters_after}/{required} voters would remain |
X409202CLSRMR | 409 | refusing to remove voter, {reachable_after}/{required} reachable voters would remain |
X409204NODNMC | 409 | could not claim a unique node name for {name} after {attempts} attempts, simultaneous joiners are contending for it, give each node its own name with shc node join --name |
X409206CLSRBN | 409 | cannot rebalance before removing voter {node}, there is no healthy non-voter inside the control-plane fence to promote ({reason}), add one to the fence and retry, or remove without --rebalance and the suffrage reconciler promotes a replacement once the fence has one |
X409207NODLST | 409 | {node} is the only node of this cluster, and a cluster cannot forget its last node, nothing was changed |
X409216CLSSUB | 409 | cannot remove {node} while another suffrage change is in flight, retry once shc cluster status shows none |
X409400CLSDRD | 409 | node {node} is already drained |
X409400CLSREC | 409 | force-leader recovery already in progress |
X409403CLSPRT | 409 | refusing force-leader recovery, {live} not provably dead ({peers}), so this estate may be partitioned rather than dead and rewriting membership to this node alone could leave two independently committing clusters |
X409405CLSLDR | 409 | refusing force-leader recovery, {leader} answers as the cluster’s leader, so quorum is not lost and there is nothing to recover |
X409407CLSRVU | 409 | refusing force-leader recovery, its split-brain safety gate could not be evaluated ({reason}), so this node cannot prove the other voters are dead |
X409408CLSCRD | 409 | refusing to {verb} {node}, its availability is {state} and only {use_instead} may change that |
X409410CLSDRS | 409 | the drain of {node} was stopped by {by} after {moved} of {planned} had moved, and what moved stays where it went |
X409411CLSASH | 409 | autoscale node {node} holds no tenant replica but still runs {held}, which autoscale never moves, so it is not cordoned or drained and stays in service |
X409427CLSDTA | 409 | drain of {node} is refused before anything moved because {reason}, put the deployments it is tied to on one node and drain again, nothing was changed |
X409588MSHNGW | 409 | no live gateway is on mesh0, an operator client reaches the cluster through one |
X500008NODREM | 500 | failed to remove node {op} {error} |
X500021CLSINT | 500 | cluster internal error {op} {error} |
X500022CERGEN | 500 | failed to generate certificate {op} {error} |
X500023JNFAIL | 500 | failed to join cluster {op} {error} |
X500024LVFAIL | 500 | failed to leave cluster {reason} {error} |
X500027RMLVFL | 500 | failed to request remote leave for node {name} {reason} {error} |
X500028TKNGEN | 500 | failed to generate join token {op} {error} |
X500046CRTCAU | 500 | cert rotation failed cluster ca unavailable {op} {error} |
X500047CACSTR | 500 | cluster ca store {op} {error} |
X500048CACUNP | 500 | cluster CA not provisioned {reason} |
X500049CAROTF | 500 | cluster CA rotation {op} {error} |
X500050CCALOS | 500 | cluster CA material is pinned on this node but its replicated row is gone, so the CA private key went with the database and nothing here can re-mint or reconstruct it, waiting will not fix this, recover the database from the pre-flip sqlite at |
X500051GRROTF | 500 | global root rotation {op} {error} |
X500060CRTNLF | 500 | internal cert renew failed on a follower and there is no local fallback, the cluster leader is the only signer {op} {error} |
X500201CLSREC | 500 | force-leader recovery failed {op} {error} |
X500202CLSPRO | 500 | promote to voter failed {error} |
X500203CLSDEM | 500 | demote from voter failed {error} |
X500207CLSRBS | 500 | promote-before-departure failed at step {step} for candidate {candidate}, voter {node} was not removed and the voter set is unchanged, fix the candidate and re-run the same command to resume {error} |
X500211RFTTLF | 500 | raft tls required by this cluster but node cert material is unavailable, re-run shc node join --force {error} |
X500216CLSSUF | 500 | suffrage {kind} of {node} failed at step {step}, the next pass retries {error} |
X500400CLSDRO | 500 | drain failed for node {node}: {reason}{error} |
X500406CLSDRP | 500 | drain of {node} partially applied, {succeeded} of {planned} deployments left the node and {failed} did not, the node is left partially_drained and re-running the drain resumes what is still on it {reason} |
X500407CLSDRJ | 500 | the drain of {node} did not move {stack}, its write-ahead journal entry could not be recorded, {detail}, a cutover with no durable record is one a re-run repeats against a deployment that has already moved, so it was not issued and the deployment is untouched |
X500408CLSDRU | 500 | the drain of {node} refuses to re-issue the cutover of {stack}, which an earlier run began at {since} and never recorded an outcome for, so whether it committed is unknown, check where {stack} is serving from and either finish or undo it by hand before re-running the drain |
X500409CLSCRO | 500 | {verb} failed for node {node} {reason} {error} |
X500592MSHPRC | 500 | mesh client peers refresh as the operator failed {error}, {stderr} |
X500911RNDFAL | 500 | os entropy source unavailable {error} |
X500912CRTATM | 500 | atomic cert write {step} {error} |
X502277JNSIGN | 502 | the join answer from {endpoint} is not signed by the cluster the join token names, nothing in it was used, {detail} |
X503021CLSQRM | 503 | cluster quorum lost, {reachable} of {voters} raft voters reachable and {required} are required to elect a leader, unreachable voters {peers}, no write can commit until enough voters return, restore them or re-form a single-node quorum on a survivor |
X503022CLSUNO | 503 | cluster state is unobservable from this node, the raft engine did not answer the {op}, so quorum can be neither confirmed nor denied, check that shc and its raft engine are running here and that the other voters are reachable |
X503070RCNDMN | 503 | daemon not reachable {error} |
X503090CLSJNP | 503 | joiner {node} raft port {raft_addr} unreachable from leader, join cannot converge until reachable |
X503091CCAJNW | 503 | joiner awaiting leader cluster CA {reason} {error} |
X503093CRTLUN | 503 | internal cert renew deferred, cluster leadership not yet confirmed on this node {op} |
X503200RFTTLW | 503 | raft tls enabled but cert material not yet on disk, starting raft in plaintext for this bring-up only, will pick up tls on next restart {error} |
X503218CLSSTH | 503 | store tier move of {node} to {role} held since {since}, {reason}, every later tier move waits until it ends |
X503284CLSPSR | 503 | peer status unavailable: {reason} |
X503425CLSDBU | 503 | drain of {node} was refused because the deploy.disruption of its deployments could not be read, {detail}, one of them may be never, nothing was changed, the node is still schedulable, retry once the store answers, or re-run with --force to accept the risk deliberately |
X503426JNRSTR | 503 | the enrol of {node} was cut by this node’s own restart, the join is tried again once the node is back |
X503427CLSDRZ | 503 | drain of {node} moved nothing because {freeze}, {node} is still {availability}, drain it again once the freeze lifts |
X503705CLSLGN | 503 | the logs of {node} were not read, the node was not reached {error} |
X504207CLSRBT | 504 | promote-before-departure timed out after {timeout} waiting for candidate {candidate} to rejoin raft as a voter, voter {node} was not removed, re-run the same command to resume once {candidate} is back |
X504216CLSSUT | 504 | suffrage {kind} of {node} timed out after {timeout} waiting for raft to list it with its new suffrage, the next pass retries |
clusterfs
Section titled “clusterfs”Source: modules/clusterfs
Count: 10
| Code | HTTP | Message template |
|---|---|---|
X200675CFSTIK | 200 | clusterfs on node {node} did not build, it keeps serving its current revision: {error} |
X200677CFSBLD | 200 | clusterfs build of revision {revision} on node {node} took {took} and {reads} store reads, outcome {outcome}: {sections} |
X409670CFSMOV | 409 | clusterfs build at revision {from} discarded, the control plane moved to {to} while it rendered |
X409681CFSWRS | 409 | clusterfs build discarded because the render wrote snapshot tables {tables} that its snapshot could not apply |
X500668CFSRAM | 500 | clusterfs cannot render its secret sections on {root}: {error} |
X500671CFSSEC | 500 | clusterfs section {section} failed to render, the node keeps its current revision: {error} |
X500672CFSWRT | 500 | clusterfs {op} failed: {error} |
X500674CFSREV | 500 | clusterfs revision counter {op} failed: {error} |
X500676CFSPKY | 500 | clusterfs build refused: {path} holds a PEM private key, and a private key is never published into clusterfs |
X503673CFSNOR | 503 | clusterfs at {root} holds no revision yet, the materialiser has not completed a build on this node |
Source: cmd/shc-scan, cmd/verify-image-pins
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X500606SCNHELP | 500 | scan helper failed {reason} |
X503675SCNDBR | 503 | scan database unavailable {reason}, run shc scan db update <archive> |
collector
Section titled “collector”Source: modules/collector
Count: 7
| Code | HTTP | Message template |
|---|---|---|
X500392COLEPH | 500 | export destination {endpoint} names no host |
X500393COLEPP | 500 | export destination {endpoint} names no port and no scheme that implies one |
X503120COLRCN | 503 | per-node collector reconcile failed at {step}, {reason}, retrying on the next sweep |
X503121COLEXG | 503 | collector export is disabled by the license.offline policy, {posture} |
X503122COLVMS | 503 | node metrics on this {node_os} node describe the container runtime’s linux vm, not the machine, cpu, memory, disk and network are the vm’s allocation, the series carry shc.host_metrics.subject=container-runtime-vm |
X503123COLREJ | 503 | the export destination refused {dropped} {signal} records from exporter {exporter} across {batches} batches this sweep. The destination said {reason}. Those records are lost and the collector counted them as sent, and nothing will retry them |
X503126COLBRG | 503 | the engine’s answer carries no network configuration, {answer} |
completion
Section titled “completion”Source: modules/completion
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400009INVSHL | 400 | unsupported shell {shell} |
X500700FILWRT | 500 | completion cannot write {path}, {err} |
condition
Section titled “condition”Source: modules/condition
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X200936CNDUNK | 200 | {unknown} could not be evaluated: {summary} |
X500936CNDOPF | 500 | condition {operation} failed |
X500937CNDOPN | 500 | {open} open at {worst}: {summary} |
config
Section titled “config”Source: modules/config
Count: 21
| Code | HTTP | Message template |
|---|---|---|
X200051CFGSEA | 200 | config key {key} moved into the vault, its row now holds a reference |
X400002VALINP | 400 | invalid input {detail} |
X400028CFGCON | 400 | --config-set key {key} is not a configuration path, and -c now means --config-set, where it meant --connection; to bind a connection use -C/--connection {key} |
X400033CFGUNK | 400 | config key {path} is not a known configuration key, possible typo, value stored anyway |
X400037CFGINR | 400 | config key {path} is stored but not in effect, {reason} |
X400041INVSCP | 400 | invalid scope {scope} |
X400043CFGUND | 400 | config key {path} is stored, but SHC cannot determine whether any component reads it |
X400050CFGSTP | 400 | config key {path} can only be set in yaml config files |
X400066CFGSCP | 400 | config key {path} is never read at {scope} scope, nothing would consult this row, set it at {readable} instead |
X400067CFGVAL | 400 | config key {path} is never acted on with value {value}, the row would store and read back while changing nothing, accepted values are {accepted} |
X400068CFGMIN | 400 | config key {path} is {value}, below {floor} at {floor_value}, {why}, so set it to at least {floor_value} or lower {floor} first |
X400155CFGNRD | 400 | nothing in this version of shc reads config key {path}, the {section} section has no reader for it |
X400831CFGOLD | 400 | config key {path} is gone, use {replacement} |
X400905SCPREQ | 400 | {field} is required |
X400949UNKSCP | 400 | unknown scope {scope} |
X409016CFGPLN | 409 | config key {key} holds a credential in plain config, it moves into the vault when the vault unlocks |
X409017CFGRSM | 409 | restored config keys {keys} refer to vault secrets this restore did not bring back, restore the backup’s secrets or set the keys again |
X409072CFGOWN | 409 | config key {path} is owned by {command} and is state, not config, so --config-set will not write it, {invariant} |
X409073CFGRTD | 409 | config key {path} is no longer configuration, {destination} |
X500952CFGOVL | 500 | config overlay {op} failed {error} |
X503018CFGVLT | 503 | config key {path} holds a credential and the vault that keeps it is locked, unlock the vault and set it again |
connections
Section titled “connections”Source: modules/connections/commands, modules/connections/providers/awsiam, modules/connections/providers/cloudflarer2, modules/connections/providers/dockerreg, modules/connections/providers/llmhold, modules/connections/providers/pfsenseapi, modules/connections/providers/s3hold, modules/connections/providers/s3scoped, modules/connections
Count: 77
| Code | HTTP | Message template |
|---|---|---|
X200464HLDUNSCOPED | 200 | s3 connection served its own unscoped credential to {tenant}/{app} at {endpoint}: no bucket scope was declared by the app or granted by the operator |
X200485CFRKEP | 200 | cloudflare r2 revoke retained {what}, {reason} |
X200488CFRUND | 200 | custom domain {domain} is attached to r2 bucket {bucket} but no grant declares it, left attached |
X200917CONRET | 200 | connection {connection} retire record failed, {error} |
X200920CONPRG | 200 | purged deferred credentials of {count} retired connections older than {ttl} |
X200944DNSZOWN | 200 | zone {zone} is already managed by connection {other}, connection {name} leaves it out of its listed zones |
X200945DNSZRFR | 200 | connection {name} zone list was not refreshed, {error}, its zones are kept as they were |
X400446AWSCRD | 400 | connection is missing the access_key or secret_key admin credential |
X400460HLDCRD | 400 | held s3 connection is missing its access_key or secret_key credential |
X400461HLDRCH | 400 | s3 connection endpoint {endpoint} unreachable or credential rejected: {error} |
X400462LLMCRD | 400 | held llm connection is missing its llm_endpoint or api_key credential |
X400463LLMRCH | 400 | llm connection endpoint {endpoint} unreachable or credential rejected: {error} |
X400464REGRCH | 400 | container registry {registry} unreachable or credential rejected: {error} |
X400465REGCRD | 400 | docker-registry connection is missing its username or password credential |
X400466HLDSCOPE | 400 | s3 {which} is not a valid scope document; it expects {“buckets”:[…]} or {“unscoped”:true} |
X400467PFSCRD | 400 | pfsense connection is missing its endpoint or api_key credential |
X400468PFSNFD | 400 | pfsense REST API v2 is not installed at {endpoint}, HTTP 404; pkg install pfSense-pkg-RESTAPI on the box, then reconnect. SHC does not mint a pfSense API key |
X400469PFSREJ | 400 | pfsense REST API v2 at {endpoint} rejected the API key with HTTP 401; the key must exist on the box and KeyAuth must be among its REST API authentication methods, SHC does not invent one |
X400470PFSRCH | 400 | pfsense REST API v2 at {endpoint} unreachable: {error} |
X400470SOSBUCKET | 400 | bucket name {bucket} is not a legal s3 bucket name and cannot be scoped |
X400473PFSTLS | 400 | pfsense connection cred {field} is not a usable TLS pin: {error} |
X400480CFRCRD | 400 | cloudflare connection is missing its token |
X400481CFRACC | 400 | cloudflare token resolves {count} accounts, connect with --cred account_id= |
X400483CFRZON | 400 | custom domain {domain} is under no zone this connection holds ({zones}) |
X400484CFRSCP | 400 | cloudflare r2 scope refused, {reason} |
X400486CFRNAM | 400 | derived bucket name {name} is not a valid r2 bucket name: 3 to 63 characters of a-z, 0-9 and - |
X400547CRDARG | 400 | --cred entry {position} {reason}; the forms are key=value, key=- and -, and a secret comes from the file --value-file names |
X400548CRDSEC | 400 | credential {field} {why} and is never taken on the command line: pass it as --cred {field}=- --value-file |
X400549CRDDUP | 400 | credential {field} is given more than once; give each field in exactly one --cred entry or document |
X400550CRDSRC | 400 | cannot read credentials from {source}: {reason} |
X400551ZNEOLD | 400 | {flag} is gone, write {now} |
X400552ZNEDUP | 400 | zone {zone} {reason}; name each zone once on --zone |
X400555ZNECON | 400 | connect cannot remove zone {zone} with a trailing !; use connection zones, or pass --zone ! with the whole declared set |
X400761CONENDPOINT | 400 | endpoint in credentials is refused, use --endpoint |
X400771DNSPURREQ | 400 | dns connection with --zone requires --purpose public|private |
X400901CONTYP | 400 | unknown connection type {type} |
X400904CONCRD | 400 | connection type {type} requires credential {field} |
X400906DNSZREQ | 400 | local DNS connection requires at least one --zone |
X400908DNSCRED | 400 | dns connection {type} credentials failed to validate |
X400912DNSPURP | 400 | dns connection purpose {purpose} is not public or private |
X400913DNSAZPUB | 400 | refusing to auto-create dns zone {zone} on connection {connection}, only a connection declared --purpose private may mint a zone |
X400914DNSOVP | 400 | dns connection type {type} answers only private clients on its overlay, purpose public refused, pass --purpose private |
X400916CONBND | 400 | grant boundary for connection {connection} is not valid json |
X400921CONMNT | 400 | connection {connection} failed to mint capability {capability} |
X400940DNSZARG | 400 | zones update for connection {name} needs --zone: zones to add, zone! to remove, or ’!’ beside the whole set, not both a set and a change and not neither |
X400941DNSZVIS | 400 | zone {zone} is not visible to connection {name}‘s credentials, nothing was changed |
X400942DNSNCP | 400 | connection {name} of type {type} has no dns provider, so it has no zones to update |
X400946CONLOC | 400 | connection type {type} has no load balancer, --location binds only a proxy connection’s edge{cred} |
X400947CONBKR | 400 | connection {connection} of type {type} cannot hold a backup repository, backup.repo names a connection of type s3 |
X400956CONLCP | 400 | --location {location} binds the edge to no node’s location: {why} |
X403465HLDNOSCOPE | 403 | s3 endpoint {endpoint} cannot mint a credential scoped to {buckets}: no scoped minter is registered for it; the scopable endpoints are {scopable}. Grant with --boundary ’{“unscoped”:true}’ to accept the held credential instead |
X403468HLDCAP | 403 | app declared s3 buckets {declared} but the grant boundary permits only {boundary}; the intersection is empty |
X403472PFSDNY | 403 | pfsense REST API v2 at {endpoint} refused this caller with HTTP 403: {reason} |
X403473BCKCAP | 403 | backblaze application key lacks {capability}, required to {op} |
X403488HLDPLUG | 403 | the app’s s3 plug addresses buckets {buckets} that the grant boundary does not permit; the boundary names {boundary} |
X403910CONGRT | 403 | connection {connection} not granted capability {capability} for tenant {tenant} |
X403922CONUNS | 403 | granting {capability} on connection {connection} serves the connection’s own unscoped credential; {remedy} |
X403925CONBKT | 403 | the s3 grant of tenant {tenant} on connection {connection} does not name bucket {bucket}, a backup repository there needs the bucket in the grant’s --boundary buckets list |
X404475BCKBKT | 404 | backblaze bucket {bucket} is not visible to the connection key |
X404902CONNOF | 404 | connection {name} not found |
X404911CONMCP | 404 | connection type {type} cannot mint capability {capability} |
X404915CONGNF | 404 | no grant for connection {connection} capability {capability} tenant {tenant} |
X409260CONSEL | 409 | connection name {name} is a selector at {scope} |
X409903CONUSE | 409 | connection {name} is in use by {where} |
X409907DNSZTIE | 409 | zone {zone} already managed by connection {other} |
X409914DNSZDROP | 409 | connection {name} owns zones {zones} that this connect leaves out; name them, or pass --zone ! to replace the whole set |
X409923CONMID | 409 | connection {connection} credential was minted as capability {minted_capability}, cannot reuse it for capability {capability}; unbind the plug and bind it again |
X409943DNSZRACE | 409 | connection {name} kept changing while its zones were being updated, nothing was written, run it again |
X500448AWSMNT | 500 | aws s3 mint {step} failed {error} |
X500449AWSIAM | 500 | aws iam mint {step} failed {error} |
X500467HLDMINT | 500 | s3 scoped minter {provider} failed: {reason} |
X500471SOSAPI | 500 | exoscale iam {op} failed: {reason} |
X500472SOSOPER | 500 | exoscale iam {op} operation ended in state {state} |
X500474BCKAPI | 500 | backblaze b2 {op} failed: {reason} |
X500482CFRAPI | 500 | cloudflare r2 mint {step} failed {error} |
X503905CONVLT | 503 | vault is not available, cannot store connection credentials |
X503918DNSCHK | 503 | dns connection {type} could not be checked against its provider, try again in {after}: {reason} |
console
Section titled “console”Source: modules/console
Count: 4
| Code | HTTP | Message template |
|---|---|---|
X403522CONROLE | 403 | the console is an operator surface and this identity holds no access to it, it needs tenant:read or higher in this realm |
X403523CONMANAGE | 403 | estate settings are a management surface and this identity holds no access to them, they need tenant:manage in this realm |
X404559CONAPI | 404 | {path} is not an API route on this daemon |
X503524CONAST | 503 | the console assets are not available on this node, the package resolved no shell document to serve, so the surface is momentarily absent rather than the request being wrong |
containerbroker
Section titled “containerbroker”Source: modules/containerbroker
Count: 19
| Code | HTTP | Message template |
|---|---|---|
X200990CBRWRM | 200 | container broker could not prepare image {image} on pool {pool}: {reason}; the pull succeeded but starts may be slower |
X200995CBRSWP | 200 | container broker could not remove everything it made for {caller} on this node{error}, the node tries again within a minute |
X400984CBRREQ | 400 | container broker run request is missing required field {field} |
X400991CBRVER | 400 | container broker answers Docker API versions {oldest} to {newest}, not {asked} |
X403984CBREEO | 403 | the job-container broker requires SHC EE with the container_runtime entitlement for tenant {tenant}; community edition runs per-job containers through shell executors only |
X403985CBROFF | 403 | the job-container broker is not enabled on this estate, opt in with shc config set container_broker.enabled true at global scope |
X403987CBRFLD | 403 | container broker refuses field {field} |
X403989CBRLIM | 403 | container broker refuses the container limit {limit} |
X403994CBRFIT | 403 | container broker refuses the container: node {node} has no room for its {resource} |
X403998CBRSLF | 403 | deployment {deployment} declares privileges.docker_socket: self, so its docker socket answers its own containers only, not {method} {path} |
X403999CBRREP | 403 | {container} is a service replica of deployment {deployment}: its docker socket lists, inspects, execs in, starts, stops and restarts it, and does not {verb} it |
X404987CBROBJ | 404 | container broker object {object} was not found |
X409993CBRSCK | 409 | container broker socket path {path} holds something that is not a socket, and it was left as it is |
X409996CBRNET | 409 | container broker deployment {deployment} has no network of its own on this node for the container to join |
X501992CBRNSV | 501 | container broker does not serve {method} {path} |
X503986CBRNYI | 503 | the job-container broker executor is not implemented in this build, the run was fully authorised but nothing can execute it yet |
X503988CBRENG | 503 | container broker cannot use the engine: {reason} |
X503989CBRNOD | 503 | container broker deployment has no replica here, holder nodes: {nodes} |
X503997CBRLAG | 503 | container broker ended the follow of {container}‘s log: its client is {reads} console reads behind, and every line is kept, so read the log again |
core/addrblock
Section titled “core/addrblock”Source: core/addrblock
Count: 8
| Code | HTTP | Message template |
|---|---|---|
X400349ADRBLK | 400 | address block {block} is unusable, {reason} |
X400450ADROVL | 400 | {overlaps} of address block {block}, {remedy} |
X409450ADROVL | 409 | node {node}: {overlaps} of this cluster’s address block {block}, move the node off that network or make the cluster again with {remedy} |
X409451ADRHLD | 409 | address block {block} overlaps {held}, a block this cluster already holds |
X409455ADRNOD | 409 | address block {block} is not added, on node {node} {overlaps} |
X409457ADRPOL | 409 | node {node}: {overlaps}, move the node off that network |
X500453ADRCRV | 500 | this node’s mesh address {address} is outside {mesh}, the mesh range this build carves from address block {block}: the cluster was formed under an earlier carve and cannot be upgraded in place, this start changed nothing on the node, form a new cluster with shc init to run this build |
X503456ADRASK | 503 | address block {block} is not added, node {node} could not be asked for its networks, {reason} |
core/api
Section titled “core/api”Source: core/api
Count: 16
| Code | HTTP | Message template |
|---|---|---|
X200067QRYTOK | 200 | query-string token used for auth on {path}, prefer the Authorization header |
X200288STRBOT | 200 | this node’s raft engine is not serving, so these rows are its own boot store as it stood when the node went onto raft and not the cluster’s |
X401000UNAUTH | 401 | internal api requires a cluster-ca client certificate or the internal token |
X403038LICLCK | 403 | estate changes are locked, {reason}, refusing {path}, running workloads keep serving and backups stay downloadable, run shc license status for what to do |
X404941APISCP | 404 | this peer is served one route on this listener, and {path} is not it |
X404942APIMTH | 404 | this daemon serves no method {method}, the methods it serves are listed in its OpenAPI document at {openapi} |
X409940APIGEN | 409 | this shc {cli_version} speaks API generation {cli_generation} and the daemon, shc {daemon_version}, speaks generation {daemon_generation}, so each would misread the other, refusing {path}, run shc {daemon_version} against this daemon |
X500040CMDFAL | 500 | command failed with exit {exit_code}, {command} {stderr} |
X500079FSMKDR | 500 | mkdir failed at {path}, {detail} |
X500083APILSN | 500 | listen {name} on {addr} failed, {error} |
X500084APIUDS | 500 | listen unix {path} failed, {error} |
X500085APICHM | 500 | chmod {path} failed, {error} |
X500086APIEXT | 500 | {name} listener exited {error} |
X503287STRHLD | 503 | this node’s raft engine is not serving and the daemon answers from its boot store, refusing {path}, a write here would never reach the cluster, {reason} |
X503906VLTLCK | 503 | vault is locked, refusing {path}, run shc vault unlock, or unattended shc vault unlock --password-file <path>, or --password-file - to read stdin |
X503907QRMLST | 503 | raft quorum unavailable, refusing {path}, retry once the cluster is healthy |
core/appcatalog
Section titled “core/appcatalog”Source: core/appcatalog
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X400761APPMAN | 400 | {path} is not an app; an app carries app.yaml |
core/appref
Section titled “core/appref”Source: core/appref
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X400076REPTWO | 400 | {ref} names repo {token_repo} but -r/--repo names repo {flag_repo}; drop one of the two |
core/collectorcfg
Section titled “core/collectorcfg”Source: core/collectorcfg
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500110COLCFG | 500 | collector config render failed {reason} |
core/composeunits
Section titled “core/composeunits”Source: core/composeunits
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X400228OVRVAL | 400 | {flag} is not {want}; nothing was written |
core/config
Section titled “core/config”Source: core/config/readerscan, core/config
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X200763ENVOLD | 200 | retired environment variables are set in shcd, {remedy} in its service unit or EnvironmentFile, or its launch environment, then restart the daemon |
X400035REFEMB | 400 | config key {key} contains an embedded secret-ref which is not resolved, only whole-value refs resolve |
X400763ENVOLD | 400 | retired environment variables are set, {remedy} |
core/containerendpoint
Section titled “core/containerendpoint”Source: core/containerendpoint
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X500087RTENDP | 500 | no {engine} api endpoint found, probed {probed} |
X500088RTENGB | 500 | container engine binary {binary} not found, searched {searched} |
core/daemonclient
Section titled “core/daemonclient”Source: core/daemonclient
Count: 8
| Code | HTTP | Message template |
|---|---|---|
X200962CLIOLD | 200 | this shc {cli_version} is older than the daemon it talks to, shc {daemon_version}, so a command or flag the daemon has may be missing here, install shc {release} or newer: https://selfhostedcloud.org/guide/getting-started/portal-cli/ |
X400963CTXYML | 400 | cannot parse {path} for the active cluster {cluster}, fix its YAML or run shc ctx --reset |
X403933DMNACC | 403 | permission denied opening the shc daemon socket |
X403963CTXREG | 403 | cannot read {path} for the active cluster {cluster}, make it readable by this user or run shc ctx --reset |
X500932DMNRPC | 500 | daemon client {op} failed |
X502932DMNRSP | 502 | daemon returned an error response {daemon_status} |
X503931DMNDWN | 503 | the shc daemon is not reachable {target_clause}{dial_clause}{next_step} |
X504934DMNNOAN | 504 | the shc daemon {target_clause} accepted the connection but did not answer{dial_clause} |
core/db
Section titled “core/db”Source: core/db/rqlitedriver, core/db
Count: 37
| Code | HTTP | Message template |
|---|---|---|
X409990MIGRST | 409 | this store’s ledger records {migrations} no catalogue in this build ships, {names}, so it was made before this release’s migration history was squashed; reinstall from this release, nothing migrates the store |
X409991MIGNEW | 409 | this store’s ledger records {migrations} newer than every file this build ships, {names}, so a newer build migrated it; run that build, or restore the control-plane snapshot taken before it |
X409992PRELIN | 409 | this node {formed} this build’s {line} reset line, {evidence}; {remedy} (https://selfhostedcloud.org/guide/operations/upgrades/#reset-lines) |
X500929DBSNAP | 500 | control-plane db snapshot failed {error} |
X500959MIGNVF | 500 | migration integrity verification disabled by escape hatch |
X500960DBOPEN | 500 | failed to open database handle {error} |
X500961DBPING | 500 | failed to ping database handle {error} |
X500963MIGRDF | 500 | failed to read migration {name} {error} |
X500964MIGTBL | 500 | failed to create migrations table {error} |
X500965MIGCHK | 500 | failed to check migration {name} {error} |
X500967MIGAPL | 500 | failed to apply migration {name} {error} |
X500968MIGREC | 500 | failed to record migration {name} {error} |
X500970MIGSCN | 500 | failed to scan migrations rowset {error} |
X500971MIGITR | 500 | failed to iterate migrations rowset {error} |
X500972MIGWLK | 500 | failed to walk migrations fs {error} |
X500974DBTIMS | 500 | db.Time cannot scan {type} into time |
X500975DBTIMP | 500 | db.Time cannot parse {value} with any known sqlite layout |
X500981DBMAIN | 500 | db maintenance pool not initialised |
X500982DBANLZ | 500 | db ANALYZE failed {error} |
X500983DBVACM | 500 | db VACUUM failed {error} |
X500984MIGSNS | 500 | migration {name} not listed in atlas.sum |
X500985MIGLDG | 500 | applied migration {name} drifted, ledger checksum {want} but on-disk content is {got} |
X500986MIGSUM | 500 | migrations atlas.sum missing or invalid {error} |
X500987MIGSTL | 500 | atlas.sum entry {name} has no matching migration file |
X500988MIGSHA | 500 | migration {name} checksum mismatch, atlas.sum records {want} but file hashes to {got} |
X500991SCHCOL | 500 | table {table} is missing {missing} that the daemon SELECTs; live columns are {present}; a read path that names a column the schema lacks must fail at boot, not once per container |
X501004BATBGN | 501 | failed to begin atomic batch {error} |
X501005BATSTM | 501 | atomic batch statement {index} failed {error} |
X501006BATCMT | 501 | failed to commit atomic batch {error} |
X501007RQLNTX | 501 | rqlite engine has no interactive transactions, {op} refused, use db.Pool.Batch for multi-statement atomicity |
X501008RQLBAT | 501 | rqlite atomic batch request failed {error} |
X501019CFSSNX | 501 | table {table} is outside this build’s snapshot, it was excluded or created after the snapshot was taken |
X501023RQLNPM | 501 | rqlite named parameters unsupported in statement {statement} |
X501032RQLNAK | 501 | rqlite returned {returned} of {statements} statement results for {op} with error {error}, the outcome is unknown and the statements may not have committed |
X501042RQLSTL | 501 | local read refused by rqlite, {error} |
X501043RQLMAT | 501 | materializing the blob column {column} failed {error} |
X501047DBRSNP | 501 | the snapshot a clusterfs build reads the store through failed: {error} |
core/eegate
Section titled “core/eegate”Source: core/eegate
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X403026DMNEEO | 403 | {feature} requires the commercial shc daemon, the daemon at {endpoint} is the community daemon. Point at a commercial shc cluster or install the commercial shc package on that node |
core/eestub
Section titled “core/eestub”Source: core/eestub
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X403028CLIEEO | 403 | shc {command} requires SHC EE, this binary is the community edition |
core/enginemarker
Section titled “core/enginemarker”Source: core/enginemarker
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500020ENGMKR | 500 | engine marker read failed {reason} |
core/executor
Section titled “core/executor”Source: core/executor/apple, core/executor/incus, core/executor
Count: 86
| Code | HTTP | Message template |
|---|---|---|
X200018INCCRT | 200 | the node’s Incus now serves certificate {served}: the health watchers of {projects} started on {held} and were told to end, and start again on the one served |
X200107INCWTR | 200 | removed {count} health watcher trust entries whose watcher is gone: {entries} |
X200124INCHLP | 200 | {count} on this node bound an exec helper other than the one it ships ({helper}): {instances}; each binds the node’s helper when it restarts or is recreated |
X200162INCAVR | 200 | dropped auto volume {volume} of {project} on {member}: an up that died part way made it and no instance used it, so this up makes it again from the image |
X200165INCEXK | 200 | the exit of {entry} in {project} could not be kept on its instance, and a reboot would lose it: {reason} |
X200256INCDLK | 200 | removed incus-compose lock {lock} whose holder pid {pid} on this host is no longer running |
X200373INCIPL | 200 | Incus recorded member {member} as holding image {fingerprint} with no file there; deleted its records in {projects} and fetched it again |
X200380INCDNR | 200 | the {verb} for {project} found Incus’s setup of {network} failing on attempt {attempt} of {tries} ({why}); it runs again in {wait} |
X200382INCLKR | 200 | the {verb} for {project} found Incus’s global database locked on attempt {attempt} of {tries}: {answer}; it runs again in {wait} |
X200391INCTOK | 200 | cancelled {count} image download tokens incus-compose’s copies left running in {project} on member {member} |
X200399INCGAT | 200 | the member-local listing {path} waits for this member’s Incus to answer GET /1.0 before it is sent: {why} |
X200400INCUSE | 200 | the usage of {instance} is read through Incus, not on the host: {reason} |
X200658INCARM | 200 | the health watcher {watcher} of {entry} in {project} has run no check for {idle}, even once woken, and was told to end and start again |
X200714EXECAR | 200 | {service} of {project} keeps {path} on volume {volume} from now on, with what anonymous volume {source} held there |
X200799INCPPL | 200 | the incus runtime pulls the image of {entry} in {project} only when the node lacks it: pull_policy {policy} has no Incus equivalent and is dropped |
X200800INCANN | 200 | the incus runtime keeps the annotations of {entry} in {project} as user. config; {keys} name no key it can take there and are dropped |
X200801APLANN | 200 | the apple runtime keeps the annotations of {entry} in {project} as labels; {keys} name a label already written and are dropped |
X200802EXEPST | 200 | the pre_stop hook {hook} of {container} did not end cleanly, {reason}; the stop goes on |
X200803EXEHOK | 200 | the {runtime} runtime runs no {hook} hook, so SHC runs those of {services} in {project} itself |
X200806EXEPRC | 200 | SHC pulled {image} but could not record the pull, {reason}; the next up pulls it again |
X200810EXERTY | 200 | the pull for {subject} got a transient registry answer on attempt {attempt} of {tries}, pulling {where}: {answer}; it pulls again in {wait} |
X200815INCWAK | 200 | the health watcher of {entry} in {project} has run no check for {idle} and could not be woken: {reason} |
X200816INCWOK | 200 | the health watcher of {entry} in {project} had run no check for {idle}, past its {interval} interval, and was woken |
X200824EXERWT | 200 | the {runtime} runtime writes {key} of {service} in {project}; {did} |
X200846INCFIL | 200 | a files request to incus failed and is tried again in {delay}, try {try} of {tries}, {reason} |
X200847INCFOK | 200 | a files request to incus answered on try {tries} after it failed with {reason} |
X200872INCDNS | 200 | stopped dnsmasq {pid} on member {member}: it still served bridge {bridge}, which Incus no longer has, and held {addresses} |
X200872INCORB | 200 | removed orphan bridge {bridge} ({subnet}) on member {member}: Incus holds no network of that name |
X200898INCRMK | 200 | deleted Incus network {network} of {name} to make it again: it still read {status} after its create was run again {reruns} times, and no instance was on it |
X201032INCUPT | 201 | up of {project} took {took}: {phases} |
X201033INCDWN | 201 | down of {project} took {took}: {phases} |
X206714IMGLFT | 206 | the {runtime} image prune removed {removed} of {meant} images and left {left} |
X400770EXERUN | 400 | runtime {runtime} has no executor in this daemon |
X400772EXEENV | 400 | exec into {container} refused env entry {key}, {reason} |
X400773EXEARG | 400 | exec into {container} was handed no command |
X400774APLKEY | 400 | the apple runtime refuses {project}: {found} |
X400775APLCMP | 400 | the apple runtime cannot run {project}: {detail} |
X400776INCKEY | 400 | the incus runtime refuses {project}: {found} |
X400776INCMNT | 400 | the incus runtime refuses {entry} in {project}: volume target {target}, {reason} |
X400776INCUSR | 400 | the incus runtime refuses {entry} in {project}: user {user}, {reason} |
X400777INCCMP | 400 | the incus runtime cannot run {project}: {detail} |
X400778INCEXE | 400 | exec into {container} refused, {reason} |
X400781EXECRT | 400 | the engine refused to create a container of {project}: {refusal} |
X400783EXEIMG | 400 | {project} names the image {image}, which no registry can be asked for: {reason} |
X400786INCPID | 400 | the image of {entry} in {project} insists on being process 1, which the incus runtime gives to its own init; it runs only on docker or podman |
X400788APLPID | 400 | the image of {entry} in {project} insists on being process 1, which the apple runtime gives to the helper that records its exit; it runs only on docker or podman |
X400789EXEHST | 400 | the {runtime} runtime runs on {on} nodes, and this node runs {here} |
X400795INCIMG | 400 | the incus runtime cannot read the image {image} of {entry} in {project}: {reason} |
X400796EXELOG | 400 | the {runtime} runtime does not support logs {option} |
X400797EXEPDM | 400 | the podman runtime refuses {project}: {found} |
X400840INCSRC | 400 | the incus runtime cannot start {project}: a bind source is missing on this node, {missing} |
X400842INCPOL | 400 | the incus runtime cannot make the volumes of {project}: incus.volume_pool names pool {pool}, which this node’s Incus does not have |
X403782EXELGN | 403 | {registry} needs a login to pull {image}, and the pull for {project} as tenant {tenant} failed; an image only the node holds is named under localhost/, which no registry is asked for: {detail} |
X403786EXEFBD | 403 | {registry} forbids this node to pull {image}: it answered 403 Forbidden and asked for no login, so a login will not change it, and the pull for {project} as tenant {tenant} failed: {detail} |
X409715EXECNV | 409 | {project} is not started beside {service} on this node, which keeps {path} in anonymous volume {volume}; the replica moves to a named volume stop-first |
X409781INCPRT | 409 | the incus runtime cannot publish {port} for {entry} in {project}: {holder} |
X409834EXEENR | 409 | {service} of {project} is not started: the environment it was made with is gone from RAM and its document no longer holds it; the next up makes it again |
X409841INCPLC | 409 | the incus runtime on cluster member {member} is not given its instances: {unmet} |
X500256INCDLK | 500 | cannot remove incus-compose lock {lock} whose holder pid {pid} is no longer running, {reason}, so the next pull of it waits for incus-compose to take it over |
X500399INCNTF | 500 | {method} {path} refused: only a GET listing of /1.0/instances or /1.0/operations carries an Incus cluster User-Agent |
X500492INCERR | 500 | {entry} in {project} did not start: its instance {instance} still read {state} {window} after its start, and it recorded no exit |
X500771EXECMD | 500 | {verb} for {subject} failed, {detail} |
X500776INCLXC | 500 | lxc could not start {entry} in {project}: {reason} |
X500779INCENV | 500 | the incus runtime cannot stage the environment of {entry} in {project}: {reason} |
X500787INCSTS | 500 | the incus runtime cannot keep the exit status of {entry} in {project}: {reason} |
X500804EXEPOS | 500 | a post_start hook of {container} in {project} failed, {reason}; the container is stopped |
X500805EXEPRS | 500 | the pre_start hook {hook} of {service} in {project} exited {code}; {service} is stopped |
X500833EXEENS | 500 | the environment of {service} in {project} is not staged in RAM, {reason} |
X500872INCDNF | 500 | cannot stop dnsmasq {pid} on member {member}, which still serves bridge {bridge} that Incus no longer has and holds {addresses}: {reason} |
X500872INCORF | 500 | cannot remove orphan bridge {bridge} ({subnet}) on member {member}: {reason} |
X502811EXEPUL | 502 | the pull for {subject} failed {attempts} times on a transient registry answer, the last pulling {where}: {answer} |
X503107INCWTR | 503 | the health watcher trust pass failed {step}: {reason} |
X503373INCIPL | 503 | the incus runtime cannot put the image {image} ({fingerprint}) of {project} on member {member}: {reason} |
X503380INCDNB | 503 | the {verb} for {project} is refused: Incus could not set up {network} on any of {attempts} attempts ({why}) |
X503382INCLKD | 503 | the {verb} for {project} found Incus’s global database locked on all {attempts} attempts: {answer} |
X503391INCTOK | 503 | cannot cancel the image download tokens incus-compose’s copies left running in {project} on member {member}: {reason} |
X503399INCGAT | 503 | the member-local listing {path} was not sent: this member’s Incus has not answered GET /1.0 ({why}): {reason} |
X503400INCUSE | 503 | Incus could not tell the state of {instance}, which is asked again in {wait}: {reason} |
X503780INCRST | 503 | cannot start {container}, its environment is not staged on this node: {reason} |
X503784EXEASK | 503 | {registry} could not be asked whether {image} needs a login: {why}; nothing on this node shows that tenant {tenant} may pull it, and the pull for {project} as tenant {tenant} failed: {detail} |
X503789INCREG | 503 | the incus runtime cannot pull the images of {project} from {registry}: {reason} |
X503843INCPOL | 503 | the incus runtime cannot place the volumes of {project} in pool {pool}: {cause} |
X504099INCDLN | 504 | incus-compose {verb} for {project} did not finish within {bound} and was stopped |
X504304INCIMW | 504 | incus-compose {verb} for {project} did not finish within {bound} and was stopped: it waited on image {image}, which Incus operation {operation} holds |
X504794INCHLT | 504 | {entry} in {project} did not read healthy within its healthcheck’s window of {window}: {reason} |
X504809EXESTL | 504 | the pull for {subject} stalled {tries} times, its processes read and wrote nothing for {window} {where} |
core/fwdhook
Section titled “core/fwdhook”Source: core/fwdhook
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500396FWHDRP | 500 | this node’s forward hook may drop traffic between containers on one bridge, {culprits}, run shc doctor for the full probe |
core/herd
Section titled “core/herd”Source: core/herd/herdhttp
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X429281APILIM | 429 | {provider} API account {account} is rate limited for {wait}, hold set by {header} |
core/hostactivate
Section titled “core/hostactivate”Source: core/hostactivate
Count: 14
| Code | HTTP | Message template |
|---|---|---|
X403027CLIPRV | 403 | shc {verb} must run as root, re-run as sudo shc {verb} or set SHC_STATE_HOME for a rootless dev sandbox |
X409131UNTAVL | 409 | the shc unit is running on an already-initialized node, so init will not replace its state directory; stop it with systemctl stop shc and re-run shc init |
X409135LNCAVL | 409 | the shcd launchd job is running on an already-initialized node, so init will not replace its state directory; stop it with sudo launchctl bootout system/org.selfhostedcloud.shcd and re-run shc init |
X500131STWRFL | 500 | the shc daemon cannot write its state directory {error}; stop it with systemctl stop shc and re-run shc init |
X500132UNTSTP | 500 | could not stop the shc unit before replacing its state directory {error}; stop it with systemctl stop shc and re-run shc init |
X500133UNTSTA | 500 | could not tell whether the shc unit is running {error}; refusing to replace its state directory |
X500134UNTSTR | 500 | could not start the shc unit again after init refused {error}; start it with systemctl start shc |
X500136LNCSTP | 500 | could not boot the shcd launchd job out before replacing its state directory {error}; boot it out with sudo launchctl bootout system/org.selfhostedcloud.shcd and re-run shc init |
X500137LNCSTR | 500 | could not start the shcd launchd job again after init refused {error}; start it with sudo launchctl bootstrap system /Library/LaunchDaemons/org.selfhostedcloud.shcd.plist |
X500687PODSCK | 500 | systemctl enable --now {unit} failed {error} {output}, shcd reaches podman only through that socket, so the service was not started, get {unit} running with systemctl, then run this command again |
X500978PODDRP | 500 | podman systemd drop-in setup failed at {step} {error} |
X501036SVCPLT | 501 | host service activation is not implemented for {platform}, start and enable the shc daemon with this host’s service manager |
X501037LNCJOB | 501 | launchd job setup failed at {step} {error} |
X503138DMNEXT | 503 | the shc daemon exited right after it was started, its last error line was {error}; see {log}; {node}, so fix the cause and start it with {start} |
core/hostplat
Section titled “core/hostplat”Source: core/hostplat
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X501391CLSPLT | 501 | cluster fabric {fabric} is not supported on {platform}, {reason}, use --fabric none for a single node |
X501392CLJPLT | 501 | joining a cluster is not supported on {platform}, a node needs a mesh0 device provided by kernel wireguard over netlink or the daemon’s userspace wireguard on a utun, use a host with the mesh capability |
X501395ROLCAP | 501 | {node} cannot take {role}, its host lacks the {capability} capability, {needs} |
core/incusapi
Section titled “core/incusapi”Source: core/incusapi
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400461INCAPI | 400 | {verb} on the incus runtime needs Incus listening on the network and core.https_address is unset; nothing was changed, run {command} and run {verb} again |
X503462INCSCK | 503 | {verb} on the incus runtime cannot read Incus on {socket}, nothing was changed: {cause} |
core/jinja
Section titled “core/jinja”Source: core/jinja
Count: 13
| Code | HTTP | Message template |
|---|---|---|
X400147JNJRET | 400 | template input {name} is gone, use {now} |
X400500JNJMAP | 400 | jinja path {path} traversal blocked, {key} is not a map |
X400501JNJKEY | 400 | jinja path {path} traversal blocked, key {key} missing |
X400502JNJLOAD | 400 | jinja template loading is disabled, refused {ref} |
X400503JNJBIG | 400 | jinja render exceeded the {limit} byte output cap |
X400504JNJTIME | 400 | jinja render exceeded the {limit} time budget |
X400505JNJPANIC | 400 | jinja render panicked: {detail} |
X400506JNJCAP | 400 | jinja strict-undefined inventory is partial, {dropped} of {examined} references were not examined |
X400507JNJPRS | 400 | jinja template {where} failed to parse: {detail}{hint} |
X400510JNJEMIT | 400 | jinja template {where} could not be attributed to its expressions: {reason} |
X400511JNJSHAPE | 400 | jinja template {where}: {culprit} changes the YAML structure the template defines, {fault}; a substituted value must stay inside the scalar it is written into |
X400512JNJMBR | 400 | members block at line {line}: {detail} |
X400513JNJREF | 400 | jinja template refused the render: {reason} |
core/labeltext
Section titled “core/labeltext”Source: core/labeltext
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400189LBLSYN | 400 | label {label} is not key=value or key!: {problem} |
X400190LBLDUP | 400 | label {key} is named twice, a node carries one value of an operator key |
core/log
Section titled “core/log”Source: core/log
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X503118LOGCAP | 503 | log export suppressed {suppressed} records in the last {window_seconds}s to stay inside its throughput ceiling, top codes: {top_codes}, full records are in the local log |
core/nic
Section titled “core/nic”Source: core/nic
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400992NICNOF | 400 | interface {name} not found or has no IPv4 address |
X500930NICDET | 500 | network interface detection failed {reason} |
core/nodefact
Section titled “core/nodefact”Source: core/nodefact
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400252CLDGON | 400 | --provider is gone, write --cloud {value} |
X400299FNCJON | 400 | --fence is gone, write --label key=value or --control-plane |
core/objchange
Section titled “core/objchange”Source: core/objchange
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X500171OBJUNK | 500 | object change {code} for {kind} {op} is not registered, nothing was recorded |
X503170OBJAUD | 503 | audit entry for {kind} {name} was not written, code {code}, {error} |
core/openstack
Section titled “core/openstack”Source: core/openstack
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400335OSKCFG | 400 | openstack auth config invalid, {reason} |
X404325OSKEPT | 404 | openstack service {service} endpoint not found in catalog for region {region} interface {interface} |
X502335OSKAPI | 502 | openstack api call {op} failed http {status} {detail} {error} |
core/otelboot
Section titled “core/otelboot”Source: core/otelboot
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X403128OTLORG | 403 | export refused, the request is not for the managed openobserve origin this exporter was built for |
X503127OTLHLD | 503 | export held, this node has no credential for the managed openobserve yet, its vault is locked or holds none |
core/pagecache
Section titled “core/pagecache”Source: core/pagecache
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500130PGCHLD | 500 | {held} bytes of {file} are still in the page cache after {passes} passes over {took} |
core/replicalabel
Section titled “core/replicalabel”Source: core/replicalabel
Count: 4
| Code | HTTP | Message template |
|---|---|---|
X400243REPLNO | 400 | no replica matches {selector}: {replicas} |
X400255REPLNM | 400 | {name} names a replica, and --where names one too; pass one of them |
X409258REPLND | 409 | replicas matching {selector} are held on {nodes}; run this operation there |
X503259REPLRD | 503 | replica label reader is not wired |
core/rqlited
Section titled “core/rqlited”Source: core/rqlited
Count: 29
| Code | HTTP | Message template |
|---|---|---|
X409047RQDCLI | 409 | this node is a store client and runs no raft engine, so it cannot {op}, run it on a voter or a replica |
X501009RQDBIN | 501 | rqlited binary not found, install the shc package or set SHC_RQLITED_BIN |
X501010RQDSTR | 501 | rqlited exited during startup with code {code} {error} |
X501011RQDTMO | 501 | rqlited not ready within {timeout} |
X501012RQDCFG | 501 | rqlited manager misconfigured {reason} |
X501013RQDSPN | 501 | failed to spawn rqlited {error} |
X501014RQDBOO | 501 | rqlite /boot ingest of {path} failed {error} |
X501015RQDBKP | 501 | rqlite backup to {path} failed {error} |
X501016RQDLDR | 501 | rqlite leader/roster query failed {error} |
X501020RQDCRA | 501 | rqlited exited unexpectedly with code {code}, relaunching |
X501021RQDRLF | 501 | rqlited relaunch failed, retrying {error} |
X501022RQDRNR | 501 | relaunched rqlited not ready {error} |
X501024RQDPRB | 501 | rqlited readiness probe {url} returned HTTP {status} |
X501025RQDGET | 501 | rqlite api GET {url} returned HTTP {status} {body} |
X501026RQDMKR | 501 | engine flip marker {marker} not removed {error} |
X501027RQDPRA | 501 | rqlite promote retry abandoned, cluster has {nodes} members and the ingest window is gone, continuing as a member on {sqlite} |
X501028RQDDMF | 501 | cluster scaled back to one node, storage engine demoted to plain sqlite on {sqlite}, scheduling daemon restart to complete the flip |
X501029RQDPMF | 501 | storage engine promoted to rqlite for the joining node, marker {marker} written, scheduling daemon restart to complete the flip |
X501030RQDDGR | 501 | rqlite engine started degraded, rqlited not ready within startup budget, retrying bring-up in background {error} |
X501031RQDNRD | 501 | rqlite engine not ready, background bring-up in progress |
X501034RQDSLF | 501 | cluster join addresses named this node’s own raft address {addr}, dropping it, rqlited cannot join itself |
X501035RQDNOJ | 501 | no raft join address left for the joining node in {state}, re-run shc node join against the cluster leader |
X501038RQDGRC | 501 | the leader query got no answer from rqlited {error}, this node keeps the leadership its engine last confirmed for up to 5 s since that answer, grace {graces}, an unanswered query past that drops it |
X501039RQDNLD | 501 | local rqlited no longer leads |
X501040RQDLBF | 501 | local leader batch failed, {reason} |
X501041RQDBRF | 501 | rqlited binary not found, install the shc package or set SHC_RQLITED_BIN, refused {refused} |
X501044RQDCLD | 501 | store client started degraded, no member of its store list answered within {budget}, restarting once one does {error} |
X501045RQDCDR | 501 | store client could not remove the rqlite data {dir} it kept as a replica {error} |
X501046RQDCUP | 501 | replica did not catch up with the leader’s revision {want} within {timeout}, its copy reads {have}, serving anyway |
core/secretscratch
Section titled “core/secretscratch”Source: core/secretscratch
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500146SCRRAM | 500 | {subject} holds resolved secrets and was not written, because the secret scratch directory {dir} cannot take it: {reason} |
core/selector
Section titled “core/selector”Source: core/selector
Count: 11
| Code | HTTP | Message template |
|---|---|---|
X400240SELSYN | 400 | {selector} is not a selector: {problem} at byte {position} |
X400241SELRES | 400 | selector {selector} names {place}, which cannot be answered: {reason} |
X400242SELFLG | 400 | {flag} is gone, write {now} |
X400244SELCLN | 400 | {flag} entry {entry} reads as a label written with a colon; write {label} for a label term or <service>:<selector> for a service’s own rule |
X400245SELEMP | 400 | {flag} entry {entry} needs a selector after {service}:; write {service}! to drop it |
X400246SELONE | 400 | {flag} entry {entry} names more than one service; write one service per entry as <service>:<selector> |
X400247SELENT | 400 | {flag} entry {entry} has an invalid selector: {problem}; write <service>:<selector> with a valid selector |
X400248SELDUP | 400 | {flag} states the deployment-wide rule twice; join the selectors with & |
X400249SELCON | 400 | {flag} states different selectors for {service}; write one selector for that service or pod |
X400250SELSVC | 400 | {flag} entry {entry} is per-service placement; set per-service rules with shc install or shc update |
X400257SELNAM | 400 | {flag} names unknown service or group {service}; write one of the app’s services or groups: {services} |
core/svcexec
Section titled “core/svcexec”Source: core/svcexec
Count: 12
| Code | HTTP | Message template |
|---|---|---|
X201004SVCCPL | 201 | staged artifact directory {path} could not be removed from service {service} after the job ran, {detail}, operator data may remain inside the running container |
X501050SVCEXRT | 501 | cannot exec into service {service}, runtime {runtime} has no service-exec dialect |
X501052SVCJREQ | 501 | service-context job is missing required field {field} |
X501053SVCJCTX | 501 | job {job} declares context {context}, which cannot be dispatched |
X501054SVCJARG | 501 | service {service} was handed both a shell command and an argv, which are exclusive, author command: as a string for the shell form or as a list for the argv form |
X501055SVCJRUN | 501 | cannot run container job {job}, runtime {runtime} has no one-off container dialect |
X501056SVCCPY | 501 | service {service} of {deployment} carries artifact transfers, @output or @input, but no container backing it could be resolved on this node, and artifacts can only be copied through a container this node also execs, author the job as context: container so it creates its own container here with real bind mounts |
X501057SVCCPS | 501 | artifact transfer for service {service} failed, {detail} |
X501058SVCJVL | 501 | job {job} runs with context service against {service} and declares {volumes}, which cannot be mounted into an already-running container, since docker fixes a mount namespace at create time; author the job as context container so it creates its own container with real bind mounts |
X501059SVCENVF | 501 | the environment for service {service} could not be handed to its exec through an env file, {detail}, and it is never put on the argv instead |
X501060SVCNCT | 501 | service {service} of {deployment} has no container to exec into on this node{detail} |
X501061SVCCPR | 501 | service {service} of {deployment} carries artifact transfers, @output or @input, and runtime {runtime} cannot copy files into or out of a container, artifact-carrying jobs run only on docker or podman |
core/tenantscope
Section titled “core/tenantscope”Source: core/tenantscope
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X400976TNTNON | 400 | no tenant named, pass -t TENANT, or X-SHC-Tenant on the API |
core/timescale
Section titled “core/timescale”Source: core/timescale
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400109TMSCAL | 400 | a time scale of {factor} is a dev-only setting and this daemon is not in dev posture, a scaled clock expires real terms, grace periods and retention windows in minutes, unset SHC_TIME_SCALE or set it to 1 |
X400137TMSNUM | 400 | SHC_TIME_SCALE={value} is not a whole number of 1 or more, 1 is a real clock and 288 is 5 real minutes per simulated day, unset it or give it a whole number |
core/usagecharge
Section titled “core/usagecharge”Source: core/usagecharge
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500926USGCHG | 500 | usage charge matched no row for tenant {tenant} |
core/validation
Section titled “core/validation”Source: core/validation
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400764ENVPRD | 400 | environment {name} is gone, write prod |
X400982NAMINV | 400 | invalid {kind} name {name}, {reason} |
X500982VLDINT | 500 | validation internal error {error} |
core/volume
Section titled “core/volume”Source: core/volume
Count: 34
| Code | HTTP | Message template |
|---|---|---|
X400310VOLCOL | 400 | invalid mount spec {spec}, too many colon-separated fields |
X400311VOLAXS | 400 | invalid mount spec {spec}, malformed access field |
X400312VOLEXT | 400 | invalid mount spec {spec}, unexpected field {field} |
X400313VOLPRM | 400 | invalid mount spec {spec}, perm field {field} is not numeric |
X400314VOLFLD | 400 | invalid mount spec {spec}, too many trailing fields |
X400315VOLOWN | 400 | invalid mount spec {spec}, owner field mismatch uid {uid} gid {gid} |
X400316VOLEMP | 400 | apply prep called with empty source |
X400317VOLPMD | 400 | parse mode {mode} failed, {error} |
X400318VOLMOD | 400 | empty mode string |
X400319VOLUID | 400 | parse uid {uid} failed, {error} |
X400321VOLGID | 400 | parse gid {gid} failed, {error} |
X400328VOLACC | 400 | volume mount {mount} declares access {access}, which is not supported, use rwo, single-node read-write, or rox, read-only multi-attach |
X400337VOLDCL | 400 | x-shc-volumes {subject} {problem} |
X400338VOLSIZ | 400 | volume mount {mount} declares size {size}, which is not a capacity, use a form like 10Gi 512Mi 1T or a byte count |
X403322VOLSMT | 403 | absolute mount source {source} is not permitted for tenant {tenant} |
X403323VOLESC | 403 | mount source {source} escapes the deployment sandbox |
X403325VOLPMU | 403 | mount source {source} is not a platform mount, known: {known} |
X403326VOLPMW | 403 | platform mount {source} must be mounted read-only: append :ro |
X403327VOLTLSU | 403 | no certificate-delivery grant for mount source {source} |
X403328VOLPMS | 403 | platform mount {source} is reserved for the system tenant, refused for tenant {tenant} |
X403329VOLSGL | 403 | volume source {source} is not a usable converter reference, {name} must be a single directory name |
X403331VOLBRK | 403 | deployment {tenant}/{environment}/{stack}‘s docker socket cannot be brokered here |
X403334VOLNST | 403 | mount source {source} is not one directory name, a mount cannot sit inside another |
X403335VOLFRO | 403 | mount source {source} is not a single file of the app, mount it read-only, append :ro |
X409034VOLNMT | 409 | refusing volume prep, {path} is not a confirmed mountpoint, attach may have silently failed |
X409347VOLSCF | 409 | volume {source} already holds {entry}, which is not the image’s {kind}, the seed leaves it as it is |
X409348VOLSND | 409 | the image’s {path} is a {kind}, not a directory, so no volume can be seeded from it |
X500310VOLCMD | 500 | {op} {path} failed {error} |
X500311VOLOWR | 500 | resolve owner {owner} failed {error} |
X500312VOLUSR | 500 | user lookup {user} failed, {error} |
X500313VOLGRP | 500 | group lookup {group} failed, {error} |
X500314VOLMDR | 500 | resolve data mount failed, MountsDir not set |
X500316VOLMNT | 500 | mountpoint check for {path} failed, {error} |
X500317VOLSED | 500 | volume seed of {source} from image {image} failed, {error} |
Source: modules/ctx
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X404903CTXNAC | 404 | no active cluster, {detail} |
daemon
Section titled “daemon”Source: daemon/wiring, daemon
Count: 57
| Code | HTTP | Message template |
|---|---|---|
X200133SYSRBT | 200 | system routes value {variable} carries a backtick, which closes a traefik rule matcher, so the routes built from it were not rendered |
X200311VOLSWP | 200 | volume size sweep: {recorded} recorded, {unreadable} unreadable, {unsupported} on a provider that cannot report a size |
X403992MSHEEO | 403 | peer call to {host} {path} refused, this community edition daemon’s peer transport is self-only and cross-node operations, multi-node clustering, require SHC EE, upgrade to add the clustering capability |
X403993CLNEEO | 403 | clone/move to node {node} refused, relocating a deployment onto another node is an SHC EE capability, multi-node clustering; community edition restores only onto the node that runs the verb, upgrade to add cross-node clone and move |
X409129VOLRCL | 409 | rebind claim lost {when} relocation {error} |
X409554DRNFIL | 409 | {stack} was not moved off {node}, {reason} |
X409638CLNRLD | 409 | this node already holds {entry} in {stack}‘s deployment directory {dir}, and a relocation never writes over it; move the directory aside and move again |
X409670CLNPRS | 409 | relocating {stack} onto node {node} is refused before it starts there: mount {mounts} holds nothing on that node, neither a mount point nor any entry, and the deployment would start against an empty directory |
X409677CLNTHN | 409 | {stack} came up on node {node} without {missing} it had before, so the move or clone that carried it there is refused |
X500381CLNSHW | 500 | wrote {wrote} of the archive’s {size} bytes |
X500382DRNCMP | 500 | {verb} of {stack} on {node} failed {stderr} |
X500383DRNSTR | 500 | {deployment} did not start again {error} |
X500623CLNXFR | 500 | clone recover could not ship the deployment to target node {node}, {reason}, refusing to restore on the source node and report a move that did not happen |
X500635CLNRLC | 500 | move could not relocate {stack} onto node {node}, {reason}; it is restarted on the node it was on |
X500641CLNRLF | 500 | relocating {stack} onto node {node} failed and nothing of it runs there, {reason} |
X500912KCTRPL | 500 | keycloak trust pool unavailable {reason} |
X500913KCDIAL | 500 | keycloak backchannel refused dial to non-SHC_HOST address {addr} |
X500914KCNOSH | 500 | managed keycloak requires SHC_HOST but it is unset |
X500992DMLOCK | 500 | another shcd already holds the singleton lock {path}, refusing to start a second instance |
X500994DMCNFG | 500 | daemon config load failed {error} |
X500995DMDBOP | 500 | daemon db.Open failed {error} |
X500996DMRALC | 500 | daemon subsystems.RegisterAll failed {error} |
X500997DMRAPN | 500 | daemon panic during RegisterAll {detail} |
X500998DMWIRE | 500 | daemon lifecycle.Wire failed {error} |
X500999DMMKDR | 500 | daemon mkdir {path} failed {error} |
X501016DMBSTR | 501 | node_bootstrap.json at {path} cannot be read {error} |
X503054OTLINI | 503 | otel init failed, continuing without telemetry {error} |
X503055SUBSTP | 503 | subsystem stop returned error {error} |
X503056OTLSHD | 503 | otel shutdown error {error} |
X503057OTLEXP | 503 | otel export failing, telemetry is being dropped, {suppressed} further failures suppressed since the last report {error} |
X503059DNSCFG | 503 | dns service skipped, nil config |
X503060QTANPL | 503 | quota service skipped, nil db pool |
X503061RPONPL | 503 | repo service skipped, nil db pool |
X503062RETNPL | 503 | retention service skipped, nil db pool |
X503063SRCNPL | 503 | search service skipped, nil db pool |
X503064CLSNPL | 503 | cluster service wired without pool, node repo unavailable |
X503065CENRSK | 503 | cluster enroll handler skipped, cert provider or node repo unavailable |
X503066MSHNRG | 503 | mesh orchestrator skipped, node registry not wired |
X503067MSHNPC | 503 | mesh orchestrator skipped, peer client not wired |
X503068MSHCST | 503 | mesh orchestrator construct failed {error} |
X503069VLTAUS | 503 | vault audit writer skipped, audit service not wired |
X503070QTANPL | 503 | quota cron deps skipped, nil db pool |
X503071STKMVS | 503 | stack move translator skipped, runtime state nil |
X503073PEERHTT | 503 | internal-API peer call failed {host} {path} {op} {error} |
X503074PEERCRT | 503 | internal-API peer client cert load failed {op} {error} |
X503074SCLWIN | 503 | x-shc-scale window scaling service {service} failed {error} |
X503075STKCTL | 503 | backup stack-controller {op} failed for {project} {error} |
X503077CASRCR | 503 | ca-signer connection cred read hit a transient vault fault for tenant {tenant} connection {conn} field {field} {error} |
X503078LDRNDL | 503 | leader internal-address resolve could not list the node table, falling back to the raft-host heuristic {error} |
X503084OTLNOA | 503 | managed openobserve destination resolved with no auth header on this node, its telemetry is dropped until the vault unlocks here |
X503085SHFSMT | 503 | shared-fs rebind of mount {mount} approved from the {provider} link row on target node {node}, which recorded a proven client mount but is not re-probed at move time, confirm the share is still mounted there |
X503086VOLORF | 503 | volume {volume} mount {mount} provider {provider} is orphaned after move, cloud volume not deleted, verify and clean up with shc volume rm {volume} |
X503087RETNBK | 503 | retention cannot delete an archive: the backup service is not wired yet, row kept |
X503096REGRCR | 503 | registry connection cred read hit a transient vault fault for tenant {tenant} connection {conn} field {field} {error} |
X503097USRNPL | 503 | user service skipped, nil db pool |
X503098CATNPL | 503 | catalog service skipped, nil db pool |
X503129DRNNWR | 503 | {seam} not wired on this daemon |
deploymentspec
Section titled “deploymentspec”Source: modules/deploymentspec
Count: 11
| Code | HTTP | Message template |
|---|---|---|
X400546DSPRBA | 400 | {digest} names more than one kept spec of {deployment}: {matches} |
X400734DSPENC | 400 | the spec of {deployment} could not be encoded: {error} |
X404543DSPRBD | 404 | {deployment} keeps no spec {digest}, it keeps {kept} |
X404547DSPRBG | 404 | {deployment} keeps no earlier spec that finished its rollout and differs from the one it runs, so a bare --rollback has nowhere to go; name one with --rollback= |
X404733DSPNOF | 404 | {deployment} has no stored spec: nothing rendered it on this line |
X404735DSPPRV | 404 | {deployment} cannot put spec {digest} back: it is no longer stored |
X409544DSPRBC | 409 | {deployment} runs spec {digest} already |
X409545DSPRBU | 409 | {deployment} cannot roll back while spec {digest} is not committed, an operation is still changing it |
X500731DSPWRT | 500 | the spec of {deployment} could not be written: {error} |
X500732DSPRED | 500 | the spec of {deployment} could not be read: {error} |
X503730DSPSTO | 503 | deployment spec {op} has no store yet, the daemon has not opened the control plane |
depnet
Section titled “depnet”Source: modules/depnet
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X409786DNTCLS | 409 | network {network} of {deployment} is on {subnet} on another member, but node {node} holds {subnet} for network {held} of {holder}: one Incus bridge cannot carry both |
X500780DNTSTO | 500 | deployment network ledger {op} failed, {error} |
X503781DNTFUL | 503 | node {node} has no free /25 left in {range} for a deployment network, every one is in use or quarantined |
Source: modules/dns/dnsapi, modules/dns
Count: 73
| Code | HTTP | Message template |
|---|---|---|
X200145DNSRDY | 200 | dns host {host} was not answered by nameserver {nameserver} within {wait}, check the zone’s delegation and nameservers |
X200146DNSAUT | 200 | dns host {host} could not discover the nameservers of zone {zone}, check the zone’s delegation and outbound port 53 |
X200150DNSCMO | 200 | dns provider {endpoint} did not commit staged record writes, the writes stand and the commit is retried in {wait} {error} |
X200904DNSTDN | 200 | dns record write skipped for host {host}, cluster teardown release already ran |
X200905DNSRLZ | 200 | cluster teardown release reached zero dns zones, {hosts} intended hostnames were not released |
X200906DNSRLI | 200 | cluster teardown release still incomplete after {attempts} attempts, records may still be live |
X200907DNSRTU | 200 | dns delete for host {host} resolved through retired connection {connection}, its live connection is already gone |
X200918DNSRTS | 200 | retired dns connection source unreadable during release, {reason} |
X200919DNSRTP | 200 | retired dns connection {connection} credentials not purged after release, {reason} |
X200920DNSGTO | 200 | dns takeover of host {host} from {found_owner} at generation {found_generation} as {owner} at generation {generation} |
X200921DNSPRV | 200 | private dns record for host {host} skipped, no address is known for the {plane} plane served by connection {connection} |
X200922DNSAZF | 200 | private dns zone {zone} could not be registered on connection {connection} {error} |
X200923DNSAZA | 200 | private dns zone for host {host} not auto-created, connections {connections} are all eligible, declare the zone explicitly with connection connect --zone |
X200924DNSPOO | 200 | dns.private_records is false for host {host} but connection {connection} is the only plane publishing it, suppressing would leave the host unresolvable, publishing anyway |
X200925DNSPFL | 200 | private dns record for host {host} on connection {connection} failed, the public record published {error} |
X200926DNSAZW | 200 | private dns zone {zone} for host {host} not auto-created, no zone registrar is wired in this process |
X200927DNSAZN | 200 | auto-created private dns zone {zone} on connection {connection} for host {host} |
X200928DNSPSK | 200 | dns plane for host {host} on connection {connection} skipped, the connection has no working dns provider, the remaining planes still publish {error} |
X200929DNSWBD | 200 | dns write for {name} deferred, this sweep has spent its budget of {budget} record writes |
X200930DNSWBS | 200 | dns sweep wrote {written} records and deferred {deferred} under its write budget, the next pass continues |
X200937DNSWBX | 200 | dns sweep still defers {deferred} record writes after {passes} passes with no progress, replay stopped until the ingress changes or leadership moves |
X400032DNSZON | 400 | dns zone not found for domain {domain} |
X400034DNSTGT | 400 | cannot resolve target {target} to ip or hostname |
X400036DNSMAN | 400 | no dns provider manages zone for {hostname} |
X400110DNSZNC | 400 | zone_id must be set on record for create |
X400111DNSZNU | 400 | zone_id must be set on record for update |
X400112DNSZND | 400 | zone_id must be set on record for delete |
X400113DNSZNO | 400 | zone_id must be set on record for create_or_update |
X400114DNSSET | 400 | set_records requires at least one content, use delete to clear an rrset |
X400117DNSNBT | 400 | netbird zones hold only a, aaaa and cname records, {record_type} refused |
X400118DNSNBR | 400 | netbird record name {name} refused, _shc-owner and _acme-challenge labels are reserved in a netbird zone |
X400119DNSPFT | 400 | pfsense zones hold only a and aaaa records and ownership claims, {record_type} at {name} refused |
X400120DNSPFR | 400 | pfsense record name {name} refused, the _shc-owner label is reserved for ownership claims |
X400121DNSPPA | 400 | dns record for host {host} refused on public connection {connection}, {address} is a private address |
X400841DNSOLD | 400 | {field} is gone for {provider}, write {replacement} |
X400922DNSUNK | 400 | unknown dns provider {provider} |
X400926DNSREQ | 400 | {config_key} is required for {provider} dns provider |
X400987DNSMRC | 400 | dns socket cannot write record {name}: {reason} |
X403040DNSOWN | 403 | dns records for host {host} owned by {found_owner} not {owner} |
X403041DNSUNO | 403 | no ownership txt for host {host}, refusing to delete unowned records |
X403042DNSPRN | 403 | skipping prune of unowned {record_type} record {content} for host {host} |
X403043DNSRPP | 403 | skipping reap of pinned host {host} |
X403044DNSRPL | 403 | leaving predecessor-owned host {host} alone, ownership cannot be proven for {owner} |
X403046DNSTKO | 403 | taking over dns records for host {host} from predecessor {found_owner} as {owner} |
X403047DNSGEN | 403 | dns records for host {host} held by sibling generation {found_generation} ({found_owner}), this cluster is generation {generation} ({owner}), refusing cross-generation write, flip authority explicitly with POST /api/dns/takeover |
X403048DNSSBY | 403 | dns {operation} for host {host} refused, this estate is on standby and is not the dns authority for its names, set cluster.dns_authority=authoritative at handover |
X403049DNSPTO | 403 | dns {operation} for host {host} refused, records are held by predecessor {found_owner} and this estate is {owner}. A same-slug claim is not proof the other cluster is dead, authorise the seizure with shc config set cluster.dns_takeover allow --scope global or flip this one name with POST /api/dns/takeover |
X403050DNSIHT | 403 | taking over dns records for host {host} from {found_owner}, whose claim stands on the host itself, as {owner} |
X403986DNSGNT | 403 | tenant {tenant} is not granted dns provider {provider}; the master tenant grants it via shc config set dns.grants.{tenant}.{provider} true at global scope |
X404038DNSZNF | 404 | no dns zone manages host {host} |
X404039DNSREC | 404 | no dns record found for host {host} |
X404047DNSNFD | 404 | dns provider reports {detail} not found |
X404860DNSACH | 404 | no public dns connection with dns-01 credentials manages host {host} |
X404988DNSMZN | 404 | no dns connection owns a zone covering {host}; bind a dns-capable connection whose zone is a suffix of it |
X409861DNSACB | 409 | dns-01 challenge name {name} holds another value the provider cannot keep beside ours |
X409872DNSOWW | 409 | wildcard host {host} cannot hold an ownership claim, its claim name {claim} would carry the wildcard mid-name, a wildcard host is one leading * label over a domain of at least two labels |
X409873DNSOWC | 409 | ownership claim name {claim} for host {host} holds {found}, the claim must be a plain TXT at that name, remove it before shc manages the host |
X409966DNSWNS | 409 | wildcard host {host} cannot be published through dns provider {provider}, shc publishes wildcard records only through a provider whose zone answers from wildcards |
X409967DNSWAP | 409 | wildcard host {host} sits at the apex of zone {zone} and would answer for every unclaimed name in it, route a wildcard one label or more below the apex |
X409968DNSWAD | 409 | wildcard host {host} publishes only A and AAAA records, a CNAME wildcard would capture the dns-01 challenge lookups under it |
X502870DNSTYR | 502 | moving host {host} from {from_type} to {to_type} failed, the {from_type} record still answers {error} |
X502871DNSTYL | 502 | moving host {host} from {from_type} to {to_type} failed and the {from_type} record could not be restored, the host may answer neither {error} restore {restore_error} |
X503030DNSAPI | 503 | dns provider api error {detail} {error} |
X503031DNSCFG | 503 | no dns provider configured |
X503032DNSACT | 503 | dns provider async action {action_id} for {detail} still running after {budget}, the write is queued not lost, later zone writes and acme dns-01 challenges may be delayed behind it |
X503033DNSUPD | 503 | rfc2136 dynamic update failed {detail} {error} |
X503034DNSRPS | 503 | dns reap refused, no managed hostname source is wired |
X503035DNSRPK | 503 | dns reap refused, managed hostname read failed {error} |
X503036DNSRPZ | 503 | dns reap refused, managed hostname set is empty |
X503037DNSRPB | 503 | dns reap refused, {orphans} of {total} owned hosts would be deleted, pass force to override |
X503038DNSOID | 503 | dns owner id is not configured, set dns.owner_id before any dns write |
X503039DNSINV | 503 | dns inventory refused, deployment host read failed {error} |
X503045DNSCMG | 503 | dns provider {endpoint} has not committed staged record writes after {attempts} attempts, they go live with its next commit {error} |
docker
Section titled “docker”Source: modules/docker
Count: 15
| Code | HTTP | Message template |
|---|---|---|
X400060CTRINP | 400 | invalid docker request {reason} |
X400067CTRFSP | 400 | invalid container fs request {reason} |
X400311REGCRD | 400 | registry connection {connection} has no username, so it cannot authenticate any pull |
X404060CTRNOF | 404 | container {container} not found |
X404061CTRFSF | 404 | path {path} not found in container {container} |
X409310REGTIE | 409 | registry connections {first} and {second} both claim {server}; docker holds one credential per registry, so which one authenticates would be nondeterministic |
X500061DKRCFG | 500 | docker client configuration error {reason} |
X500062DKRCLL | 500 | docker {operation} failed {reason} |
X500063CMPFAL | 500 | docker compose {subcommand} exited {exit_code} {reason} |
X500064EXCFAL | 500 | docker exec on {container} failed {reason} |
X500065EVCNCT | 500 | docker events channel closed {reason} |
X500066EVCMAX | 500 | docker events {attempts} consecutive reconnect failures |
X500067CTRFSO | 500 | container fs {op} on {container} failed {reason} |
X500312REGBAS | 500 | docker registry config could not be parsed or rendered: {reason} |
X500313REGWRT | 500 | registry credential file {path} could not be written: {reason} |
doctor
Section titled “doctor”Source: modules/doctor
Count: 17
| Code | HTTP | Message template |
|---|---|---|
X200985DCRRTM | 200 | this node runs the {runtime} runtime and no docker, {check} skipped |
X400271HSTHDR | 400 | --host is gone, write {now} |
X400921DCRUNK | 400 | no diagnosis named {diagnosis} |
X400922DCRNDS | 400 | diagnosis {diagnosis} has no destructive fix, its class is {class}; use --fix |
X409717DCRRUN | 409 | doctor fix {operation} is running on node {node} since {since}, shc doctor follow {operation} waits for it |
X410565DCRGON | 410 | no node holds operation {operation} any more, its daemon restarted or it ended more than five minutes ago, shc doctor run shows what is left |
X500917DCROPF | 500 | doctor {operation} failed |
X500918DCRNWR | 500 | doctor diagnose dependency not wired {dep} |
X500923DCRNDY | 500 | rbac deny enforcement not verified: {reason} |
X500924DCRNRA | 500 | rbac app reachability not verified: {reason} |
X500926DCRCTL | 500 | container listing unavailable on this node, {check} skipped |
X503919DCRKCD | 503 | system keycloak not running, {check} skipped |
X503920DCRNAV | 503 | doctor fixes require a running daemon |
X503927DCRNPR | 503 | doctor origin-probe is not wired on this daemon |
X503928DCRKCR | 503 | keycloak could not be read, {check} not verified: {reason} |
X503929DCRNLC | 503 | no diagnosis named {diagnosis} here, and the daemon that holds the module checks is not reachable |
X504849DCRFOL | 504 | the fix goes on as operation {operation}, shc doctor follow {operation} waits for it again and shc operation ls lists it while it runs |
events
Section titled “events”Source: modules/events
Count: 11
| Code | HTTP | Message template |
|---|---|---|
X400046EVTTYP | 400 | event type {type} is none of {types} |
X500007EVTBUS | 500 | event bus not running, {reason} |
X500015EVTBCS | 500 | event broadcaster {stage} failed {error} |
X500016EVTHND | 500 | event handler panicked {reason} {error} |
X500017EVTPRN | 500 | event prune failed {op} {error} |
X500018EVTCAP | 500 | event row truncated by the containment cap, code {code}, {detail} |
X500019EVTSUP | 500 | suppressed {count} duplicate occurrences of {code}, coalesced by the events containment layer |
X500020EVTDROP | 500 | pending-broadcast backlog cap shed {dropped} non-audit rows to hold the cap of {cap} |
X500021EVTSHD | 500 | event bus shed {dropped} events and could not publish the report {error} |
X500023EVTTRM | 500 | {summary} and could not publish the report {error} |
X500026EVTTSK | 500 | event and its task rows not written together: {reason} |
export
Section titled “export”Source: modules/export
Count: 42
| Code | HTTP | Message template |
|---|---|---|
X400501EXPINV | 400 | invalid exporter configuration {detail} {error} |
X400503IMPREQ | 400 | missing required import parameter {param} |
X400504EXPREQ | 400 | missing required export parameter {param} |
X400505IMPJOB | 400 | import job {job_name} failed {error} |
X400507NOEJOB | 400 | exporter {exporter_name} has no exporter jobs defined |
X400508NOIJOB | 400 | exporter {exporter_name} has no importer jobs defined |
X400509ARERRO | 400 | ar archive error {op} {error} |
X400515WRPSPC | 400 | wrap spec malformed {spec} |
X400516EXPNDR | 400 | data dir {path} is not a directory |
X400516WRPNOF | 400 | wrap input not found {path} |
X400519EXPSVL | 400 | job {job_name} runs with context service against {service} and declares volume {volume}, which cannot be mounted into an already-running container, only @output and @input are honoured on a service job, copied in and out; author the job as context container if it needs a real mount |
X400521IMPMTY | 400 | import artifact {artifact_path} for exporter {exporter} carries an empty payload with no files, so there is nothing to import, an artifact produced before service-context jobs could move their output to the host will look exactly like this and must be re-exported |
X400522IMPDIR | 400 | import source {path} is outside the designated import directory {root}, place the file under that directory; absolute paths elsewhere, .. escapes and symlinks leaving it are refused |
X400528EXPUND | 400 | exporter {exporter} declares no {direction} parameter {param}, its {direction} parameters are {declared}, nothing was run |
X400529EXPTYP | 400 | exporter {exporter} declares {direction} parameter {param} as {type}, and {value} is not one, nothing was run |
X400544IMPVKY | 400 | import vault key {key} is not referenced by the deployment app vars |
X400545IMPVFL | 400 | import vault output for key {key} is missing, unreadable or not a regular file |
X400555IMPVEM | 400 | import vault output for key {key} is empty |
X400559IMPVSC | 400 | import vault key {key} resolves at {scope} scope in the deployment app vars; an import seals only deployment-scoped keys |
X404500EXPNFD | 404 | exporter {exporter_name} not found in stack {stack_name} |
X404523EXPREP | 404 | this node holds no replica of deployment {deployment}, so export job {job_name} has no project to run in |
X404540IMPNON | 404 | no .exp artifact found in {dir} that exporter {exporter} made of deployment {deployment}, so nothing was imported, name the artifact to import with --input or --wrap |
X409108EXPRNG | 409 | operation {operation} already holds this export scope, wait with shc operation follow {operation} before retrying |
X409524EXPENT | 409 | export job {job_name} cannot run as compose service {service} in replica project {project}, that name is one of the replica’s entries |
X409525EXPKEY | 409 | export job {job_name} names {kind} {key}, which no replica of deployment {deployment} on this node declares, so the job would create it under the replica project |
X409541IMPSTP | 409 | import into {deployment} refused before any job ran: it is stopped, and its {job} job talks to its services; start it first |
X409542IMPREF | 409 | import into {deployment} refused by its {job} job: {reason} |
X409543EXPNRN | 409 | {verb} of {deployment} cannot run on {node}: its directory holds only the deployment’s mounts, and no node holding a live render of it could be told apart; run it on the node that holds the render |
X500170EXPLNG | 500 | the {action} stopped on an internal fault {detail} |
X500511EXPRUN | 500 | export run failed {reason} {error} |
X500512IMPRUN | 500 | import run failed {reason} {error} |
X500513EXPNST | 500 | export service not wired |
X500514EXPSTR | 500 | export stream failed {reason} {error} |
X500515EXPCKM | 500 | data checksum mismatch got {got} want {want} |
X500517WRPSTG | 500 | wrap staging failed {reason} {error} |
X500518EXPLST | 500 | export list failed {dir} {error} |
X500520EXPMTY | 500 | export {exporter} produced no files in {output_dir}, so the artifact would carry an empty payload and nothing could ever be imported from it, the jobs ran but wrote nowhere the runner reads |
X500530IMPVIO | 500 | import vault seal failed during {operation} |
X500531IMPVRB | 500 | import vault seal failed and previous values could not all be restored |
X500532IMPVJB | 500 | import vault output job failed; its output is private |
X500533IMPVDR | 500 | import vault private directory could not be created |
X503526EXPREM | 503 | export job {job_name} in project {project} was interrupted, the replica it ran in was removed from this node, retry the job |
fabric
Section titled “fabric”Source: modules/fabric/engine, modules/fabric/policy, modules/fabric
Count: 54
| Code | HTTP | Message template |
|---|---|---|
X200357FABNKY | 200 | node {name} enrolled without a fabric public key, no fabric chunk allocated, re-enroll with a fabric-capable cli to repair |
X200361FABGLU | 200 | fabric host firewall glue not installed, cross-node container traffic may be dropped, {reason} |
X200370FABXNG | 200 | fabric bridge-crossing guard not in force, a pinned container can reach another tenant’s container on a different local bridge, {reason} |
X200376FABQRT | 200 | fabric pin {service} of {deployment} left out of the policy, {reason} |
X200377FABBNF | 200 | fabric bridge netfilter not in force, same-node traffic on one bridge bypasses the fabric policy, {reason} |
X200378FABSRT | 200 | fabric source-route rejection not in force, a source-routed packet is judged by its first hop and delivered to its next, {reason} |
X200379FABCLS | 200 | node {node} loaded the fail-closed fabric table, all flows within {cidr} are dropped until its policy can be applied |
X200384FABFLW | 200 | fabric flows not reconciled, a connection to a released address or across a withdrawn permission may linger, {reason} |
X200385FABBRQ | 200 | fabric bridge row {interface} for tenant {tenant} on node {node} left out of the policy, {reason} |
X200387FABREV | 200 | fabric pins of {deployment} released without moving the clusterfs revision, nodes learn of it at the next revision, {reason} |
X200389FABLFT | 200 | network {bridge} could not be created while the host held {interface} at {address} with no network behind it, a network setup that failed partway left it, it was removed and the network created again |
X200404FABRTQ | 200 | fabric routed row {interface} for tenant {tenant} on node {node} left out of the policy, {reason} |
X200405FABLOP | 200 | published loopback routing not converged, {reason} |
X200423FABCRV | 200 | fabric chunk {chunk} of node {node} changed without moving the clusterfs revision, the other nodes route it at their next sweep, {reason} |
X200555FABEND | 200 | {pass} flow pass on node {node} ended {proto} flow {src} -> {dst}, delivered to {backend}, answered to {client}, {reason} |
X200556FABIGU | 200 | the system ingress on node {node} stays off its ingress unit {unit}, {holder} holds the unit, shc doctor run -c fabric.ingress-unit --fix moves it |
X400351FABCID | 400 | fabric cidr {cidr} is unusable, {reason} |
X400355FABKEY | 400 | fabric wireguard key for {holder} is invalid, {reason} |
X400356FABMOD | 400 | unknown fabric {fabric}, must be one of shc|none |
X400364FABPOL | 400 | fabric policy input invalid, {reason} |
X400365FABTEN | 400 | fabric policy isolation boundary violation, {reason} |
X400371FABSWM | 400 | fabric swarm is not supported on the new line, use --fabric shc or none |
X400372FABXTN | 400 | cross-tenant connection refused, {consumer} in tenant {consumer_tenant} cannot be wired to {provider} in tenant {provider_tenant}, the fabric blocks every flow between tenants |
X400373FABNPL | 400 | fabric node-plane ruleset input invalid, {reason} |
X400383FABEXP | 400 | fabric explain request invalid, {reason} |
X400386FABENG | 400 | node {node} cannot carry the shc fabric, {reason}, so its containers would not reach another node, install Docker Engine {engine} and Compose {compose} or newer from Docker’s own package repository (https://docs.docker.com/engine/install/), a distribution’s docker.io can be older |
X400387FABNFT | 400 | node {node} cannot carry the shc fabric, {reason}, install the nftables package with apt-get install nftables or dnf install nftables |
X400388FABINI | 400 | node {node} cannot run deployments on podman, {reason}, install catatonit with apt-get install catatonit or dnf install catatonit |
X400389FABOFF | 400 | the shc fabric is the workload network on a node running {runtime}, so it has no --fabric none, leave --fabric unset or pass --fabric shc, a cluster is formed without the fabric only where the runtime cannot attach it ({reason}) |
X400390FABMTU | 400 | node {node} cannot carry shc0 and mesh0, its underlay link at {address} has MTU {mtu} and they need {needs}, their floor {floor} plus WireGuard’s {overhead}, raise the link’s MTU or name a link that carries it with --nic |
X400391FABPCY | 400 | node {node} needs python3’s PyYAML and python-dotenv to run podman-compose {compose}, install them with {command} |
X400395FABATT | 400 | the shc fabric cannot be set up on a node running {runtime}, {reason}, leave --fabric unset to form the cluster without it |
X400396FABPDC | 400 | node {node} cannot carry the shc fabric, {reason}, a distribution’s podman-compose can be older, install podman-compose {compose} with apt-get install -y python3-dotenv python3-yaml && curl -fsSL https://downloads.selfhostedcloud.org/shc/podman-compose/{compose}/podman_compose.py -o /usr/local/bin/podman-compose && chmod 0755 /usr/local/bin/podman-compose |
X400397FABPRC | 400 | node {node} cannot run deployments on podman, {reason}, so an update would replace containers it keeps and what they wrote outside a named volume, a distribution’s podman-compose can be older, install podman-compose {compose} with apt-get install -y python3-dotenv python3-yaml && curl -fsSL https://downloads.selfhostedcloud.org/shc/podman-compose/{compose}/podman_compose.py -o /usr/local/bin/podman-compose && chmod 0755 /usr/local/bin/podman-compose |
X400398FABAVK | 400 | node {node} cannot carry the shc fabric, {reason}, so its containers would be answered every tenant’s service names, remove the aardvark-dns package with apt-get remove aardvark-dns or dnf remove aardvark-dns, and stop the containers a running one serves, the node’s DNS answers its containers instead |
X409358FABNON | 409 | node {name} cannot join, the cluster fabric is none which allows a single node only, re-init with --fabric shc for multi-node |
X409374FABNGR | 409 | deployment {deployment} cannot render on node {node}, the node holds no fabric grant and the fabric never falls back to a shared network, wait for its allocation or re-enroll it |
X409375FABUNP | 409 | deployment {consumer} cannot reach {provider} service {service} on the fabric, that service holds no fabric pin, update {provider} first so it renders onto the fabric |
X409399FABPRU | 409 | the update of {project} on node {node} is refused, {reason}, so it would replace containers the update keeps and what they wrote outside a named volume. They keep running as they are. Install podman-compose {compose} with apt-get install -y python3-dotenv python3-yaml && curl -fsSL https://downloads.selfhostedcloud.org/shc/podman-compose/{compose}/podman_compose.py -o /usr/local/bin/podman-compose && chmod 0755 /usr/local/bin/podman-compose and update again |
X409401FABCLM | 409 | deployment {deployment} render stopped, a later render holds its fabric pins, this render writes no compose and runs none |
X409402FABADR | 409 | apple replica address refused, {reason} |
X409406FABDUP | 409 | node {node} cannot join, its shc0 public key is already live on node {holder} |
X500352FABREP | 500 | fabric allocation repository error {op}{error} |
X500353FABFUL | 500 | the fabric {ranges} has no free chunk left, a chunk a node gave back is reused an hour later once every live node has dropped it, shc cluster block add adds another block |
X500354FABDEV | 500 | fabric wireguard device {op} failed{error} |
X500359FABPIN | 500 | fabric service pin error {op}{error} |
X500360FABBRG | 500 | fabric network {name} could not be ensured{error} |
X500362FABPST | 500 | cluster fabric posture error {op}{error} |
X500366FABVFY | 500 | fabric policy ruleset failed self-verification, {reason} |
X500367FABPCY | 500 | fabric policy {op} failed{error} |
X500397FABPCI | 500 | podman-compose {compose} could not be installed at {path} on node {node}, {reason} |
X502393FABPCS | 502 | podman-compose {compose} fetched from {url} for node {node} has sha256 {got}, not the pinned {want}, so it is not installed |
X502395FABPCF | 502 | podman-compose {compose} for node {node} could not be fetched from {url}, {reason} |
X503382FABGUR | 503 | deployment {deployment} cannot render on node {node}, the node’s fabric grant could not be read, which does not mean it holds none, retry when the store answers{error} |
failover
Section titled “failover”Source: modules/failover
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X409138FOVNST | 409 | the dead-source move had not started |
X500388FOVSTP | 500 | failover could not {step}, {error} |
Source: modules/fence
Count: 52
| Code | HTTP | Message template |
|---|---|---|
X200184FNCKCK | 200 | the label reconcile a node change asked for failed{error}, the reconcile that runs every minute retries it |
X200195FNCOUT | 200 | replica {replica} of {deployment} is bound to {node}, which its {scope} rule {rule} removes |
X400159FNCSET | 400 | {flag} does not apply to label value {fence}, it applies to {applies} |
X400182FNCPOD | 400 | {deployment} cannot be placed as asked: {reason} |
X400186FNCSHR | 400 | {deployment} cannot be placed as asked: {services} share volume {volume} on a node’s own disk, so they run on one node, and --scale puts their replicas on label values {fences}, which have no node in common |
X400187FNCRTM | 400 | {deployment} cannot be placed: no node its rules leave can run {service}, {refusals}; a node of a runtime that can run it would take it, and so would an app without what the runtime refuses |
X400188LBLKEY | 400 | label {key} is SHC’s: it comes from {from}, so no operator sets it |
X400251FNCGON | 400 | shc fence {verb} is gone: {replacement} |
X400253CNSCOP | 400 | --scope {scope} is not a constraint scope, the scopes are cluster, tenant and deployment |
X400254CNSFIT | 400 | scope {scope} does not fit its target: {why} |
X400260SELNAM | 400 | selector name {name} must be 1 to 63 of a-z 0-9 . _ - starting with a letter or digit |
X400261SELSCP | 400 | selector scope {scope} {problem} |
X400265SELEMP | 400 | a node selector is empty |
X400266SELGRP | 400 | a node selector cannot use a grouped place |
X400267SELVIS | 400 | selector {name} names {place}, which is not visible here |
X400268SELCYC | 400 | selector {name} names itself |
X400269SELGON | 400 | shc selector {verb} is gone: {replacement} |
X400298FNCFIT | 400 | {deployment} cannot be placed: service {service} requests {request} {resource}, larger than every node; largest node capacity is {capacity} {resource}{quota}; nothing was written |
X403163RULGLB | 403 | a constraint at {scope} needs platform:manage; a tenant’s tenant:manage covers that tenant and its deployments |
X403197GRNOUT | 403 | label value {label} is reserved for {grant}, and tenant {tenant} is outside that grant: {rule} is refused |
X403261SELAUT | 403 | {what} needs platform:manage, a tenant selector needs tenant:manage in that tenant |
X404153FNCNOF | 404 | label value {fence} not found, shc label ls --all lists every label value |
X404154FNCNOD | 404 | node {node} not found, shc node ls lists the nodes |
X404161RULNOF | 404 | constraint {id} not found, shc constraint ls lists the constraints |
X404164FNCDEP | 404 | deployment {deployment} not found, name it as |
X404260SELNOF | 404 | selector {name} not found |
X409155FNCORG | 409 | label value {fence} is {origin}, {verb} applies to {applies} |
X409156FNCRUL | 409 | label value {fence} is named by constraints, remove them first: {rules} |
X409157FNCSTR | 409 | {verb} would strand running deployments outside their eligible set: {strands}, move or drain them first |
X409171FNCEMP | 409 | no node can take {deployment}: {steps} |
X409172FNCNOD | 409 | {node} is outside the nodes {deployment} may run on: {steps}; shc update --where relocates it, after showing the plan |
X409173FNCRCV | 409 | shc recover lands {deployment} on {node}, and its rules leave {node} out: {rules}; nothing was installed, replace them and run the recover again: {commands} |
X409174FNCARC | 409 | shc recover lands {deployment} on {node}, and the rule its archive carries, where {rule}, leaves {node} out; nothing was installed; nodes the rule keeps: {nodes} |
X409177FNCCPE | 409 | removing {nodes} would empty the control-plane label, add the nodes that take over first |
X409179PLCPND | 409 | {deployment} is pending, no node fits it now: {nodes}{quota}; nothing was installed, shc constraint explain shows each node{instead} |
X409180FNCMOV | 409 | {deployment} runs on {current}, and this request would put it on {node}; a rule change relocates a deployment: shc update --where |
X409183FNCNDY | 409 | no node can take {deployment} yet: where {fence} depends on derived labels not written yet, the reconciler was asked to write them now and also runs every minute; retry in a few seconds |
X409184FNCSEP | 409 | {deployment}: the cluster has fewer eligible nodes ({nodes}) than group {group} has members ({members}), and separate=“required” gives each member a node of its own; nothing was placed |
X409185FNCSHR | 409 | {deployment}: group {group} is separate=“required”, and its members {members} share {node}; nothing was changed, shc cluster rebalance --apply moves them apart and then this update can run |
X409192LBLMOV | 409 | the labels of {node} changed while this request ran, nothing was written; run it again |
X409199GRNOUT | 409 | label value {label} cannot be reserved for {grant} while deployments outside the grant name it, clear those constraints first: {outsiders} |
X409255CNEMPT | 409 | where {expr} at {scope} leaves no node{deployments}{hint} |
X409256CNSCHG | 409 | constraints changed while this was being set; run it again |
X409262SELLOC | 409 | selector name {name} is a location a node is in |
X409263SELSHD | 409 | selector {name} is already defined at {where} |
X409264SELCON | 409 | selector name {name} is a connection |
X409265SELCHG | 409 | node selectors changed while this one was being written; run it again |
X409269SELUSE | 409 | selector {name} is named by {users}, remove them first |
X500165FNCSTO | 500 | label index {op} failed {error} |
X503185FNCLDR | 503 | the label reconcile runs on the leader, and {reason}; the reconcile that runs every minute converges the label index |
X507294FNCROM | 507 | {deployment} refused before any image was pulled: no node it may land on has disk for the images it lacks; the most room is on {node}, {free} free and {reclaimable} in unused images it may remove, where its images on that node need {need} and {floor} is kept free, so {short} more must be freed there; nodes it fits on: {fits}; each node’s pool: {pools}; nothing was written |
X507318FNCDSK | 507 | {deployment} refused: no node it may land on has room under its disk mark; the most room is on {node}, where {disk} has {free} free of {total}, the deployment needs {need} more there and scheduler.disk_mark {mark} keeps {keep} free, so {short} more must be freed there; nodes it fits on: {fits}; each node’s pool: {pools}; nothing was written |
Source: modules/forms
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400213HUDFAB | 400 | interactive form cancelled |
X500214HUDFRN | 500 | interactive form failed, {error} |
forward
Section titled “forward”Source: modules/forward
Count: 9
| Code | HTTP | Message template |
|---|---|---|
X400084INVSRN | 400 | invalid service name {name} |
X400086EMTFWD | 400 | empty forward specification |
X400088FWDPRT | 400 | invalid port {port} |
X400089FWDPRR | 400 | invalid port {port}, must be 1-65535 |
X400090FWDFMT | 400 | invalid forward specification format {spec} |
X400091FWDINF | 400 | cannot infer port for service {service}, {detail} |
X400910FWDREQ | 400 | forward requires {reason} |
X400911FWDOLD | 400 | {spec} is the retired spelling, write {now} |
X500910FWDOPF | 500 | forward operation failed {reason} |
freeze
Section titled “freeze”Source: modules/freeze
Count: 5
| Code | HTTP | Message template |
|---|---|---|
X500792FRZSTO | 500 | the placement freeze state could not be {op}: {error} |
X503790FRZMOV | 503 | automatic moves are frozen since {since}: {reason} |
X503791FRZEXP | 503 | the leader acts on no lease expiry: {reason} |
X503793FRZRAT | 503 | no automatic move may start now: this minute’s automatic moves are spent; it is tried again on the next pass |
X503798FRZLDR | 503 | no automatic move may start on this node: only the leader holds the move budget, and this node does not lead; the leader it knows: {leader} |
health
Section titled “health”Source: modules/health/reconcile, modules/health
Count: 20
| Code | HTTP | Message template |
|---|---|---|
X200046NODCRW | 200 | node {node_id} certificate warning, {reason} |
X200506OTLPST | 200 | managed openobserve OTLP provider persisted to the boot config drop-in and global config, a daemon that configured no exporter at startup loads it at its next restart |
X200507OTLPDG | 200 | managed openobserve OTLP provider persisted to global config only, a restart will not attach the auth header, set otel.provider in config.yaml to enable authenticated ingest |
X200924RSTRMT | 200 | deployment {stack} is broken on node {node} but the self-healing pass runs on {local_node} and can only repair its own node, so nothing will repair it |
X200933SYSDWN | 200 | module {app} is {status} on node {node}, stack {stack}; the estate cannot fully authenticate, persist, route or observe until it is back, and it is first in the recovery order |
X400060HLTNDA | 400 | no dial address |
X409903PRTCNF | 409 | port {port}/{protocol} is already allocated to another deployment |
X409932CPSFOL | 409 | control-plane snapshot refused on {node}, {leader} leads the cluster and the snapshot is taken on the leader; run it on {leader} |
X500507OTLDIW | 500 | failed to write managed OTLP config drop-in {path} at {stage} {error} |
X500932CPSFAI | 500 | control-plane snapshot on {node} failed, {reason} |
X503014NODNAV | 503 | node {node_id} unavailable |
X503050HLTNID | 503 | node health probe identity mismatch, got {got_id}, want {want_id} |
X503058SNPCFG | 503 | control-plane snapshot in cluster mode with no cluster-dump port wired |
X503060HLTNCK | 503 | no health checker wired |
X503061NODNVS | 503 | node {node_id} still unavailable, {suppressed} checks suppressed over {unavailable_for} |
X503064DBVSKP | 503 | db vacuum skipped, {reason}, freed pages are never returned to the filesystem |
X503092NODCRT | 503 | node {node_id} certificate critical, {reason} |
X503119HLTCSK | 503 | health cron {cron} dropped a tick, the previous run has been in flight for {in_flight} and produced nothing this tick; hours here means the skip-if-running flag was never released and this cron has been inert since |
X503932CPSLDR | 503 | control-plane snapshot refused on {node}, {reason}; the snapshot is taken on the leader |
X503932CPSNWR | 503 | control-plane snapshot refused on {node}, no snapshot directory or database dump is wired on this node |
inspect
Section titled “inspect”Source: modules/inspect
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X400910INSREQ | 400 | inspect requires a stack name |
X500910INSDSP | 500 | inspect display failed {op}{error} |
internal_rpc
Section titled “internal_rpc”Source: modules/internal_rpc
Count: 35
| Code | HTTP | Message template |
|---|---|---|
X400186RPCFRM | 400 | malformed rpc frames {detail} |
X400977RPCJSN | 400 | malformed rpc request body {detail} |
X400978RPCFNM | 400 | missing rpc function name |
X400979RPCRDF | 400 | rpc body read failed {detail} |
X403192TRFPER | 403 | transfer {handle} was issued to another node |
X403193TRFMSH | 403 | the transfer route answers only on this node’s mesh address, not {local} |
X403227RPCJTR | 403 | join {function} answers only on the public listener, not on {transport} |
X403282RPCPCT | 403 | the peer status port answers only a caller with a verified cluster node certificate |
X403945RPCTRN | 403 | rpc {function} requires the internal mTLS listener, got transport {transport} |
X403946RPCCAP | 403 | rpc {function} requires capability {capability}, which this caller was not granted |
X404183RPCUNK | 404 | unknown rpc function {function} |
X404191TRFUNK | 404 | no transfer {handle} is staged on this node |
X404240RPCJNF | 404 | no join function {function} |
X404281RPCPNF | 404 | no peer status function {function} |
X410190TRFEXP | 410 | transfer {handle} has expired |
X410290RPCFLW | 410 | rpc {function} has no followed call {call} on this node: the node restarted since the call began, or its answer expired |
X413147RPCBND | 413 | rpc {function} carries at least {size} bytes of transfers, past the {bound} it may make this node pull; nothing was pulled |
X413188TRFSIZ | 413 | transfer payload grew past its declared {declared} bytes |
X413900RPCBIG | 413 | rpc body exceeds the {limit}-byte cap |
X416198TRFRNG | 416 | range {range} does not fit a {size}-byte transfer |
X429228RPCJRL | 429 | join requests from {source} are over the limit, try again in {wait} |
X429280RPCPRL | 429 | peer status requests from {source} are over the limit, try again in {wait} |
X500185RPCBLB | 500 | rpc {function} carries binary data but {detail} |
X500196TRFIOE | 500 | transfer {op} failed: {detail} |
X502184RPCENV | 502 | rpc {function} to {addr} returned an unreadable reply: {detail} |
X502194TRFSUM | 502 | transfer {handle} arrived with sha256 {got}, not the {want} its holder reported |
X502199TRFPUL | 502 | pulling transfer {handle} from {addr} failed: {detail} |
X503182RPCBSY | 503 | rpc busy: {peer} already has {in_flight} calls in flight on this node, retry after {retry_after_ms} ms |
X503189TRFBSY | 503 | transfer busy: the {class} queue {detail}, retry after {retry_after_ms} ms |
X503195TRFKEY | 503 | transfer data key unavailable: {detail} |
X503197TRFOFF | 503 | no transfer store is open in this process |
X503220RPCOPN | 503 | {what} to {addr} was not sent: the peer’s circuit is open after repeated failures, retry after {retry_after_ms} ms |
X503229RPCJSG | 503 | the answer to join {function} cannot be signed: {detail} |
X504292RPCFLL | 504 | rpc {function} on {addr} is followed for its answer, and the node did not answer for {budget}: {detail} |
X507187TRFQTA | 507 | transfer staging refused: {size} bytes would exceed {limit} ({detail}) |
Source: modules/job
Count: 26
| Code | HTTP | Message template |
|---|---|---|
X200005JOBFAL | 200 | job {job_name} failed during {phase} {error} |
X200074JOBTHR | 200 | registry pull rate limit for job {job_name}, retrying in {delay} |
X200557JOBSLO | 200 | job {job} has made no progress since {since}: its output {output} stays at {bytes} bytes and its network has not moved, it is stopped once that lasts {after} |
X400010INVJOB | 400 | invalid job definition with {detail} |
X400011JOBMNG | 400 | job {job_name} is a {source} job and cannot be run directly |
X400015JOBPRS | 400 | job template parse failed, {reason}{token} |
X400027JOBREQ | 400 | {field} field is required for {context} context |
X400028JOBSNS | 400 | job {job_name} declares sensitive_output and runs in {context} context, where its stdout is a container log; run it in service context |
X400029HKSENS | 400 | job {job} declares sensitive_output and runs as a hook or start job, whose output reaches the caller and the daemon log; run it on demand or on a schedule |
X400065JRNTSK | 400 | job run {job_run_id} has no task yet with status {status}, nothing to cancel |
X404001JOBNFD | 404 | job {job_name} not found in stack {stack_name} |
X404004JOBSTK | 404 | deployment {stack_name} is not on this node, job {job_name} cannot be loaded |
X404077JOBREP | 404 | this node holds no replica of deployment {deployment}, so job {job_name} has no project to run in |
X404904JRNFND | 404 | job run {job_run_id} not found |
X409066JRNTRM | 409 | job run {job_run_id} already {status}, nothing to cancel |
X409067JRNRUN | 409 | job run {job_run_id} is executing, cannot cancel |
X409068JRNCLM | 409 | job run {job_run_id} was claimed for execution before the cancel landed |
X409077JOBENT | 409 | job {job_name} cannot run as compose service {service} in replica project {project}, that name is one of the replica’s entries |
X499075JOBCAN | 499 | {command} was killed after {elapsed}s because the caller cancelled the run, not because the job’s timeout expired |
X500900JOBOPF | 500 | job {operation} failed{error} |
X500901JOBNET | 500 | job network inspect failed for {network}{error} |
X503078JOBREM | 503 | job {job_name} in project {project} was interrupted, the replica it ran in was removed from this node, retry the job |
X503919JOBSEL | 503 | job {job_name} declares sensitive_output and the vault on this node can’t seal its output; unlock the vault and run it again |
X504075JOBTMO | 504 | {command} exceeded the job’s {timeout}s timeout after {elapsed}s and was killed (SIGKILL); any output the job had not flushed is lost. If the job enforces its own deadline, its timeout: must be strictly larger or that diagnostic can never print |
X504319JOBUPT | 504 | job {job}‘s container on {runtime} did not come up within its {bound}s bring-up bound, which covers image placement, its project, create and start. It was given up after {elapsed}s, before its command’s timeout began: {error} |
X504556JOBSTL | 504 | job {job} made no progress for {after}: its output {output} stayed at {bytes} bytes and its network did not move since {since}, so it was stopped |
Source: modules/kv
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400400KVINPT | 400 | kv invalid input {reason} {error} |
X404400KVNOFD | 404 | kv entry {namespace}/{key} not found |
X500401KVOPFL | 500 | kv {operation} failed |
labelcheck
Section titled “labelcheck”Source: modules/labelcheck
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400452LBLCHK | 400 | service {service} live label {key} is refused: {reason} |
X400454ALSDCL | 400 | service selector {service_selector} is refused: {reason} |
X403453LBLNOD | 403 | live labels for node {node} are reported only by that node itself, the caller presented {caller} |
leader
Section titled “leader”Source: modules/leader
Count: 5
| Code | HTTP | Message template |
|---|---|---|
X200923LDRCBK | 200 | leader {callback} callback failed {error} |
X503017LDRNOB | 503 | no node-health observer is wired on this node |
X503019LDRNOL | 503 | node health is observed by the cluster leader only; this node is not currently the observing leader |
X503021LDRSTL | 503 | the node-health walk has no observation newer than {window} for {count} of {expected} known nodes: {nodes} |
X503044LDRNRG | 503 | the cluster registry lists no nodes for the node-health walk to observe |
license
Section titled “license”Source: modules/license
Count: 39
| Code | HTTP | Message template |
|---|---|---|
X200937LICCHP | 200 | could not publish the estate licence-challenge key, {reason}, automatic licence checks stay node-local until it lands |
X200938LICCHM | 200 | could not materialise the estate licence-challenge key, {reason}, this node loses its offline copy until the state dir is writable |
X200961LICGOK | 200 | join-time capacity gate enforced for node {node}, {nodes} nodes and {cores} cores measured against {caps} |
X200997LICDRP | 200 | the broker granted a licence this estate did not keep, the replicated row holds one that outranks it, so the grant was written and reverted in the same refresh, upstream entitlements will not take effect until the row is displaced with shc license delink then shc license install <file>, or a re-mint that outranks the held licence |
X200998LICOFF | 200 | no broker ask was made, network license checks are disabled by the license.offline policy, install a vendor-signed file with shc license install <file> |
X400152LICWKR | 400 | workshop licence request refused, {reason}, a lab’s licence is bound to one label under the lab domain suffix and lives no longer than the lab |
X400750LICFORM | 400 | {form} is gone, use {replacement} |
X400968LICMAL | 400 | license file malformed, {reason} |
X400969LICSIG | 400 | license signature is invalid, it is not signed by the vendor key this binary trusts |
X400970LICKEY | 400 | minting requires the vendor Ed25519 signing key via --key |
X400971LICNAF | 400 | license file not found at {path} |
X400972LICREQ | 400 | vendor record request rejected, {reason}, fix the invoice and re-sync, this request will never succeed as sent |
X400973LICCAP | 400 | purchased capacity {cores} cores exceeds the {ceiling}-core ceiling for tier {tier}. Quote this as Enterprise, or raise the broker’s ceiling |
X403029LICENT | 403 | {feature} is not included in this estate’s SHC license. Activate or renew a license that includes it, see shc license status |
X403030LICDOM | 403 | license is bound to domain {expected} but this estate serves {actual} |
X403031LICLIM | 403 | license limit reached for {feature}, this estate holds {count} of {limit}, existing resources keep working and creating more needs a higher-tier license, see shc license status |
X403032LICDNS | 403 | activation callback for {domain} failed the public-DNS leg, {reason} |
X403034LICNCE | 403 | activation callback for {domain} failed the challenge-nonce leg, {reason} |
X403035LICGRT | 403 | no license grant on record for domain {domain}. Complete a purchase for this domain, then re-run activation |
X403036LICOPT | 403 | {feature} is a paid SHC feature and the 30-day trial includes it, start it with shc license trial start, and existing workloads are never affected when a trial ends |
X403037LICOFF | 403 | {feature} is not covered by this estate’s license and network license checks are disabled by policy license.offline, obtain a new signed license file from the vendor and install it with shc license install |
X403039LICCAP | 403 | this estate is over its licensed capacity for {resource}, using {count} against a licensed {limit}, reduce below the limit to clear it immediately, or license the extra capacity |
X403040LICENC | 403 | cluster enrollment refused, missing or invalid enrollment code, POST /register requires the code the vendor issued as a bearer token |
X403041LICENR | 403 | cluster enrollment refused for {domain}, {reason} |
X403042LICZON | 403 | a licence record was found at {record} but does not apply to this estate, {reason}, check the _shc-license TXT value for this domain |
X403043LICUNB | 403 | the licence record at {record} carries an unbound licence. A licence that matches every domain is never honoured from DNS, because the record is public. Publish a licence minted for this domain, or install the unbound one with shc license install |
X403044LICCRT | 403 | a licence record for {domain} was found but this estate cannot prove it controls that domain, {reason}, a DNS-carried licence is honoured only while the estate holds a publicly-trusted certificate covering the licensed domain, which is what stops a public record licensing somebody else’s estate |
X403045LICPTL | 403 | portal request refused, missing or invalid portal credential, the portal’s routes require the broker’s LB_PORTAL_TOKEN as a bearer token |
X403048LICVND | 403 | vendor mint refused, missing or invalid vendor token, POST /mint is vendor-only and requires the broker’s LB_VENDOR_TOKEN as a bearer token |
X403150LICWKS | 403 | workshop request refused, missing or invalid workshop credential, POST /workshop requires the broker’s LB_WORKSHOP_TOKEN as a bearer token |
X409941LICSUP | 409 | the licence presented does not supersede {comparand} so nothing was changed, presented {presented}, held {held}, a licence is adopted only if it expires later, or on an identical term was issued later or grants strictly more. Re-mint at or past the held expiry, or release the estate first with shc license delink |
X500158LICWKA | 500 | workshop route not armed, {reason}, POST /workshop stays disabled until the broker’s workshop settings are corrected |
X500960LICSGN | 500 | license signing failed, {reason} |
X500961LICSTO | 500 | license store operation failed, {reason} |
X502960LICBRK | 502 | online license activation failed, {reason}, use the offline signed-file path for airgapped estates |
X502961LICMNT | 502 | license mint failed after a verified activation callback, {reason}, retry activation, and contact the vendor if it persists |
X502962LICRFR | 502 | license re-fetch from the broker failed, {reason}, entitlements continue resolving from the locally held file |
X502963LICREC | 502 | writing the purchased rights into Keygen failed, {reason}, this is a retry, not a decline, the purchase stands and the next sync attempt should land it |
X503964LICGSK | 503 | join-time capacity gate skipped for node {node}, the node registry read failed {reason}, so {limits} went unenforced for this join |
Source: modules/logs
Count: 8
| Code | HTTP | Message template |
|---|---|---|
X400133LOGRTM | 400 | logs runtime {runtime} is not supported |
X400940LOGREQ | 400 | logs requires a stack name: pass --stack, rely on ctx fallback, or use --all |
X400941LOGDUR | 400 | invalid since value {since} |
X400942LOGTAL | 400 | invalid tail value {tail} |
X403944LOGSCM | 403 | permission denied, missing stack {stack} read |
X404940LOGNOF | 404 | no log target for project {project} service {service} |
X500940LOGRUN | 500 | log retrieval failed {op}{error} |
X500941LOGSTM | 500 | log stream failed {op}{error} |
Source: modules/mcp
Count: 4
| Code | HTTP | Message template |
|---|---|---|
X400381MCPHDR | 400 | the mcp endpoint needs the token in the Authorization header, a query-string token cannot open a session |
X500379MCPCTX | 500 | mcp tool call carried no per-call auth context, so SHC refuses to execute without the calling principal |
X500380MCPPAN | 500 | mcp loopback dispatch panicked, {panic} |
X503378MCPNRT | 503 | mcp daemon api router not ready, {reason} |
Source: modules/mesh
Count: 50
| Code | HTTP | Message template |
|---|---|---|
X200591MSHRLY | 200 | mesh relay: {a} and {c} on {device} have no reachable relay, {reason} |
X400562MSHTRQ | 400 | mesh trial request refused, {reason} |
X400571MSHKEY | 400 | mesh0 key for {holder} is unusable, {reason} |
X400572MSHADR | 400 | mesh0 address {address} is unusable, {reason} |
X400582MSHSNP | 400 | the peer table snapshot is malformed, {reason} |
X400596MSHPNT | 400 | mesh punch instant {at} is outside the allowed window |
X400604MSHRLA | 400 | mesh relay: the call needs device mesh0 or shc0, two different ends a and c, a relay other than either end and a generation of 0 or more |
X400811MSHROT | 400 | key rotation is refused: {reason} |
X403563MSHTRC | 403 | mesh trial refused, the caller is not node {from} |
X403581MSHSIG | 403 | the signed peer table is refused, {reason} |
X403590MSHAUT | 403 | peer table request refused, {detail} |
X403592MSHRLC | 403 | mesh relay: {caller} may not set the relay of {a} and {c} on {device} |
X403594MSHPNC | 403 | mesh punch: caller or owner proof is invalid |
X403597MSHRCF | 403 | a restored peer table is previewed or confirmed only through a live mesh0 node of the leader’s table, the caller presented {caller}; run shc cluster confirm-restore on such a node or on the leader |
X403812MSHAUT | 403 | key rotation requires the caller’s node leaf identity |
X404576MSHNOP | 404 | node {node} has no mesh0 address recorded |
X404579MSHNCL | 404 | no operator client {client} is on mesh0 |
X409561MSHTRY | 409 | this node is busy with a trial on {device}, try again in a few seconds |
X409564MSHTRB | 409 | this node cannot take part in a trial on {device}, {reason} |
X409578MSHKND | 409 | mesh0 row {id} is a {have}, not a {want} |
X409580MSHSTL | 409 | the store does not hold what this node’s mesh0 was last built from, {reason}; mesh0 stays as it is |
X409583MSHGEN | 409 | the offered peer table is {offered}, this node holds {held} and keeps it |
X409584MSHEXP | 409 | the offered peer table, {pair}, expired at {not_after} |
X409585MSHFLT | 409 | two peer tables carry {pair} with different rows, held {held}, offered {offered}; this node keeps the one it holds |
X409587MSHUNR | 409 | this node cannot take up the peer table it has stored, {reason}; it takes no other table until that one reads again or is reset |
X409588MSHERA | 409 | the peer table’s era moved since the preview, it was {from} and is {held}, so nothing was written |
X409593MSHRLO | 409 | mesh relay: relay selection is off on {node} for {device} |
X409595MSHPNR | 409 | mesh punch refused: {reason} |
X409603MSHRLG | 409 | mesh relay: {a} and {c} on {device} already hold another decision at generation {generation} |
X409605MSHRLE | 409 | mesh relay: {node} reaches {a} or {c} on {device} through a relay itself, so it cannot relay them |
X409607MSHRLH | 409 | mesh relay: {node} holds another generation than {generation} for {a} and {c} on {device} |
X409810MSHBUS | 409 | a key rotation is already open for node {node} |
X409813MSHHOF | 409 | node {node} must hand raft leadership to another voter before rotating mesh0 |
X409815MSHLAG | 409 | no shc0 key rotation starts while a member is on a release that takes no part in one: {nodes} |
X500560MSHTRN | 500 | the trial rule on {device} could not be deleted, {reason} |
X500573MSHFUL | 500 | mesh0 pool {cidr} has no free address left and no block the cluster added has a free chunk, the address of a removed node is reused an hour later once every live node has dropped it, shc cluster block add adds a block |
X500574MSHREP | 500 | mesh0 peer repository error {op}{error} |
X500575MSHCAC | 500 | mesh0 local state error {op}{error} |
X500586MSHSGN | 500 | the peer table could not be signed, {op}{error} |
X500608MSHRLW | 500 | mesh relay: {node} cannot sign a decision for {a} and {c} on {device}, it is not their owner or its owner signer is not wired |
X503577MSHOFF | 503 | this node is not on mesh0, so it cannot admit a node to it; enrol against a Linux member whose mesh0 is up |
X503588MSHGWY | 503 | this gateway holds no operator client, the rules that keep a client to the public API listener did not converge{error} |
X503589MSHLDR | 503 | no leader can be reached to confirm the restored peer table, {reason} |
X503591MSHSRV | 503 | peer table unavailable, {detail} |
X503592MSHGET | 503 | peer table recovery failed, {detail} |
X503601MSHRLS | 503 | mesh relay: node {node} has no relay session |
X503602MSHRLD | 503 | mesh relay: {node} has no direct path to {a} and {c} on {device} |
X503606MSHRLP | 503 | mesh relay: {node} has no handshake source for {device} |
X503814MSHROT | 503 | key rotation is waiting: {reason} |
X504816MSHACK | 504 | key rotation did not switch: node {peer} has not installed the pending key |
metrics
Section titled “metrics”Source: modules/metrics
Count: 7
| Code | HTTP | Message template |
|---|---|---|
X404920METNOF | 404 | metrics no definition for {name}{want}{error} |
X500920METREG | 500 | metrics duplicate registration for {name} |
X500921METINI | 500 | metrics failed to create {kind} instrument {name} {error} |
X500922METCAR | 500 | metrics cardinality cap exceeded for {name}, {observed} > {cap} |
X500923METNEG | 500 | metrics withheld impossible gauge {name}={value} for node {node_id}: this quantity cannot be negative |
X500924METATT | 500 | metrics withheld node {node_id} commitment: {axis} {observed} is not the {expected} attributed to that node |
X503120METTSK | 503 | metrics tick {collector} dropped a tick, the previous one has been in flight for {in_flight} and no metrics were collected this tick; hours here means the tick never returned and every gauge is stale by that much |
network
Section titled “network”Source: modules/network
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X500900NOTWRD | 500 | network service is not wired with a database |
Source: modules/node/commands, modules/node
Count: 24
| Code | HTTP | Message template |
|---|---|---|
X400061NODHDA | 400 | node health dial address empty |
X400307NODPRN | 400 | usage shc node prune |
X400899NODARG | 400 | usage shc node {cmd} <{arg}> |
X400911NODNOA | 400 | node {name} has no address configured |
X400915NAMVAL | 400 | {field_name} validation failed {reason} {error} |
X400932NODTTL | 400 | invalid ttl {value} {error} |
X400933NODTTP | 400 | invalid ttl {value}, must be positive |
X400934NODPRGS | 400 | node leave --purge is self-only, run it on the node you want to wipe without a [node] argument |
X400935NODPRGF | 400 | node leave --purge permanently destroys all local SHC state and data, re-run with --force to confirm |
X403459NODIFU | 403 | the running operations answer on this node’s unix socket only |
X403936NODUNA | 403 | node {node} is removed only at the word of the leader or a live voter, the caller presented {caller} |
X403938NODPSU | 403 | the pre-stop hook answers on this node’s unix socket only |
X404003NODNOF | 404 | node {name} not found |
X500019NODINI | 500 | local node not initialized, {path} missing, run shc init or shc node join first |
X500899NODREPO | 500 | node repository error {op}{error} |
X500923HTTPST | 500 | http {status} {body} |
X500924UNMRSH | 500 | unmarshal response {error} |
X503072NODHPF | 503 | node {addr} health probe failed {error} |
X503073NODHCN | 503 | node health client not configured |
X503074NODMIPF | 503 | mesh ip pool {cidr} is full |
X503075NODMIPC | 503 | mesh ip allocation contended for node {name} |
X503934TKNDMN | 503 | cannot mint a join token, the shc daemon stayed unreachable for {waited}, a token minted without the daemon is never recorded in the enroll ledger and the worker join it is used for fails X400022INVTKN, start shcd, or wait for it to finish restarting, and retry |
X503937NODUNU | 503 | node {node} removal cannot check its caller, {reason} |
X503998CMDNYI | 503 | not yet wired in Go port {operation} |
nodeagent
Section titled “nodeagent”Source: modules/nodeagent
Count: 24
| Code | HTTP | Message template |
|---|---|---|
X200695NAGRST | 200 | the node agent restarted {container} of {project} by its restart policy {policy} |
X200711NAGROM | 200 | pass over {deployment} on node {node} waits for room: passes over {running} run |
X200773NAGTKN | 200 | the node agent could {what} after it failed {tries} since {since} |
X200774NAGTKG | 200 | the node agent no longer owes the takedown to {what}, which failed {tries} since {since}: the copy is gone or placed here again |
X200826NAGKEP | 200 | the node agent could not keep the completed services of this node on disk, {error}; after shcd restarts each runs once more |
X409689NAGSTP | 409 | {tenant}/{environment}/{stack} was stopped by its operator, so its containers are not started until it is started again |
X409696NAGNAS | 409 | {tenant}/{environment}/{stack} is not assigned to this node, so its containers are not started here |
X409699NAGLLS | 409 | a lease-loss stop of {tenant}/{environment}/{stack}‘s RWO volumes is running or has stopped its writers, so a writer is not started here until their attachment lease is renewed |
X409700NAGSPC | 409 | {replica} of {tenant}/{environment}/{stack} was rendered as {got} and the stored spec renders it as {want}, so this node does not start it |
X409708NAGREP | 409 | {replica} of {tenant}/{environment}/{stack} is not bound to this node, so it is not started here |
X409710NAGSPL | 409 | {tenant}/{environment}/{stack} runs replicas on other nodes too, so a start of its whole project is refused here: its compose file names entries this node does not run |
X409712NAGMOV | 409 | {container} of {project} was started, stopped or removed since this start of it was decided, or its operator stopped it, so it is not started |
X409796NAGHLD | 409 | a stopped backup of {tenant}/{environment}/{stack} holds its starts |
X500694NAGSTA | 500 | the node agent could not start containers of {project}: {error} |
X500766NAGPRJ | 500 | the node agent could not converge this node’s replica projects: {error}; it tries again on its next apply |
X500771NAGTKD | 500 | the node agent could not {what}: {error}; it has failed {tries} since {since} and the boot gate stays closed on it until it is quarantined |
X503693NAGGAT | 503 | the node agent’s boot gate is closed, it is waiting for {waiting} and starts nothing until then |
X503697NAGLSE | 503 | this node’s lease for this boot is not live, so a writer of {tenant}/{environment}/{stack} is not restarted here |
X503698NAGUNB | 503 | {tenant}/{environment}/{stack} is not bound to any node yet, so its containers are not started until the scheduler binds it |
X503709NAGSTU | 503 | the runtime’s record of whether {container} of {project} was stopped on request could not be read, so it is not started until it can |
X503765NAGWAI | 503 | the node agent left replicas of this node unstarted, each waiting: {waits}; it tries again on its next apply |
X503767NAGOWN | 503 | {joiner} of {project} joins the namespace of {owner}, which was not running before the start bound passed, so {joiner} was not started and the next apply tries again |
X503770NAGRET | 503 | the node agent could not return against the stored assignments: {error}, so the boot gate stays closed |
X503772NAGQRN | 503 | the node agent quarantined the takedown to {what} after it failed {tries} since {since}: {error}; the boot gate no longer waits for it, it is tried again every {retry}, and it is never deleted by other means: take it down by hand; shc doctor run names the step |
nodelease
Section titled “nodelease”Source: modules/nodelease
Count: 19
| Code | HTTP | Message template |
|---|---|---|
X200746NLSMIS | 200 | node {node} lease renewal was not acknowledged, retrying in {retry}: {error} |
X200747NLSPRS | 200 | node {node} could not record its pressure level {level}: {error} |
X200756NLSVLT | 200 | node {node} could not record that its vault is {state}: {error} |
X200844NLSMEM | 200 | node {node} could not record its measured memory: {error} |
X200852NLSPOL | 200 | node {node} could not record its pool’s free space: {error} |
X403758NLSIDN | 403 | node {node} lease is renewed only by that node itself, the caller presented {caller} |
X409743NLSEPC | 409 | node {node} has seen liveness epoch {seen}, newer than the answering leader’s {epoch} |
X409745NLSDEP | 409 | the liveness term moved past epoch {epoch}, this node no longer leads node liveness |
X500678NLSRED | 500 | node leases could not be read: {error} |
X500744NLSTRM | 500 | the liveness term could not be {op}: {error} |
X500755NLSEXP | 500 | the lease was renewed but its expiry could not be written to {path} for the single-writer watchdog, which acts on the last expiry it read: {error} |
X500757NLSVRD | 500 | node vault states could not be read: {error} |
X500845NLSMRD | 500 | node measured memory could not be read: {error} |
X500851NLSPRD | 500 | the nodes’ pools could not be read: {error} |
X503676NLSSTO | 503 | node lease {op} has no store yet, the daemon has not opened the control plane |
X503727NLSVRC | 503 | node {node} could not record that its vault is {state} before placement read it, so nothing was placed: {error} |
X503741NLSLDR | 503 | node {node} renewed its lease with a node that does not lead node liveness |
X503742NLSQRM | 503 | the liveness leader last proved its quorum {age} ago, so it acknowledges no renewal |
X503748NLSHLD | 503 | node {node} renewal is held, {why} |
notification
Section titled “notification”Source: modules/notification/channels, modules/notification
Count: 14
| Code | HTTP | Message template |
|---|---|---|
X400115NTFPTN | 400 | at least one pattern is required |
X400700NTFPTN | 400 | invalid pattern {pattern} {error} |
X400701NTFCFG | 400 | invalid notification rule {context} {error} |
X400703NTFCHC | 400 | notification channel field {field} is empty |
X400711NTFTMP | 400 | notification template is invalid {issue} {detail} |
X429707NTFTST | 429 | notification rule {rule} was tested less than {interval} ago, test it again in {retry} |
X500701NTFSND | 500 | notification send failed {label} {error} |
X500702NTFDRP | 500 | notification dropped for rule {rule}, dispatcher not running {events} |
X500704NTFTPL | 500 | notification template {stage} failed {error} |
X500705NTFHTP | 500 | notification webhook returned HTTP {status} |
X500706NTFSND | 500 | unknown notification send failure |
X503011QUEFUL | 503 | notification queue full, dropping rule {rule} {events} |
X503012NTFRSK | 503 | notification rule {rule} skipped at dispatch {reason} |
X503013NTFDSF | 503 | notification dispatch send for rule {rule} failed {error} |
otelrelay
Section titled “otelrelay”Source: modules/otelrelay
Count: 12
| Code | HTTP | Message template |
|---|---|---|
X400108OTRSIG | 400 | {signal} is not a signal the telemetry relay carries, which are metrics, traces and logs |
X400111OTRBDY | 400 | the relayed export has no usable body, {detail} |
X400113OTRORG | 400 | the telemetry relay sends only exports for its own origin, and {request} is not one |
X409115OTRMOV | 409 | {node} does not hold openobserve, {holder} does, and the sender reads the holder again |
X502109OTRFWD | 502 | the relayed {signal} export did not reach openobserve, {detail} |
X503107OTRNOH | 503 | no node holds {deployment}, so this node’s telemetry has nowhere to be relayed |
X503110OTRDST | 503 | this node holds openobserve but has no address for its replica, {detail} |
X503112OTRCRD | 503 | this node holds openobserve but its vault gives no openobserve credential yet, it is locked or the credential is not minted, so relayed exports wait |
X503114OTRNWR | 503 | the telemetry relay is not wired yet, the daemon has not opened its control plane |
X503118OTRDOR | 503 | the node collector’s relay door did not open on {addr}, {detail}, so this node’s container logs and host metrics reach no store |
X504116OTREXP | 504 | the relayed {signal} export waited five minutes without reaching openobserve and was dropped |
X507117OTRFUL | 507 | the telemetry relay queue was full, so its oldest {signal} export was dropped |
Source: modules/pods
Count: 50
| Code | HTTP | Message template |
|---|---|---|
X200729PODEHL | 200 | early probe of {entry} in {project} passed {after} after its start: what waits on it healthy goes now, before its runtime’s first probe at {due}, whose word stands from then |
X200729PODPAS | 200 | pass over {deployment} on node {node} took {took} for {replicas} replicas: {pulls} pulls in {pull_wall}, at most {pull_peak} at once; {admitted} admitted in {admit_time}; {starts} started in {start_wall}, at most {start_peak} at once |
X200749PODLFT | 200 | replica project {project} was taken down on this node, {why} |
X200760PODHCW | 200 | replica project {project}‘s healthcheck could not be read, the replicas that wait for it to be healthy wait {wait}: {error} |
X200769PODOFF | 200 | replica projects are off on node {node}: {why} |
X200772PODONN | 200 | node {node} runs every deployment as replica projects |
X200777PODBRK | 200 | deployment {deployment} cannot be projected, its previous projection is kept if present: {reason} |
X200778PODHLD | 200 | replica {replica} has no vault document, its containers and previous materialised state are kept |
X200779PODPKF | 200 | the app files of archive digest {digest} were not placed on this node: {why} |
X200793PODLKR | 200 | the pull of {project} at spec {spec} found Incus’s global database locked, so this node pulls it again on its next pass, retry {retry} of {retries}: {answer} |
X200797PODKEP | 200 | replica project {project} is kept running on this node, its replica is bound to node {node} where it reads {state}, not ready |
X400755PODRUN | 400 | replica projects cannot run on this node, {what} |
X400760PODSPC | 400 | replica project {project} is not started, this node cannot make what it names: {error} |
X400766PODRFS | 400 | replica {replica} of deployment {deployment} cannot start on node {node}, its runtime refuses it at every start: {refusal} |
X400775PODAMB | 400 | the argument {service} is ambiguous between service {service} and replica {ordinal} of service {member} |
X404757PODUNK | 404 | this node holds no replica project {project} |
X404762PODSVC | 404 | service {service} of deployment {deployment} is in no replica project on node {node}, so there is no pod to act on |
X404763PODNON | 404 | deployment {deployment} has no replica project on node {node}, so nothing was acted on |
X404781PODNSV | 404 | service {service} is in no replica project of deployment {deployment}, so there is no pod to act on. Services in its replica projects: {services} |
X409751PODREP | 409 | the replica project at {dir} is refused, {why} |
X409752PODDIG | 409 | replica project {project} is refused, its compose document is not the one its replica record’s digest {want} seals: {error} |
X409754PODVOL | 409 | replica project {project} is not started, its durable volume {volume} is missing on this node and only the replica’s first bind creates it |
X409758PODUNB | 409 | replica project {project} is not started, the assignment store does not bind it to node {node} |
X409761PODWHL | 409 | {op} of compose project {project} is refused, this node runs every deployment as replica projects and {project} is the one project of a whole deployment, which it never runs |
X409767PODDIR | 409 | {op} of deployment {deployment} is refused in this process: this node’s daemon runs every deployment as replica projects, and a process with no runner of its own would act on the deployment’s one compose project beside them. Start shcd and run the command through it |
X409773PODSTP | 409 | replica project {project} is stopped by the operator, shc start runs it again |
X409776PODNOD | 409 | replica project {project} is bound to node {bound}, not this node {node} |
X409778PODMOV | 409 | replica project {project} refuses volume {volume}: row moved marker {row} differs from volume moved label {label} |
X409780PODOLD | 409 | deployment {deployment} is refused: the volume {old} holds data and {volume}, where member 1 of the group {group} keeps it, is empty. Nothing was started. Back up the deployment with the version that wrote {old} and restore it with this one, or reinstall it. |
X409783PODCRS | 409 | replica {replica} of deployment {deployment} on node {node} failed {times} in {window} without reading ready once: {entry} exited {exit}{last} |
X409784PODEND | 409 | {entry} exited {exit}, and its restart policy no never starts it again |
X409785PODFIN | 409 | replica {replica} of deployment {deployment} failed on node {node} and nothing starts it again: {reason} |
X409792PODJNR | 409 | replica project {project} of deployment {deployment} waits for run {run} of start job {job}, and the store has held no row of that run for {waited}: no install or update runs it, so the replica never starts; shc update {stack} -t {tenant} -e {environment} runs the deployment’s start jobs again |
X500756PODSEC | 500 | the stored replica {replica} cannot be written to clusterfs, {why} |
X500759PODIOE | 500 | replica projects {op} failed: {error} |
X500765PODRAM | 500 | replica projects are not materialised at {dir}, nothing was written: {why} |
X500770PODRES | 500 | replica {replica} was not materialised, its entry was not resolved: {error} |
X500774PODWRT | 500 | replica {replica} was not materialised, {op} failed: {error} |
X501782PODFRZ | 501 | deployment {deployment} cannot be paused or thawed on node {node}: its runtime has no freeze |
X503750PODDIR | 503 | the node’s replica projects could not be read at {dir}, nothing was started or taken down: {error} |
X503753PODAFT | 503 | replica project {project} waits, {waits} |
X503764PODWAI | 503 | replica projects of deployment {deployment} on node {node} are not started yet, they wait: {waits} |
X503768PODPND | 503 | {op} of {target} waits: this node has not decided yet whether it runs every deployment as replica projects ({why}); retry once it has |
X503771PODCFS | 503 | replica {replica} of deployment {deployment} is not started on node {node}, the node’s clusterfs does not build and the replica never reaches it: {why} |
X503786PODSED | 503 | replica {replica} of deployment {deployment} is not started on node {node}, its volume cannot be seeded from its image: {seed} |
X503787PODPUL | 503 | replica {replica} of deployment {deployment} is not started on node {node}, the pull of its images failed there: {pull} |
X503790PODBSY | 503 | {op} gave up after waiting {waited} for this node’s replica runner, busy with {holder} |
X504720PODPNW | 504 | {op} of {target} waited {waited} for this node to decide whether it runs every deployment as replica projects, and it has not ({why}); nothing was changed |
X504798PODSET | 504 | deployment {deployment} did not read ready within its settle window of {window}, which starts once its images are pulled and again each time one of its replicas reaches the spec, starts or reads ready; it waits: {waits} |
X504799PODPLS | 504 | the images of deployment {deployment} are still being pulled and no pull of them ended in {stall}: {pulls} |
portal
Section titled “portal”Source: modules/portal
Count: 45
| Code | HTTP | Message template |
|---|---|---|
X400141PTLCOD | 400 | invalid portal registration code, {reason} |
X400142PTLURL | 400 | invalid portal.url {value}, it must be an absolute http or https url |
X400148PTLDOM | 400 | this estate has no domain, set it with shc config set license.domain <domain> or initialise the estate with shc init --ingress-host <domain> before registering with the portal |
X400477PRTRNG | 400 | invalid portal.federation {value}, it is federated, registrant or sealed |
X400478PRTREQ | 400 | the portal exchange is malformed, {reason}, nothing was executed |
X400488PRTCOD | 400 | the registration exchange was refused, {reason}, mint a fresh code in the portal because codes are single-use and short-lived by design |
X400497PRTGRT | 400 | invalid store grant {entry}, each entry is <tenant>/<environment> in lowercase and the master tenant is never a store target |
X401479PRTSIG | 401 | portal directive signature did not verify, {reason}, refusing to execute anything the vendor cannot be proven to have sent |
X401514PRTBRR | 401 | the portal userinfo relay takes one bearer token in the Authorization header and this request carried none it could use |
X401516PRTUIA | 401 | the portal did not accept this sign-in’s token, so start the sign-in again |
X403140PTLOFF | 403 | the portal registration agent is disabled, portal.enabled is off by default |
X403146PTLUDS | 403 | portal registration runs only over the daemon host’s own socket, run shc portal register as root on a node |
X403147PTLROO | 403 | run as root on the daemon host |
X403480PRTVRB | 403 | portal directive names kind {kind}, which this estate does not accept, v1 accepts {accepted} and nothing else, and widening that set is a deliberate release decision rather than a runtime one |
X403487PRTAUD | 403 | portal directive {dispatch} is addressed to cluster {addressed}, and this cluster is {actual}, so SHC refuses it |
X403491PRTUNR | 403 | portal directive {dispatch} matches no install request this estate minted, and portal.require_requested_installs is on, so SHC refuses a dispatch the cluster never asked for |
X403492PRTREQM | 403 | portal directive {dispatch} claims install request {request} but does not match it, {reason}, SHC refuses it |
X403494PRTEDG | 403 | {host} refused this server at its edge with http 403 before the portal saw the request, so the portal is out of reach from this server’s network, and on dev that means joining this server to the VPN |
X403496PRTGNT | 403 | store installs into {target} are not granted on this cluster, an operator allows them by adding that target to portal.store_grants |
X403510PRTLIM | 403 | {key} is set from the portal by the org that owns this cluster, an admin of that org changes it there and this cluster applies it within a minute |
X403515PRTSLD | 403 | portal.federation is sealed on this cluster, so the portal userinfo relay refuses every sign-in |
X403517PRTUID | 403 | the portal refused this person a sign-in here, only a registrant, owner or admin of the org that owns this cluster signs in |
X404484PRTNRG | 404 | this estate is not registered with a portal. Registration is optional in every tier, so run shc portal register <code> with a code from my.selfhostedcloud.org if you want the marketplace and support bundles |
X409481PRTDUP | 409 | portal directive {dispatch} has already been settled on this estate in state {state}. The recorded outcome is being re-reported and nothing was executed a second time |
X409483PRTREG | 409 | this estate is already registered with {portal} as cluster {cluster}. Deregister first with shc portal deregister if you mean to move it |
X409498PRTEXS | 409 | store install of {app} into {target} would replace the deployment {deployment} that already runs there, and a store install only creates |
X409507PRTSEQ | 409 | portal limits {dispatch} carry seq {seq}, and this estate already applied seq {applied}, so SHC keeps the newer caps and changes nothing |
X409511PRTLNK | 409 | store install for {email} needs exactly one enabled user of tenant {tenant} with that email verified and found {matches}, so nothing was installed, a tenant admin adds the user with shc user create <username> "<name>" {email} --tenant {tenant} or fixes the duplicate |
X409513PRTGON | 409 | installer {email}, subject {subject}, is no longer a user of tenant {tenant} with that email, so nobody was granted the deployment its held install made |
X409519PRTKCO | 409 | this cluster is registered with the portal, but its Keycloak was created before the portal sign-in relay and can’t resolve it, so the portal sign-in on master isn’t set up. Run shc update keycloak -t master, then shc config set portal.federation sealed and shc config set portal.federation {rung} |
X410482PRTEXP | 410 | portal directive {dispatch} is outside the window this estate will act on, {reason}, refusing rather than replaying, because it can no longer be proven this directive has not already run |
X410493PRTOPG | 410 | portal install {dispatch} lost operation {operation} before it reported an end, {finding} |
X500489PRTKEY | 500 | the estate’s portal agent key could not be {action}, {reason} |
X500540PRTFLT | 500 | portal directive {dispatch} failed on this estate and the portal was told only that it failed, {cause} |
X502143PTLHTT | 502 | portal request failed, the portal answered http {status}, {body} |
X502144PTLTRN | 502 | portal request failed in transport, {error} |
X502486PRTCHN | 502 | the portal channel round trip failed, {reason}, the estate is unaffected and the agent will retry with backoff |
X502518PRTUIF | 502 | the portal userinfo relay got no usable answer, {reason}, so this sign-in stops here |
X503145PTLNYI | 503 | the portal outbound channel is not wired in this build yet, {piece} |
X503149PTLINI | 503 | this node has no shc daemon yet, run shc init first, or shc node join <token> to join a cluster, then run this again |
X503476PRTKCD | 503 | the system Keycloak is not running, so the portal sign-in on master was not converged, it converges on the next registration or portal.federation change |
X503485PRTNRT | 503 | this binary carries no portal trust root, so a vendor directive cannot be verified and the channel refuses to run. The vendor root keys that ship in modules/portal/trust.go are missing from this build |
X503490PRTVLT | 503 | the portal agent key is held in the vault and the vault is not readable on this node, {reason}, the channel will not fall back to a weaker store and stays down until the vault is available |
X503499PRTDPL | 503 | could not read this estate’s deployments to confirm {target} gets a new install, {reason} |
X503512PRTUSR | 503 | could not read the users of tenant {tenant} from this estate’s user service, {reason} |
portforward
Section titled “portforward”Source: modules/portforward
Count: 7
| Code | HTTP | Message template |
|---|---|---|
X403924FWDTGT | 403 | port-forward target {service}:{port} is not a port stack {stack_name} publishes or exposes |
X403926FWDOWN | 403 | the container answering for {stack_name}/{service} is not owned by that deployment |
X403927FWDADR | 403 | the container answering for {stack_name}/{service} has no container network address to forward to |
X404921FWDCNT | 404 | port-forward target {container} not found or unreachable from host |
X429923FWDLIM | 429 | too many open port-forwards for {scope}, past the limit of {limit}; close one and retry |
X503922FWDSCT | 503 | socat is required to port-forward containers without a host-reachable address but is not installed, run apt-get install -y socat on this node |
X503929FWDENG | 503 | the container engine on this node could not list the containers of {stack_name}, {detail} |
privilege
Section titled “privilege”Source: modules/privilege
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X403983PRVGNT | 403 | tenant {tenant} is not granted the privileged capability class it requested, {request}; the master tenant grants it via shc config set privilege.grants.{tenant} true at global scope |
X403990HSTGNT | 403 | deployment {deployment} asks for {request}, a host-reaching feature of class {class}; the master tenant’s operator grants it with shc config set privilege.deployment_grants.{tenant}.{environment}.{name} {classes} at global scope |
Source: modules/proxy
Count: 15
| Code | HTTP | Message template |
|---|---|---|
X200940PRXNBK | 200 | no live backend nodes while {intents} deployments ride external load balancers, leaving every lb target set unchanged this tick |
X200979PRXDUP | 200 | shared-vip proxy connection {conn} port {port} claimed by both {first} and {second} in tenant {tenant}, first claim wins this sweep |
X200983PRXHOL | 200 | proxy forward {external}/{protocol} of {deployment} on tenant {tenant} connection {conn} is held at node port {node_port}: {reason}, it keeps {pool} and every other forward reconciles |
X200984PRXSTL | 200 | load balancer {conn} VIPs for {tenant}/{stack} served stale as {vips}, the leader cannot be asked: {error} |
X400972PRXUNK | 400 | unknown proxy implementation {impl} for tenant {tenant} |
X400973PRXCFG | 400 | proxy backend {impl} misconfigured, missing connection cred {field}, {remedy} |
X400974PRXLBZ | 400 | load balancer for connection {conn} is in network zone {lb_zone} but network {network} has subnets only in {net_zone}, a hetzner load balancer cannot attach across network zones, put the nodes and the network in one zone or add a subnet in {lb_zone} |
X400975PRXADR | 400 | connection {conn} does not hold address {address}, it holds {addresses} |
X400978PRXNET | 400 | network {network} of connection {conn} is of type {type}, a publish needs a bridge |
X400981PRXPPU | 400 | proxy.proxy_protocol_trusted_ips is set but proxy backend {impl} for tenant {tenant} connection {conn} cannot send the PROXY protocol header, refusing to reconcile, unset the config or move the port mappings to an aws connection |
X409976PRXHLD | 409 | address {address} of connection {conn} is held by {holder} |
X409977PRXFUL | 409 | all {count} addresses of connection {conn} are held |
X500970PRXRCN | 500 | failed to reconcile proxy for tenant {tenant} connection {conn} {op} {error} |
X503971PRXNWR | 503 | proxy backend not available for tenant {tenant} connection {conn} |
X503984PRXLDR | 503 | load balancer {conn} VIPs for {tenant}/{stack} not read from the leader, {reason}{error} |
Source: modules/purge
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400940DBPRGB | 400 | invalid --before value {value}, expected a relative interval like 30d or a date like 2026-08-01 |
X403940DBPRGA | 403 | purging audit records requires the explicit audit opt-in |
X500940DBPURG | 500 | control-plane purge failed {op} {error} |
Source: modules/quota
Count: 20
| Code | HTTP | Message template |
|---|---|---|
X400915QTAINP | 400 | invalid quota input {reason} {error} |
X403001CPUEXC | 403 | cpu quota of {scope} exceeded, requested {requested} millicores but only {available} of {limit} available |
X403002MEMEXC | 403 | memory quota of {scope} exceeded, requested {requested} bytes but only {available} of {limit} available |
X403003DSKEXC | 403 | disk quota of {scope} exceeded, using {used} bytes of {limit} bytes limit |
X403004DEPEXC | 403 | deployment quota of {scope} exceeded, {current} of {limit} deployments |
X403005ENVEXC | 403 | environment quota of {scope} exceeded, {current} of {limit} environments |
X403006APPEXC | 403 | app quota of {scope} exceeded, {current} of {limit} apps |
X403007VDPEXC | 403 | vdeployment quota of {scope} exceeded, {current} of {limit} vdeployments |
X403008DSKASK | 403 | disk quota of {scope} exceeded, {used} in use, {asked} asked, {limit} limit |
X403010NODCPU | 403 | node cpu capacity exceeded, requested {requested} millicores but node {node} has only {available} millicores free after committed reservations |
X403011NODMEM | 403 | node memory capacity exceeded, requested {requested} bytes but node {node} has only {available} bytes free after committed reservations |
X403013SWMREP | 403 | no single node can host one replica, requires {requested_cpu} millicores and {requested_memory} bytes but largest node has {max_cpu} millicores and {max_memory} bytes across {node_count} nodes |
X403508ESTAPP | 403 | app cap of {limit} reached, this cluster runs {used} apps and they keep running, the cap is set by {owner} and an admin of that org raises it in the portal |
X403509ESTSRV | 403 | server cap of {limit} reached, this cluster has {used} servers and they keep running, the cap is set by {owner} and an admin of that org raises it in the portal |
X404909USGNOF | 404 | usage record not found for scope {key} {value} |
X500909DSKSCA | 500 | disk usage scan failed with {error} |
X500913USGREC | 500 | usage reconciliation failed with {error} |
X500914USGOPF | 500 | usage {operation} failed |
X500936QTACMT | 500 | node commitment {operation} failed {error} |
X503096DSKNMS | 503 | disk usage of {scope} is unmeasured, no sweep has measured it |
rebalance
Section titled “rebalance”Source: modules/rebalance
Count: 1
| Code | HTTP | Message template |
|---|---|---|
X409214RBLSTL | 409 | the move of {deployment} from {from} to {to} was not made, the estate changed after the plan, {detail} |
replicadoc
Section titled “replicadoc”Source: modules/replicadoc
Count: 10
| Code | HTTP | Message template |
|---|---|---|
X400660RDCREF | 400 | replica document refused, {why} |
X400661RDCENT | 400 | replica document entry refused, {why} |
X400665RDCKEY | 400 | the vault key is not a document of replica {replica} |
X403663RDCASN | 403 | node {node} may not read replica {replica} |
X404662RDCMKY | 404 | replica {replica} cannot be checked, the cluster mac key is not in the vault |
X404669RDCNOF | 404 | replica {replica} has no document at the named version |
X409666RDCMAC | 409 | the document stored for replica {replica} does not match the digest in its entry |
X409667RDCCOL | 409 | replica {replica} already holds a different document at this version, it was not overwritten |
X500668RDCVLT | 500 | the vault could not {op} {what}: {code} |
X503664RDCASG | 503 | the assignment of replica {replica} could not be read: {error} |
Source: modules/repo
Count: 26
| Code | HTTP | Message template |
|---|---|---|
X200906REPHDM | 200 | repository {name} synced without {missed} of {total} head archives from {origins}; they kept their previous browse facts: {apps} |
X400013INVURL | 400 | invalid repository url |
X400702REPCFF | 400 | repository {name} cannot take its credential from {value} |
X400762REPIDX | 400 | repository index {reason}; publish a v2 index with api_version: v2 and a nonempty versions list per app, without parent_app or vapp |
X400927REPFIL | 400 | file-path repositories are no longer supported |
X400928REPRSV | 400 | repository name {name} is reserved |
X400943REPADP | 400 | unsupported adapter {adapter} |
X400944REPNDL | 400 | repository url {url} is node-local and this estate has {nodes} nodes |
X400946REPCST | 400 | adapter {adapter} has no public catalog to sync |
X400947REPAGT | 400 | adapter {adapter} catalogs sync only from a git repository, not {url} |
X400967REPSSR | 400 | repository url host {host} is not an allowed remote target |
X403901REPSYS | 403 | cannot delete the system repository |
X403902REPBLT | 403 | cannot remove the shipped repository |
X403907REPSYW | 403 | repository {name} belongs to the system scope and only a platform admin can change it |
X404901REPNOF | 404 | repository {name} not found |
X404917REPLGN | 404 | repository {name} reads the pull login of connection {connection} in tenant {tenant}, and there is none |
X409901REPOEX | 409 | repository {name} already exists |
X409918REPREV | 409 | repository {name} is at {have} on this node but its last sync read {want}, and syncing it here failed {error} |
X409987REPAMB | 409 | repository {name} exists in more than one scope ({scopes}); name one with ?tenant_name= and ?environment= |
X500902REPMAT | 500 | failed to materialize source for repository {name} {error} |
X500903REPSYN | 500 | failed to sync repository {name} with {reason} {error} |
X500904REPOPF | 500 | repository operation {operation} failed |
X500905REPGIT | 500 | git {args} failed {error} {output} |
X502908REPCRD | 502 | repository {name} needs a credential and its index answered HTTP {status} |
X502909REPDEN | 502 | repository {name} refused this cluster’s credential with HTTP {status} |
X503917REPVLT | 503 | vault refused the credential of repository {name} |
resolver
Section titled “resolver”Source: modules/resolver
Count: 5
| Code | HTTP | Message template |
|---|---|---|
X200279RSVRCV | 200 | the DNS listener on {addr} was granted {granted} bytes of the {requested} byte receive buffer it asked for; the kernel will drop a burst beyond it and those drops are counted as resolver.dns refusals |
X500271RSVHST | 500 | could not route the private domains to the node resolver on {link}, the host keeps its own nameservers: {error} |
X503272RSVBND | 503 | could not listen for DNS on {addr}, retrying: {error} |
X503273RSVNAM | 503 | the node’s DNS could not take up the fabric addresses and provider names this render wrote, nothing was started: {error} |
X503274RSVLOD | 503 | the node’s DNS could not load {revision} and keeps answering from the last one it loaded: {error} |
retention
Section titled “retention”Source: modules/retention
Count: 8
| Code | HTTP | Message template |
|---|---|---|
X400916RETINP | 400 | invalid retention input, {context}{error} |
X500916RETOPF | 500 | retention {operation} failed |
X500918RETARC | 500 | retention kept backup {backup_id}: its archive at {location} could not be deleted, {detail} |
X500919RETRCL | 500 | retention space reclaim did not complete, {detail} |
X500920RETKPT | 500 | retention for tenant {tenant_name} deleted {deleted} and kept {kept} it could not delete; what it kept stays listed and is retried next sweep |
X500921RETNRS | 500 | retention cannot delete {location}: it addresses a restic repository and no restic-aware archive deleter is wired |
X500922RETCAC | 500 | retention deleted backup {backup_id} but its backup_cache row remains, it will keep appearing in shc backup ls, {detail} |
X500923RETBKG | 500 | retention could not remove expired group bundle {path}, {detail} |
rollout
Section titled “rollout”Source: modules/rollout
Count: 15
| Code | HTTP | Message template |
|---|---|---|
X200716RLTCNV | 200 | {service}/{ordinal} of {deployment} updates stop-first whatever its order says, since it keeps {paths} in anonymous volumes on {nodes}, which move to named volumes while it is stopped |
X404139RLTNRO | 404 | {deployment} has no rollout |
X409139RLTACT | 409 | the rollout of {deployment} is unfinished, so the update waits for it |
X409140RLTUNS | 409 | the replicas of {deployment} run more than one spec or incarnation, so the update waits for them to settle |
X409141RLTSTF | 409 | the rollback that settles the replicas of {deployment} finished with them still on more than one spec, so the update waits for an operator |
X409143RLTOVR | 409 | the rollout of {deployment} is over, so there is nothing to roll back |
X409144RLTSPU | 409 | the newest spec of {deployment} is staged by an operation that has not committed |
X409145RLTNON | 409 | every replica of {deployment} already runs the current spec |
X409724ROLVER | 409 | the rollout of {deployment} is no longer at version {version}, so the save changed nothing |
X409726ROLDEP | 409 | the rollout of {deployment} was not saved: this engine was deposed, its epoch is {epoch} and the current one is {current} |
X500389RLTSTP | 500 | rollout could not {step}, {error} |
X500722ROLRED | 500 | rollouts could not be read: {error} |
X500723ROLWRT | 500 | the rollout of {deployment} could not be written: {error} |
X503132RLTNST | 503 | rollout has no store |
X503721ROLSTO | 503 | rollout {op} has no store yet, the daemon has not opened the control plane |
Source: modules/scan
Count: 4
| Code | HTTP | Message template |
|---|---|---|
X400671SCNARG | 400 | invalid scan request {reason} |
X400672SCNOUT | 400 | invalid scan output {reason} |
X500607SCNWRITE | 500 | scan output could not be written {reason} |
X500673SCNTGT | 500 | scan target resolution failed {reason} |
schedule
Section titled “schedule”Source: modules/schedule
Count: 14
| Code | HTTP | Message template |
|---|---|---|
X400001CRNINV | 400 | invalid cron expression {cron} |
X400932SCHSTK | 400 | --stack is required |
X400934CRNEMT | 400 | empty cron expression |
X400935CRNFMT | 400 | invalid cron {cron} |
X400936CRNHMS | 400 | expected HH MM |
X400937CRNCNN | 400 | non-numeric clock parts |
X400938CRNOOR | 400 | out-of-range hour or minute |
X404902SCHNFD | 404 | schedule not found {job} |
X409900SCHDPL | 409 | schedule already exists for job {job} |
X500617SCHLAT | 500 | schedule {job} of {tenant}/{stack} ({environment}) was due {due}, more than its {interval} interval ago, and has not fired |
X500954SCHCAC | 500 | count active schedules failed {error} |
X500955SCHCPS | 500 | count paused schedules failed {error} |
X500956SCHNRT | 500 | next-run lookup failed {error} |
X503125SCHGON | 503 | schedule {schedule_id} waits: node {node_id} holding {stack_name} is gone |
scheduler
Section titled “scheduler”Source: modules/scheduler
Count: 31
| Code | HTTP | Message template |
|---|---|---|
X400689SCHSTA | 400 | {state} is not an assignment state: assigned, starting, ready, unready, failed, completed or stopped |
X400690SCHDUP | 400 | assignment {op} names replica {replica} twice, one batch binds a replica once |
X400693SCHUNB | 400 | intend names replica {replica}, which is not bound, so there is nothing to move |
X400697SCHREP | 400 | replica {replica} names no pod, no node or an ordinal below 0, so it has no assignment row to keep |
X400946NODRES | 400 | --reserve {item} {problem} |
X400949NODHYP | 400 | --hypervisor {value} {problem}; write |
X404692SCHDNF | 404 | deployment {deployment} does not exist, so none of its replicas can be bound |
X404950NODHYC | 404 | --hypervisor names connection {connection}, which {problem}; nothing was written |
X409676SCHUNC | 409 | global deployment {deployment} has an uncommitted staged spec, so the binding pass waits to create replicas |
X409678SCHREF | 409 | global service {service} of {deployment} has an empty eligible set ({detail}), so no node receives a replica |
X409679SCHGLB | 409 | global service {service} of {deployment} has no room on node {node} ({detail}), so that node runs no replica of it |
X409683SCHDEP | 409 | this engine was deposed: its epoch is {epoch} and the current one is {current}, so the bind changed nothing |
X409684SCHGEN | 409 | replica {replica} is at generation {got}, not the {want} this bind read, so the bind changed nothing |
X409685SCHTGT | 409 | replica {replica} is being moved to {got}, not {want}, so the bind changed nothing |
X409686SCHREN | 409 | node {node} renewed its lease since this bind read it, so it is back and the bind changed nothing |
X409687SCHFIT | 409 | node {node} has no room for this bind’s {resource} requests any more, so the bind changed nothing |
X409688SCHGRD | 409 | assignment {op} was refused by its guard and a re-read shows no cause, another write raced it |
X409695SCHSTP | 409 | {deployment} is stopped, so nothing delivers its project anywhere |
X409698SCHSPC | 409 | replica {replica} already has an incarnation at {spec}, so the start changed nothing |
X409699SCHMVG | 409 | the move of {deployment} to {target} holds no live copy of {replica} there, so the copy it left was not retired |
X409701SCHNXT | 409 | {replica} cannot start on {spec}, the spec documents incarnation {documented} but its next is {next}, another rollout took the number, the leader finishes the spec again for the rows as they stand |
X409702SCHUND | 409 | {replica} cannot start on {spec}, the spec documents no incarnation of it to start, the leader finishes the spec again for the rows as they stand |
X409947SCHRSV | 409 | node {node} keeps {reserve} for work outside SHC and has {left} left for SHC, so it takes no new replica; {deployment} fits on {fits}{quota}; nothing was written |
X409948SCHOUT | 409 | node {node} has {held} taken by {work} outside SHC and {left} left for SHC, so it takes no new replica; {deployment} fits on {fits}{quota}; nothing was written |
X413677SCHBIG | 413 | assignment {op} names {rows} replicas, more than one statement can guard: it would bind {parameters} parameters and the store takes {limit} |
X500681SCHWRT | 500 | assignment {op} could not be written: {error} |
X500682SCHRED | 500 | {what} could not be read: {error} |
X500696SCHPRT | 500 | {deployment} is installed on {node} but its delivery did not finish: {error}; it is not tried again on its own, shc update finishes it |
X503680SCHSTO | 503 | assignment {op} has no store yet, the daemon has not opened the control plane |
X503691SCHNOE | 503 | no scheduler has taken an epoch yet, the leader’s scheduler subsystem has not started |
X503694SCHDLV | 503 | nothing can deliver {deployment}‘s project to {node}: the daemon has not wired the deployment dispatch |
search
Section titled “search”Source: modules/search
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400400SRINPT | 400 | search invalid input {reason} |
X404400SRAPNF | 404 | app {name} not found |
X500401SROPFL | 500 | search {operation} failed |
selfclean
Section titled “selfclean”Source: modules/selfclean
Count: 2
| Code | HTTP | Message template |
|---|---|---|
X200326SLFSWP | 200 | self-clean {trigger} sweep on node {node} removed {what}, giving back {freed}; {disks} |
X507326SLFFUL | 507 | {disk} on node {node} is still past the self-clean sweep mark after its sweep: {figure}; the sweep kept {kept} |
Source: modules/shell
Count: 8
| Code | HTTP | Message template |
|---|---|---|
X400920SHLREQ | 400 | shell requires a stack name |
X400922SHLCMD | 400 | exec requires a command |
X404920SHLCNT | 404 | no running container for deployment {deployment} service {service} |
X500920SHLWSF | 500 | shell websocket exec failed {op}{error} |
X500921SHLEXC | 500 | shell exec failed {op}{error} |
X500922SHLPTY | 500 | shell pty operation failed {reason} |
X500923SHLRDR | 500 | shell reader done |
X503153SHLUPG | 503 | the shc daemon {target} has no streamed exec, upgrade it to this CLI’s release and run the command again |
Source: modules/stack
Count: 16
| Code | HTTP | Message template |
|---|---|---|
X400060STKREQ | 400 | stack name required |
X400062CMDRQD | 400 | command required for exec |
X400210STKARG | 400 | stack dispatch {what} is malformed {error} |
X400957STKRUN | 400 | stack runtime {runtime} is not supported on the new line; use docker, podman, incus or apple |
X400958STKVRB | 400 | stack verb {verb} is not run on the {runtime} runtime |
X400959SVCRQD | 400 | service name required for exec |
X400962STKTTY | 400 | an exec with a terminal is not run on the {runtime} runtime |
X404908STKNFD | 404 | stack {stack_name} not found |
X409069STKAMB | 409 | stack {stack_name} exists in more than one scope, found in {scopes} |
X409231CTRAMB | 409 | container {container} names more than one container ({ids}); restart one by its full id |
X409880STKRIN | 409 | start of {stack} refused: {reason}. Its data is in doubt, so it is not started until a restore of {subjects} from that backup finishes, shc backup restore {backup_id} -s {stack}{paths}, or it is uninstalled and installed fresh, shc uninstall {stack} and then shc install |
X409881STKVLT | 409 | {verb} of {stack} failed, and a vault value of it changed after its last render, which only shc update {stack} puts in its containers: {reason} |
X409882STKDEP | 409 | {verb} of {service} in {stack} refused: it needs {needs}, which an operator stopped, so it would wait without end. Start what it needs first, shc start {stack} -S {first}, or the whole deployment, shc start {stack} |
X502070EXCRPL | 502 | exec reply from node {node} is invalid {reason} |
X502071EXCHTT | 502 | node {node} answered the compose call with HTTP {status} |
X503010NDUNRC | 503 | cannot connect to node {node} {error} |
storage
Section titled “storage”Source: modules/storage/providers/alibabadisk, modules/storage/providers/awsebs, modules/storage/providers/azuredisk, modules/storage/providers/cephfs, modules/storage/providers/cloudstackvol, modules/storage/providers/dovolume, modules/storage/providers/gcepd, modules/storage/providers/incusvolume, modules/storage/providers/linodevolume, modules/storage/providers/linstor, modules/storage/providers/nfs, modules/storage/providers/upcloudstorage, modules/storage/providers/vultrvolume, modules/storage/storageapi
Count: 168
| Code | HTTP | Message template |
|---|---|---|
X200036LNKSKP | 200 | storage link-table write failed for node {node} on {provider} after its share was proven reachable, the node is not recorded as a client {error} |
X200037MNTSKP | 200 | share on node {node} could not be proven reachable for {provider}, the node is not recorded as a client and a later re-enable retries {error} |
X200038ATTSKP | 200 | store attestation write failed for node {node} on store {store}, the node is not read as reaching it {error} |
X200088FSTTRN | 200 | {path} held a torn line, NUL bytes from an interrupted write, and the rewrite took it out: {line} |
X200089FSTRGN | 200 | volume {volume_id} of {deployment} had lost its fstab line on {node}, written again from its attach: {line} |
X200310VOLSRD | 200 | volume {volume} size could not be recorded from {provider}: {reason} |
X200318VOLLRC | 200 | reconciled {count} stranded volume backup leases |
X200319VOLFIN | 200 | automatic volume failover is inert on this estate, {reason} |
X200333VOLCHL | 200 | volume {volume_id} takeover claim {claim} is off the attachment {after} after it was not handed back, the node may restart a writer its lease loss stopped |
X200342VOLRST | 200 | volume {volume_id} is back on {node} after the partition healed, remounting it and starting the writers its lease loss stopped |
X200354VOLRFS | 200 | volume {volume_id} of mount {mount} was not destroyed in {budget}, {error}; it is kept with its data on no node until shc volume remove {volume_id} deletes it |
X200368VOLRMD | 200 | volume {volume_id} of {deployment} is mounted again on {node} at {mountpoint} |
X200425VOLRWM | 200 | {step} of {device} on {node} opened DRBD resource {resource} read-write after {attempts} attempts in {waited} |
X202347VOLRNU | 202 | volume {volume_id} lease renewal committed, the read of its holder failed {error} |
X400040EXTNAM | 400 | shc-managed providers must use reserved names local, nfs, cephfs |
X400053RSVTYP | 400 | provider type {provider_type} is reserved for the singleton {reserved_name}, custom name {name} not allowed |
X400058MNGDEL | 400 | managed provider {name} cannot be removed via storage remove, use shc storage {provider_type} disable |
X400060STGWRF | 400 | path {path} is not on a {expected} filesystem |
X400081NFSBND | 400 | nfs server cannot listen on {bind}, it is neither an IP address nor an interface with an IPv4 address on this node |
X400283VOLICT | 400 | incus volume provider misconfigured, {reason} |
X400291LNSCFG | 400 | linstor volume provider misconfigured, {reason} |
X400320VOLDOC | 400 | digitalocean volume provider misconfigured, {reason} |
X400323VOLHCT | 400 | hetzner volume provider misconfigured, {reason} |
X400324VOLCFM | 400 | volume {volume_id} rebind requires -y/--yes old node detached without waiting for ack |
X400325VOLCFG | 400 | no volume backend configured {reason} |
X400326VOLCSU | 400 | volume connection {conn} for tenant {tenant} not resolvable to a volume provider |
X400327VOLAMB | 400 | storage.volumes.provider is unset and multiple volume-capable connections exist, {candidates}, set storage.volumes.provider to the one to use |
X400329VOLSNP | 400 | volume {volume_id} snapshot request incomplete, {reason} |
X400330VOLSRC | 400 | volume {volume_id} restore-snapshot requires -y/--yes, its current contents are discarded |
X400334AZDCFG | 400 | azure disk provider misconfigured, {reason} |
X400336VOLCSC | 400 | cloudstack volume provider misconfigured {reason} |
X400340LNKEVD | 400 | refusing to link node {node} to shared-filesystem provider {provider} by hand, the link row means the node proved it can reach the share and nothing proved it here, re-run the provider enable so the client mount is dispatched and verified |
X400343EBSCFG | 400 | aws ebs volume provider misconfigured, {reason} |
X400344GPDCFG | 400 | gce persistent disk volume provider misconfigured, {reason} |
X400347VOLRCH | 400 | volume connection {conn} names no provisioning location, so its reach is unknown, set the connection’s region or zone |
X400352VOLOVT | 400 | operator lease assertion refused for target {target}, {reason} |
X400362VOLLCT | 400 | linode volume provider misconfigured, {reason} |
X400855VOLPROV | 400 | volume provider hetzner is gone, use hcloud or a volume connection name |
X400929NODLNK | 400 | node {node} is not linked to storage provider {provider} |
X400931INVCFG | 400 | invalid storage configuration {reason} |
X400937QNOSUP | 400 | quotas not supported by storage provider {name}, filesystem {filesystem} |
X400942SNOSUP | 400 | snapshots not supported by storage provider {name}, filesystem {filesystem} |
X400944PRVTYP | 400 | unknown storage provider type {provider_type} |
X400945SNPMTH | 400 | unknown snapshot method {method} |
X400946QTAMTH | 400 | unknown quota method {method} |
X400947RSVNAM | 400 | reserved name {name} can only be used for shc-managed providers |
X403056CFSCBN | 403 | cephfs node handler refused, caller identity does not match target node {reason} caller={caller} target={target} |
X403080NFSCBN | 403 | nfs node handler refused, caller identity does not match target node {reason} caller={caller} target={target} |
X403081VOLCBN | 403 | volume node handler refused, {reason}, caller {caller} target {target} |
X403324VOLEEO | 403 | volume {volume_id} rebind requires SHC EE, cross-node failover needs the multi-node failover plane |
X403333VOLOVA | 403 | operator lease assertion refused, it could not be attributed to an authenticated operator and an unattributable force-detach authorization is not acceptable, {meaning} |
X403992VOLEEO | 403 | automatic volume failover requires SHC EE, this build ships no failover engine to arm. Move a stranded volume with shc volume rebind <volume> --to <node>, see https://selfhosted.cloud/pricing to upgrade |
X404031STFNOF | 404 | state folder {path} not found on storage provider {provider} |
X404032SNPNOF | 404 | snapshot {snapshot_id} not found for {path} |
X404033SRCNOF | 404 | source path does not exist {path} |
X404103STGNFD | 404 | shared storage provider {name} not configured, run shc storage {name} enable first |
X404283VOLINF | 404 | incus resource not found by {selector} {value} |
X404291LNSNOF | 404 | linstor resource definition {volume} does not exist |
X404320VOLNOF | 404 | volume not found by {selector} {value} |
X404322VOLHNF | 404 | hetzner resource not found by {selector} {value} |
X404324AZDNOF | 404 | azure resource not found by {selector} {value} |
X404336VOLCSN | 404 | cloudstack resource not found by {selector} {value} |
X404341VLTVNF | 404 | vultr resource not found by {selector} {value} |
X404343EBSNOF | 404 | aws ebs resource not found by {selector} {value} |
X404344GPDNOF | 404 | gce persistent disk resource not found by {selector} {value} |
X404346VOLHSV | 404 | no hetzner server matches node {node}, tried {tried} |
X404349VOLNPL | 404 | no machine this volume provider can see is node {node}, {why} |
X404362VOLLNF | 404 | linode resource not found by {selector} {value} |
X404383ALIVNF | 404 | alibaba disk resource not ready: {resource} |
X404385UPCVNF | 404 | upcloud {resource} not found |
X404914STGNOF | 404 | storage provider {name} not found |
X409030STGEXS | 409 | storage provider {name} already exists |
X409031STFEXS | 409 | state folder {path} already exists on storage provider {provider} |
X409032VOLXTN | 409 | volume belongs to tenant {got} not {want} |
X409033STGUSE | 409 | storage provider {name} is in use by {stacks} {stack_names} and {volumes} volume rows, pass --force to delete anyway |
X409034VOLREB | 409 | volume {volume_id} rebind refused current node {current_node} not expected {expected_node} |
X409035VOLLSE | 409 | volume {volume_id} lease refused, request generation {req_gen} row generation {row_gen} {detail} |
X409036VOLATT | 409 | volume {volume_id} still attached to {node} pass force to detach first |
X409037VOLFRB | 409 | volume {volume_id} auto failover refused, {reason} |
X409038CEPFID | 409 | ceph cluster identity conflict, /etc/ceph carries fsid {found} but the pinned cluster fsid is {pinned}, run shc storage cephfs disable before enabling again |
X409040VOLREL | 409 | volume {volume_id} provider {provider} cannot relocate from {prev_node}, its Attach does not self-detach a previous holder |
X409041VOLWKL | 409 | volume {volume_id} rebind refused, deployment {stack} is still running on {node}, rebind moves the disk and never the workload, stop the deployment or move it first |
X409042VOLSNA | 409 | volume {volume_id} is attached to {node}, detach it before restoring a snapshot |
X409043VOLRNM | 409 | refusing to lay out block volume root {root} on {node}, {reason} |
X409044VOLRLW | 409 | volume {volume_id} relocate refused, deployment {stack} still runs a writer on {node} after the relocation stopped it, stop it there and retry |
X409050VOLNKP | 409 | volume {volume} cannot be bound on runtime {runtime}, that runtime keeps no writer ledger and a bound volume is leased, so a lease-loss stop would have nothing to kill from |
X409055CEPMGR | 409 | cephfs join refused, the ceph cluster has no active mgr, check ceph -s on the leader |
X409056CEPFSD | 409 | refusing to re-bootstrap ceph, managed cluster fsid {fsid} exists but is unresponsive, repair the existing cluster or remove it via cephadm rm-cluster --fsid {fsid} and shc storage cephfs disable before re-enabling |
X409057CEPNET | 409 | cephfs enable refused, this node has no address in ceph’s public network {network}, pass --public-network with a network every node has an address in |
X409058CEPNEN | 409 | cephfs join refused, no ceph cluster answers on the leader, run shc storage cephfs enable first |
X409283VOLIMB | 409 | incus volume {volume} is on member {volume_member} and instance {instance} runs on {instance_member}, move the volume to the instance member before attaching on a local pool |
X409283VOLIOW | 409 | incus volume {volume} belongs to another deployment |
X409283VOLIPD | 409 | incus instance {instance} device {device} for volume {volume} comes from a profile and must be removed from the profile by hand |
X409283VOLIRH | 409 | incus volume {volume} is held by instance {instance}, detach it before relocating |
X409283VOLIRP | 409 | incus volume {volume} on member {member} is not this relocation’s copy and must be inspected by hand |
X409291LNSDEV | 409 | linstor resource {volume} on node {node} has no device yet |
X409291LNSOWN | 409 | linstor resource definition {volume} belongs to another deployment |
X409306VOLRSZ | 409 | volume {volume} is on {provider}, which cannot grow a volume |
X409307VOLNPV | 409 | volume {volume} was never provisioned, so it has nothing to grow |
X409308VOLDET | 409 | volume {volume} is attached to no node, so its filesystem cannot grow |
X409309VOLNSZ | 409 | volume {volume} has no recorded size and {provider} cannot report one, so it cannot grow |
X409320VOLDOD | 409 | digitalocean volume {handle} cannot be confirmed detached from {node}, {reason} |
X409324AZDREL | 409 | azure disk {handle} not freed from holder {holder} within detach-settle bound, last http {last} |
X409342VOLCLM | 409 | volume {volume_id} is claimed by another operation, {reason} |
X409343EBSDEV | 409 | aws ebs no free device slot on instance {instance}, /dev/sd[f-p] exhausted |
X409346VOLCST | 409 | cloudstack volume {id} has shc-volume tag {actual} instead of {expected} |
X409351VLTLIV | 409 | vultr refused a live detach of block {block} from the running instance of node {node}, it leaves once the instance stops or by a forced detach that reloads it: {error} |
X409352VOLLFT | 409 | mount {mount} is still held by volume {volume_id}, released {since} and not destroyed yet, {error}; it takes a fresh volume once that one is gone |
X409356VOLCSM | 409 | multiple cloudstack volumes match {name} with ids {ids} |
X409440VOLKPL | 409 | mount {mount} is held by volume {volume_id}, kept with its data at {since} when an uninstall kept it or its delete was refused to the end; no deployment attaches it again. Copy what you need off it with shc volume mount {volume_id}, then delete it with shc volume rm {volume_id} |
X409448VOLNAM | 409 | {name} names more than one volume: {volumes}. Name the deployment with -s and -e, or give the volume’s ID |
X409864VOLLSE | 409 | volume {volume_id} already leased by {owner} until {until} |
X409866VOLSFN | 409 | volume {volume_id} lease loss in progress on {node}, not yet provably stopped |
X409868VOLPPD | 409 | volume {volume_id} auto failover stalled on {node} for {stalled}, lease path {lease}, stonith path {stonith}, operator override {override} |
X409869VOLOVH | 409 | operator lease assertion refused for node {node} in state {state}, {reason} |
X500032CMDFLR | 500 | command failed {command} {error} |
X500035STGCMD | 500 | {tool} failed {stderr} {error} |
X500050CEPMON | 500 | ceph mon bring-up via cephadm failed, check the daemon log and ceph -s on the leader |
X500051CEPMDS | 500 | ceph mds placement via the orchestrator failed, check ceph orch ls and the daemon log |
X500052CEPFSC | 500 | cephfs volume creation via ceph fs volume create failed, check ceph -s and the daemon log |
X500053CEPENB | 500 | shc storage cephfs enable failed during the cephadm bring-up, check ceph -s/ceph orch host ls on the leader and the daemon log |
X500054CEPENR | 500 | ceph enroll {op} {error} |
X500054CFSCLI | 500 | cephfs client mount setup failed {op}{error} |
X500055CEPHKY | 500 | cephadm host-key install on {host} failed {op} {error} |
X500056CEPAUT | 500 | cephx client authorization failed {op} {error} |
X500076NFSSRV | 500 | nfs server setup failed {op}{error} |
X500077NFSCLI | 500 | nfs client setup failed {op}{error} |
X500078NFSDIS | 500 | nfs disable failed {op}{error} |
X500081NFSEXP | 500 | nfs export {path} is not usable, {reason} |
X500082NFSREL | 500 | nfs exportfs reload refused the exports files so nothing is published, {reason} |
X500129NFSHID | 500 | nfs storage not enabled, the local node id is unresolved so no node can be recorded as the export host {error} |
X500315VOLREP | 500 | volume repository error {op}{error} |
X500317VOLNDP | 500 | node volume provisioner {op} on {node} failed {error} |
X500318VOLSFU | 500 | node lease-loss {op} on {node} failed {error} |
X500327VOLCMD | 500 | node volume command failed {reason} |
X500328VOLWKU | 500 | volume {volume_id} rebind refused, could not determine whether the workload still runs on the old node, {reason} |
X500329VOLRLU | 500 | volume {volume_id} relocate refused, could not tell whether deployment {stack} still runs on {node}, {reason} |
X500331VOLNPR | 500 | volume {volume_id} has been stranded on {node} for {stalled} with NO force-detach proof path making progress, {blocked}, {action} |
X500333VOLCHB | 500 | volume {volume_id} takeover claim {claim} was not handed back, the node cannot restart a writer its lease loss stopped until the claim is past its deadline and the node or the leader’s sweep puts back what it replaced, {reason} |
X500917QTAERR | 500 | quota operation failed for {path} {error} |
X500919SNPERR | 500 | snapshot operation failed for {path} {op} {error} |
X501330VOLSTN | 501 | no stonith provider configured, cannot confirm the power-off of node {node} |
X501331VOLSNU | 501 | volume provider {provider} cannot snapshot block volumes, {reason} |
X501393NFSPLT | 501 | nfs {op} is not supported on {platform}, it needs the linux kernel nfs server, nfs-kernel-server with exportfs and /etc/exports.d, and a systemd unit to run it, use a host-path or s3 volume instead |
X501394CEPPLT | 501 | ceph {op} is not supported on {platform}, cephadm places mon/mgr/osd/mds daemons through systemd and the clients mount through the kernel rbd/cephfs drivers, none of which exist here, use a host-path or s3 volume instead |
X502111LDRFWD | 502 | shared-storage operation {op} could not be relayed to the raft leader, {reason} {error} |
X502283VOLIAP | 502 | incus volume api call {op} failed, http {status} {error} |
X502283VOLRLF | 502 | volume {volume_id} rebind relocation to {node} failed, {error} |
X502291LNSAPI | 502 | linstor api call {op} failed, http {status} {error} |
X502320VOLDOA | 502 | digitalocean volume api call {op} failed, http {status} {error} |
X502321VOLHAP | 502 | hetzner volume api call {op} failed, http {status} {error} |
X502322VOLNDA | 502 | node volume dispatch to {node} {path} failed, {reason} {error} |
X502324AZDAPI | 502 | azure disk api call {op} failed, http {status} {error} |
X502326VOLCSA | 502 | cloudstack volume api call {op} failed http {status} {error} |
X502329VOLDTF | 502 | volume {volume_id} rebind refused, the cloud detach from {node} failed and the volume is left attached where it was, {reason} |
X502331VLTVAP | 502 | vultr block storage api {op} failed http {status} {error} |
X502343EBSAPI | 502 | aws ebs ec2 api call {op} failed {error} |
X502344GPDAPI | 502 | gce persistent disk compute api call {op} failed {error} |
X502362VOLLAP | 502 | linode volume api call {op} failed, http {status} {error} |
X502383ALIVAP | 502 | alibaba disk api {op} failed: {error} |
X502385UPCVAP | 502 | upcloud storage api {op} failed http {status} |
X503110NOTLDR | 503 | shared-storage operation requires the raft leader, {reason} {error} |
X503345VOLRLQ | 503 | volume {volume_id} is off its mount and could not be destroyed yet, {error}; it is deleted again every minute until it is gone or its release is given up |
X503366THNPOL | 503 | lvm thin pool {pool} on node {node} holds {volumes} and is not active, {check}, every volume on it is down until the pool is activated |
X503368VOLRMT | 503 | volume {volume_id} of {deployment} is attached to {node} and not mounted at {mountpoint}, {reason} |
X503425DRBWAT | 503 | {step} of {device} on {node} waits for DRBD resource {resource} to promote this node, {reason}, trying again in {delay} |
X503425VOLRWF | 503 | volume device {device} on {node} was not opened read-write for {step}, {reason} |
X504332VOLSTL | 504 | volume binder {step} on node {node} via provider {provider} made no progress within {budget} and was abandoned, the volume is not bound{detail} |
storerpc
Section titled “storerpc”Source: modules/storerpc
Count: 5
| Code | HTTP | Message template |
|---|---|---|
X400135STRVAL | 400 | a store statement cannot carry a value of type {type} |
X501082STRNTX | 501 | a store client runs no interactive transaction ({call}), a multi-statement write goes through db.Pool.Batch |
X503128STRNOL | 503 | this node is a store client and its store list names no member |
X503134STRSTL | 503 | this node’s replica is more than {bound} behind the leader, so it answers no local read |
X503136STRUNR | 503 | no member of this node’s store list answered {function}, {count} tried, the last {error} |
subsystems
Section titled “subsystems”Source: subsystems/impl, subsystems/lifecycle, subsystems
Count: 121
| Code | HTTP | Message template |
|---|---|---|
X200202BKPANC | 200 | deployment {stack_name}/{environment} records node {node} but its deployment directory is on {holder}, backing up on {holder} and re-anchoring the row |
X200203BKPARF | 200 | deployment {stack_name}/{environment} re-anchor onto {node} failed {error}, the backup ran on the right node but the deployment row still names the wrong one |
X200863SWKILL | 200 | node {node} lost its lease and its container engine did not answer, so single writer {container} of {deployment} was killed by its cgroup, the node agent starts it again once the lease is live and the engine answers |
X200864SWFRGN | 200 | node {node} lost its lease and left single writer {container} of {deployment} running, it is not this node’s: {reason} |
X200963INGGAT | 200 | ingress reconcile traefik host check failed {error} |
X200964INGSWP | 200 | ingress route materialize sweep failed {error} |
X200965LEAFSW | 200 | certificate leaf renewal sweep failed {error} |
X200966CAEXPS | 200 | certificate intermediate expiry scan failed {error} |
X200968KCBRCN | 200 | keycloak base path reconcile failed {error} |
X200969OOBRCN | 200 | openobserve base path reconcile failed {error} |
X200971NETRCN | 200 | shared network reconcile failed {error} |
X200973CTRSTL | 200 | container reconcile stale container list failed {error} |
X200974CTRSRM | 200 | container reconcile stale container {container_id} remove failed {error} |
X200975CTRDRL | 200 | container reconcile status drift list failed {error} |
X200976CTRDRF | 200 | container reconcile status drift fix failed for deployment {deployment_id} {error} |
X200978INTTLS | 200 | internal api tls server error {detail} |
X200985PRXRAT | 200 | proxy reconcile stopped {provider} for this pass after an API rate refusal, retry after {wait} |
X200986PRXREF | 200 | proxy reconcile parked {tenant}/{stack} on {connection} after {provider} refused HTTP {status}, retry in 1h or when inputs change |
X400728EDGPRT | 400 | {source} puts the public api at {address}, the edge serves 443 on every node and nodes join through it, bind the api elsewhere |
X400975VLTRFE | 400 | SHC_VAULT_PASSWORD is set; the vault auto-unlock credential is a file, not an environment variable: the sealed vault-autounlock.cred beside shc.service’s drop-ins, or /etc/shc/vault-unlock mode 0600 on launchd |
X401014VLTPRM | 401 | vault auto-unlock credential file {path} {reason} |
X403044INTNMB | 403 | internal api peer certificate rejected, identity {identity} is not in the live node registry, node removed from the cluster or never enrolled |
X409132RQDJND | 409 | a member joined while the store was copied, so this node stays on rqlite |
X409133RPLRCN | 409 | this node’s replica was rebuilt less than an hour ago |
X409134RPLNJM | 409 | this node holds no cluster_join.json to rejoin from |
X500384RFTSNP | 500 | no rqlite snapshot with a readable meta.json |
X500385RFTTRM | 500 | raft’s current term cannot be read from raft.db, {reason} |
X500386RPLJSN | 500 | cluster_join.json is not readable JSON |
X500387COLTRE | 500 | podman info named no container tree, it answered {answer} |
X500390COLILS | 500 | the {runtime} executor on this node lists no instance |
X500391COLATR | 500 | container system status named no app root, it answered {answer} |
X500394COLEPR | 500 | the collector printed no probe result, it printed {output} |
X500990INTAPCA | 500 | failed to parse internal-api CA {path} no PEM blocks |
X500991INTAPKP | 500 | failed to load internal-api node cert and key {error} |
X500992LCSTFL | 500 | lifecycle subsystem {subsystem} start failed {error} |
X500993LCDPBL | 500 | lifecycle deps builder for {name} panicked {detail} |
X501002DBREOP | 501 | failed to reopen rqlite pool {error} |
X501003INTAPRD | 501 | failed to read internal-api CA {path} {error} |
X501017RQDSTP | 501 | rqlited manager stop returned error {error} |
X501018RQDDEM | 501 | scale-to-one demote failed, staying on the raft engine {error} |
X503015LDRPOL | 503 | leader_hub poll-driven FlipLeader returned error {error} |
X503022EVBNPL | 503 | event_bus no db pool wired, running without events.Service |
X503023EVBSTR | 503 | event_bus events.Service.Start failed {error} |
X503024EVBREC | 503 | event_bus pending-broadcast recovery sweep failed {error} |
X503025EVBNOJ | 503 | event_bus job.Service not wired, V200900JOBRUN handler is a no-op |
X503026QUENPL | 503 | queue no db pool wired, running without task.Service |
X503027QUESTR | 503 | queue task.Worker.Start failed {error} |
X503028HTPNAS | 503 | http subsystem no api.Server available, skipping TCP listener |
X503029STKRWR | 503 | stack_reconcile reconcile.Wire returned error {error} |
X503034VLTSKP | 503 | vault subsystem started without config, skipping |
X503035DKRDWN | 503 | docker daemon unreachable, continuing {error} |
X503036SSEBSK | 503 | sse_broker subsystem started without pool, skipping |
X503037COLSKP | 503 | collectors subsystem started without config, skipping |
X503038COLTKE | 503 | tick collector error {error} |
X503039CFGSKP | 503 | config_loader subsystem started without pool, skipping |
X503040DKEVEX | 503 | docker_events Subscribe exited {error} |
X503041RTRWLK | 503 | router walk failed for module {module} {error} |
X503042INTRWK | 503 | internal router walk failed for module {module} {error} |
X503043INTAEX | 503 | internal_api listener exited {error} |
X503046BKMRCN | 503 | backup_mount reconcile failed {error} |
X503046LCSTRB | 503 | lifecycle start failed in group {group}, rolling back {error} |
X503047LCSTPE | 503 | lifecycle subsystem {subsystem} stop returned error {error} |
X503048LCRBKE | 503 | lifecycle rollback Stop for {subsystem} returned error {error} |
X503048USKVNS | 503 | unix_socket filesystem entry vanished, rebinding {path} |
X503049LCFAHL | 503 | lifecycle subsystem {subsystem} reported fatal health error {error} |
X503049USKRBD | 503 | unix_socket rebind failed {path} {error} |
X503051LCSTDG | 503 | lifecycle subsystem {subsystem} started degraded, daemon staying up {error} |
X503052LCDGRD | 503 | lifecycle subsystem {subsystem} degraded {error} |
X503053LCONLD | 503 | lifecycle OnLeader callback failed for {subsystem} is_leader={is_leader} {error} |
X503055NSRWRN | 503 | node_self_register {step} failed {error} |
X503056COLPRT | 503 | collectors per-tenant alloc failed for {tenant} {error} |
X503075SCHFRR | 503 | schedule_dispatcher per-row dispatch failed {schedule_id} {error} |
X503076SCHSWP | 503 | schedule_dispatcher sweep returned error {error} |
X503077SCHDQE | 503 | schedule_dispatcher enqueue to task queue failed at {op}{error} |
X503078BKSCEX | 503 | backup_scheduler scope execute failed {scope_key} {error} |
X503079MNTMKD | 503 | backup_mount default repo {repo} mkdir failed {error} |
X503080MNTRIN | 503 | backup_mount restic init failed for {repo}, backup ops fail until configured {error} |
X503081VLTAUF | 503 | vault auto-unlock from the credential file failed {error} |
X503082VLTENV | 503 | vault auto-unlock credential could not be cleared from the daemon environment {error} |
X503083CFGRLD | 503 | config_loader DB-layer reload failed after {changed} changed paths {error} |
X503084CCAGEN | 503 | cluster_ca_genesis provision returned error {error} |
X503085CCAGSL | 503 | cluster_ca_genesis row committed but sealed vault key unreadable {error} |
X503086CCAGLF | 503 | cluster_ca_genesis first-node local port 4003 leaf sign failed {error} |
X503087CRNSKP | 503 | cron_runner skipped {module}.{cron}, previous run still in flight |
X503088CRNBAD | 503 | cron_runner unparseable schedule for {module}.{cron} spec={spec} {error} |
X503089CRNRUN | 503 | cron_runner {module}.{cron} Run returned error {error} |
X503091COLTKI | 503 | collectors tick interval {reason}, running at {interval} |
X503091GCAGEN | 503 | global_ca_genesis provision returned error {error} |
X503093OPRREAP | 503 | operation_registry stale-operation reaper sweep returned error {error} |
X503094OPRLST | 503 | operation_registry reaped lost operation {task_id}, its worker’s node held no lease for {lease}s |
X503095CCAGVL | 503 | cluster_ca_genesis deferred the sealed cluster CA key check, this node vault is locked {error} |
X503099LCONWD | 503 | lifecycle OnLeader for {subsystem} is_leader={is_leader} has not returned after {elapsed} of its {budget} budget; the leader broadcast continued without it, so this subsystem is not holding the rest back, but it has not taken on its half of the leadership edge |
X503100LCONWL | 503 | lifecycle OnLeader for {subsystem} is_leader={is_leader} returned late after {elapsed} {detail} |
X503105INTMBR | 503 | internal api membership gate registry refresh failed {error} |
X503106BKSLOD | 503 | backup_scheduler schedule load failed {error} |
X503107BKPNOK | 503 | backup_mount no backup key configured, {missing} not set, backups will refuse; set shc config set backup.repo <path-or-url> and shc config set backup.password <key> |
X503108BKPNOP | 503 | backup_mount SHC_BACKUP_REPO={repo} set without SHC_BACKUP_PASSWORD, repo not adopted |
X503109SCHPLC | 503 | schedule_dispatcher cannot dispatch {schedule_id}, deployment {stack_name} has no app directory on this node and the deployment table places it on {node} |
X503112SCHDIS | 503 | schedule_dispatcher disabled {schedule_id}, {reason} |
X503114EVBRGU | 503 | event_bus pending-broadcast recovery continuation gave up, {reason}, after {retries} consecutive retries and {republished} rows re-published, {remaining} rows remain pending_broadcast=1 and retention cannot delete them, restart the shc.service unit on a node that holds quorum to resume the drain {error} |
X503115BKPPLC | 503 | backup_scheduler refusing to back up {stack_name}/{environment} on {local_node}, the deployment table places it on {node} and a backup can only read local disk |
X503116BKPDSP | 503 | backup_scheduler could not capture {stack_name}/{environment}, the deployment table places it on {node} and the capture could not be run there, {detail} |
X503119RCLTMO | 503 | periodic tick for {loop} exceeded its {budget} budget and was cancelled, the sweep did not finish and the next tick will retry |
X503120RCLDRN | 503 | reconcile loop {loop} did not drain within {budget} of being stopped, abandoning the goroutine, a sweep is wedged somewhere its cancellation cannot reach |
X503121PUMPSTL | 503 | {subsystem} has completed no sweep in {silence}, past its {budget} budget, its pump is running but producing nothing |
X503122LDRSTL | 503 | control-plane loop {loop} has completed no sweep in {silence}, past its budget |
X503123LDRSDF | 503 | leader loop {loops} is wedged and the rqlite leadership could not be stepped down {error} |
X503124LDRSDN | 503 | leader loop {loops} is wedged, stepped the rqlite leadership down so another node leads |
X503130RFTNLD | 503 | raft has no leader now |
X503131RPLNSC | 503 | no store client to read the nodes’ rows from |
X503133RFTNUP | 503 | this node’s raft engine has not come up yet, so no node can be removed from here and nothing was changed |
X503135COLNRN | 503 | no {service} container of project {project} is running |
X503136RFTSTD | 503 | cannot tell node {node} to stand down, {why} |
X503147SCHHLD | 503 | global deployment {deployment} is held by operation {operation} in status {status} since {since} ({age}), no joining node binds it and it is not re-rendered until that operation ends, re-run shc update on it if nothing is running |
X503149LDRWRK | 503 | could not record this leader’s leader-only work for the other nodes to read: {cause} |
X503150CRNDUP | 503 | cron_runner did not fire {module}.{cron}, this tick already fired at {at} on {node} |
X503151CRNCAT | 503 | cron_runner fires {module}.{cron} once now, its tick at {tick} passed with no node firing it, last fire {last} |
X503152CRNRSV | 503 | cron ledger could not record {module}.{cron}‘s fire in the cluster store {error} |
X503938VLTSOP | 503 | vault auto-unlock credential {path} did not open, so the vault stays locked until shc vault unlock, which seals a new one {error} |
X504208BKSCDB | 504 | backup of {deployment} in the fire of {scope_key} ran past its own {budget} budget and was cancelled, the fire went on without it, {error} |
X507831BKSCSP | 507 | backup of {deployment} in the fire of {scope_key} was refused for staging space, {refusal}, and the fire tries it again while its retries last, {error} |
supportbundle
Section titled “supportbundle”Source: modules/supportbundle
Count: 14
| Code | HTTP | Message template |
|---|---|---|
X200373SPBSEC | 200 | support bundle section {section} degraded, {reason} |
X200376SPBOMT | 200 | section {section} omitted, estate-scoped sections ride only a platform-admin bundle |
X400374SPBREQ | 400 | invalid support bundle request, {reason} |
X400379SBFORM | 400 | not a loadable support bundle, {reason} |
X400380SBVERS | 400 | support bundle format version {version} is newer than the {supported} this shcsb reads |
X403378SBRDON | 403 | support bundle replay is read-only, {method} {path} would change the cluster |
X403382SPBCFG | 403 | read access to stack {stack} configuration is not granted |
X404381SBNOID | 404 | no support bundle {id} is loaded |
X404396SBNONE | 404 | not in this support bundle, {what} |
X500371SPBSTR | 500 | support bundle download failed at {step}, {error} |
X500372SPBHTT | 500 | support bundle request failed, the daemon answered http {status}, {body} |
X500395SBLOAD | 500 | support bundle load failed at {step}, {error} |
X502377SPBSTQ | 502 | support bundle store query failed, http {status}, {body} |
X503375SPBNWR | 503 | support bundle source {source} is not wired on this daemon |
Source: modules/task
Count: 13
| Code | HTTP | Message template |
|---|---|---|
X200914TSKRTY | 200 | task {task_id} scheduled for retry {attempt}/{max_attempts} in {delay}s |
X400916TSKAFF | 400 | affinity {node_id} names no node |
X404404TSKNFD | 404 | task {task_id} not found |
X409404TSKAMB | 409 | ambiguous task id {task_id} matches {count} tasks, pass a longer prefix |
X500004HDLNFD | 500 | handler not found for task {task_name} |
X500904TSKFAL | 500 | task {task_id} failed with {error} |
X500905TSKINT | 500 | task {task_id} interrupted, server restarted while running |
X500909TSKOPF | 500 | task {operation} failed |
X500912TSKTMO | 500 | task {task_id} timed out after {max_runtime_seconds}s |
X500913TSKWRK | 500 | task worker {stage} failed {error} |
X500914TSKPNC | 500 | task {task_id} {name} handler panicked {panic} |
X500915TSKLST | 500 | task lost-operation reaper {stage} failed |
X503010QUEFUL | 503 | queue at capacity {depth}/{max_depth}, task {name} rejected |
telemetry
Section titled “telemetry”Source: modules/telemetry
Count: 5
| Code | HTTP | Message template |
|---|---|---|
X200393TELNSL | 200 | no stack label in this metrics stream |
X400390TELREQ | 400 | invalid stack metrics request, {reason} |
X403391TELREJ | 403 | read access to stack {stack} telemetry is not granted |
X502392TELSTQ | 502 | OpenObserve metrics query failed, http {status}, {body} |
X502394TELUNR | 502 | telemetry store {host} could not be reached, {reason} |
tenant
Section titled “tenant”Source: modules/tenant
Count: 13
| Code | HTTP | Message template |
|---|---|---|
X400059TNTHAS | 400 | tenant {name} has {count}, use force to remove |
X400062TNTREQ | 400 | tenant name is required |
X400958TNTREQ | 400 | tenant {name} has {count} to uninstall first |
X400974TNTNAM | 400 | tenant name {name}, {reason} |
X403975TNTEEO | 403 | tenant {name} not created, creating additional tenants requires SHC EE |
X404973TNTNXS | 404 | tenant {name} does not exist, {hint} |
X409059TNTUNK | 409 | tenant {name} deployment count could not be determined, {reason}, refusing to delete a tenant whose deployments cannot be counted |
X409974TNTTMB | 409 | tenant {name} was deleted and is not re-adopted automatically, {hint} |
X500460TNTSQL | 500 | tenant sql operation {operation} failed {error} |
X500461TNTFSO | 500 | tenant fs operation {operation} failed {error} |
X500462TNTVLT | 500 | tenant admin credential vault store failed {reason} |
X500463TNTKCP | 500 | detached keycloak provisioning failed {tenant} {op} {error} |
X503973TNTIND | 503 | tenant {name} existence could not be determined, {reason} |
Source: modules/test
Count: 10
| Code | HTTP | Message template |
|---|---|---|
X400026TSTBND | 400 | the app under test at {dir} cannot be bound to the name {name} its suite installs, so the run would test a catalogue copy, declare its name in app.yaml as lower-case letters, digits, - and _ |
X404010APPNFD | 404 | app {app} not found |
X404026TSTNON | 404 | no test run {run} was started on this node |
X404910TSTNFD | 404 | app {app} has no tests directory |
X409026TSTHLD | 409 | test run {run} is still running on this node, so it is not cleaned up |
X500010BATSNF | 500 | bats is not installed |
X500011TSTNIL | 500 | apptest Runner has nil receiver |
X500012TSTCMD | 500 | apptest bats command is empty |
X500017TSTCLP | 500 | test run cleanup failed {reason} |
X500026TSTRUN | 500 | test run stage {stage} failed {error} |
underlay
Section titled “underlay”Source: modules/underlay
Count: 16
| Code | HTTP | Message template |
|---|---|---|
X400566UDPREQ | 400 | UDP probe request refused, {reason} |
X404568UDPPRB | 404 | no UDP probe {id} is held on this node for this caller, it was read already or ran out |
X404580UDPRLY | 404 | this node cannot relay a joiner’s UDP probe to {node}, {reason} |
X409571UDPPAR | 409 | this node at {address} and {members} cannot reach each other on the underlay within {window}, {detail}, no relay carries them because {relay}, open {ports} between them in both directions or publish a public address on a member that reaches both |
X409572UDPNON | 409 | this node at {address} proved no path to any member on the underlay, {reasons} |
X409576UDPARM | 409 | this node at {address} could not arm {members} for the underlay check, {detail}, so no UDP handshake with them was tried on {ports} and no relay carries them because {relay}, let this node reach their join route on TCP 443 or upgrade the member it joins through so it relays the arm |
X409598UDPOUT | 409 | UDP {port} from this node to the cluster does not get through, no WireGuard handshake from this node reached {device} on {members} within {window}, open UDP {port} outbound from this node and inbound on those members |
X409599UDPBCK | 409 | UDP {port} from the cluster back to this node does not get through, {members} received this node’s handshake on {device} and answered, the answer did not arrive within {window}, let UDP {port} replies back in to this node |
X500574UDPPRD | 500 | the underlay.pairs row cannot read {source}{error} |
X501569UDPTKN | 501 | this node cannot check a bootstrap token, so it hosts no joiner’s UDP probe |
X501570UDPHST | 501 | node {node} cannot host a UDP probe on {device}, {reason} |
X502575UDPSIG | 502 | the answer from {host} is not signed by the cluster, {reason} |
X502581UDPRLF | 502 | this node could not relay a joiner’s UDP probe to {node}: {reason} |
X502583UDPRLR | 502 | this node at {address} armed {members} through {relay} for the underlay check, but {relay} could not read back what they held, {detail}, so this node cannot tell whether {ports} reached them and the check is incomplete, not a UDP failure; join again through a member that stays in the cluster |
X503567UDPBSY | 503 | this node holds {held} UDP probes already, try again in a few seconds |
X503573UDPMBR | 503 | this node cannot list the cluster’s members, {reason} |
Source: modules/user
Count: 33
| Code | HTTP | Message template |
|---|---|---|
X400913USRPWM | 400 | passwords do not match |
X400924USRNAM | 400 | {name} is not a full name: give the person’s given and family names, like “Ada Lovelace” |
X400930USRREQ | 400 | user request missing {field} |
X400932USRTNB | 400 | caller has no tenant binding |
X400933USRROL | 400 | {role} is not a role tenant {tenant} grants, the roles are {roles} |
X400934USRGNM | 400 | group name {name} is not valid, use lowercase letters, digits, dot, underscore and hyphen, starting with a letter or digit, at most 64 characters |
X400935USRMAP | 400 | {role} needs auth.trusted_realms to map realm {realm} to tenant {target}, add {realm}={target} to auth.trusted_realms |
X400937USRRNM | 400 | realm role name {name} is not valid, use letters, digits, space, dot, underscore and hyphen, starting with a letter or digit and ending without a space, at most 64 characters, and no colon or slash |
X400939USRRST | 400 | {arg} is not a realm setting, the settings are display-name, registration=true|false, reset-password=true|false, verify-email=true|false, mail-host, mail-port, mail-security=starttls|tls|none, mail-from, mail-from-name, mail-username and mail-password=- (stdin) |
X400941USRRML | 400 | realm mail setting {setting} {reason} |
X400943USRRDN | 400 | realm setting display-name {reason} |
X403930USRPRM | 403 | requires tenant manage permission |
X403931USRXTN | 403 | cannot operate on tenant {requested}, caller bound to {own} |
X403935USRLMT | 403 | tenant {tenant} has {count} user accounts, the community edition seat limit is {limit}, more requires SHC EE |
X403939USRPLT | 403 | only a platform admin grants platform:manage in tenant {tenant} |
X403988RBCEEO | 403 | granting {role} in tenant {tenant} is organizational RBAC and requires SHC EE with the rbac entitlement, the community edition grants the baseline roles stack: |
X404930USRNOF | 404 | user {username} does not exist in tenant {tenant}, list the tenant’s users with shc user ls |
X404934USRGNF | 404 | group {group} does not exist in tenant {tenant}, list the tenant’s groups with shc user group ls |
X404936USRSTK | 404 | {role} names deployment {stack}, which tenant {tenant} does not have |
X404937USRRNF | 404 | realm role {name} does not exist in tenant {tenant}, list the tenant’s realm roles with shc tenant role ls {tenant} |
X409930USRLMG | 409 | user {username} is the last manager of tenant {tenant}, grant tenant:manage to another user first, or a platform admin can pass --force-last-admin |
X409931USRLPA | 409 | user {username} is the last platform admin, grant platform access to another user first, or a platform admin can pass --force-last-admin |
X409932USRGLM | 409 | removing group {group} would leave tenant {tenant} with no manager: tenant:manage is held only through it, by {holders}; grant tenant:manage to a user first, or a platform admin can pass --force-last-admin |
X409933USRGOW | 409 | group {name} is one SHC makes itself and is not made or removed here: SHC’s groups are {own}, and users join and leave them with shc user join and shc user leave |
X409937USRROW | 409 | realm role {name} is one Keycloak or SHC gives a meaning of its own and is not made, changed or removed here: those are {own} |
X409938USRMST | 409 | the realm of tenant {tenant} is the platform’s own and its settings and realm roles are not declared here |
X409942USRVEM | 409 | the realm of tenant {tenant} cannot require a verified email without mail settings; set mail-host and mail-from, in the same call if needed |
X413930USRLAY | 413 | launcher layout exceeds {max} bytes |
X503930USRKCN | 503 | system keycloak is not running |
X503931USRLAY | 503 | launcher layout store unavailable |
X503932USRRLM | 503 | keycloak realm for tenant {tenant} is not provisioned yet |
X503933USRGLK | 503 | user management guard lock unavailable: {reason}, retry |
X503934USRCTN | 503 | console tenant store unavailable |
Source: modules/vault
Count: 64
| Code | HTTP | Message template |
|---|---|---|
X200052VLTSKP | 200 | vault auto-unlock credential {path} was not planted because this host cannot seal it, so the vault needs shc vault unlock after every restart {error} |
X200966VLTDRW | 200 | vault unlocked but the auto-unlock drop-in {path} could not be repaired so this node will come up locked at its next restart {error} |
X200970VLTUBP | 200 | vault unlock broadcast peer {node} failed {error} |
X200972VLTENA | 200 | vault envelope state adoption failed this node has no replicated envelope state until the next unlock retries {error} |
X200973VLTCSD | 200 | vault cold-start holder declaration failed on {node} {error} |
X200997VLTUPD | 200 | vault unlock pull peer {node} accepted but no unlock landed within {wait} |
X400025PRVAUT | 400 | {auth_method} authentication requires {requirement} |
X400026PRVKTY | 400 | {provider} requires {required_key_type} key, got {got_key_type} |
X400381VLTNML | 400 | the vault path is longer than the {limit} characters vault provider {provider} can stamp, so use a shorter key |
X400382VLTNMG | 400 | the vault path encodes to a {length}-character secret id, longer than the {limit} characters vault provider {provider} accepts |
X400385VLTNMD | 400 | {name} is not a name vault provider {provider} writes for a vault path |
X400906INVSCP | 400 | invalid scope {scope} requires {required} |
X400910VLTEXP | 400 | vault export failed with {reason} {error} |
X400912VLTIMP | 400 | vault import failed with {reason} {error} |
X400916PRVUNK | 400 | unknown vault provider {provider} |
X400917PRVREQ | 400 | {config_key} is required for {provider} provider |
X400918PRVSCP | 400 | {scope_type} required for {operation} |
X400919PTHFMT | 400 | invalid path format {path} {error} |
X400925PRVPIN | 400 | pinned vault provider not configured {provider} {path} |
X400962VLTHOK | 400 | {hook} hook not wired |
X400963VLTPWM | 400 | passwords do not match |
X400964VLTRMS | 400 | invalid remap-scope pair {reason} {pair} |
X400965VLTDRI | 400 | vault operation refused the auto-unlock drop-in {path} {reason} {error} |
X400970VLTVAL | 400 | invalid secret value source: {reason} |
X400978AGNCRT | 400 | autogen certificate {key} cannot be signed: {reason} |
X400980VLTFMT | 400 | vault crypto format failure {reason} {error} |
X400981VLTCST | 400 | vault cold-start replant has no usable target {node} {reason} |
X400983AGNCHS | 400 | invalid autogen charset {charset} {reason} |
X400984VLTESL | 400 | the escrow receipt was refused: {reason} |
X400985VLTESK | 400 | the escrow label or note contains the {what} itself; record where the copy is kept, never the key |
X400986AGNTYP | 400 | vault ref {key} has an invalid autogen type {type}: {reason} |
X401012VLTINV | 401 | invalid vault password |
X401013VLTNEW | 401 | invalid new vault password {reason} {error} |
X401902VLTPWI | 401 | vault import password incorrect or data corrupted |
X403905CAPRTC | 403 | protected ca section is not ref resolvable {key} |
X403906CONPRT | 403 | protected connection credential is not accessible {key} |
X403907MIRPRT | 403 | private mirror key custody is not accessible {key} |
X403907RDCPRT | 403 | replica document keys require the replica document store |
X404905SECREQ | 404 | required vault secret {key} unresolved for {tenant} {stack} {environment} with {reason} |
X404907SECNOF | 404 | secret {key} not found |
X404986AGNCAM | 404 | autogen certificate {key} needs its {param} {ca_key}, which the vault does not hold |
X409388VLTNMO | 409 | vault provider {provider} holds an item titled {path} that SHC did not write, so it is neither read nor written |
X409807VLTRNP | 409 | vault secrets did not follow the rename of {source} to {target}, {prefix} still holds {count} of them on vault provider {provider} |
X409902SECEXS | 409 | secret {key} already exists at scope {scope} |
X409904SECAMB | 409 | autogen secret {key} for {tenant} {stack} {environment} exists but stores an empty value |
X409905SECSHD | 409 | secret {key} cannot be written at scope {scope}: a {shadow_scope} row shadows it |
X409906VLTCSH | 409 | node {node} holds the cluster’s vault cold-start capability and the vault is locked, so it cannot be re-planted. Run shc vault unlock, then shc vault coldstart replant, then retry the removal |
X409908RDCMKY | 409 | replica document MAC key changed while minting |
X409986VLTESN | 409 | there is no {what} on this estate to escrow: {held} |
X409987VLTESV | 409 | the escrow is not current for {keys}; escrow the current key and record it with shc vault escrow record --what <key> --where <label> |
X500101VLTKEK | 500 | vault kek salt failure {reason} {error} |
X500102VLTDRP | 500 | vault master rotated but the auto-unlock drop-in {path} {reason}: the new password is live, the drop-in is not; fix it before this node restarts or the vault comes up locked {error} |
X500103VLTCSP | 500 | vault cold-start plant failed on {target} {reason} {error} |
X500141VLTCLK | 500 | vault password rotated and this node is locked: the new password is current, unlock with the new password |
X500806VLTRNS | 500 | vault scope rename failed with {reason} {error} |
X500912VLTDBS | 500 | database session required for vault {operation} |
X500960PRVEXE | 500 | vault provider {provider} cli failed {stderr} {error} |
X500961VLTCRP | 500 | vault crypto failure {op} {error} |
X502221VLTPER | 502 | peer {node} refused vault {operation}: {reason} |
X503902VLTNAV | 503 | vault not available with {reason} {error} |
X503903VLTPWM | 503 | vault is locked |
X503904VLTCSL | 503 | vault cold-start {operation} needs an unlocked vault on this node; run shc vault unlock first |
X503909VLTUNS | 503 | vault password was not rotated because this node’s store swap is still ahead or a rebind is in progress |
X503950PRVAPI | 503 | vault provider {provider} api returned {status} {body} |
Source: modules/vip/compile, modules/vip
Count: 26
| Code | HTTP | Message template |
|---|---|---|
X200235VIPTIK | 200 | service VIP {what} tick failed: {error} |
X200240VIPDRT | 200 | service vip drain of {deployment} timed out after {waited}, drain needs {revision}, unconfirmed routing nodes {nodes} |
X200241VIPDRF | 200 | service VIP drain of {deployment} could not reach the store and tries again: {error} |
X200242VIPDRL | 200 | service VIP drain of {deployment} was not released, its backends stay out of the VIP tables until the drain’s lease lapses: {error} |
X200244VIPDRX | 200 | service VIP drain of {deployment} by operation {op} lapsed and was removed by the sweep: the operation never ended it, its backends were out of the VIP tables until now |
X200245VIPDRO | 200 | service VIP drain of {deployment} lapsed under its operation, {why}: its backends may be back in the VIP tables, the drain is written again as soon as the store answers |
X200257VIPOWN | 200 | published ports withheld on node {node}: {ports} |
X200286VIPLOP | 200 | published port {port}/tcp does not answer on [::1], {reason} |
X200289VIPLBP | 200 | {proto} port {port} of {host} in {deployment} goes to no service inside the cluster: its load balancer sends it to {service}, {reason}, so a client inside the cluster reaches it only at the load balancer |
X400230VIPTAB | 400 | service VIP table invalid, {reason} |
X404238VIPGON | 404 | service VIP for {service} not allocated: service {id} no longer exists |
X409232VIPFUL | 409 | service VIP range {range} is full, {held} addresses held and none released long enough ago to reuse, and no block the cluster added has a free chunk, shc cluster block add adds one |
X409236VIPRAC | 409 | service VIP allocation for {service} kept losing to another writer, retry |
X409237VIPSTL | 409 | service VIP for {service} not allocated: service {holder}, which still exists, holds the VIP, not service {id} |
X409239VIPOVL | 409 | service VIPs are off: the fabric CIDR {cidr} overlaps the VIP range {range}; move the fabric to a disjoint supernet to turn them on |
X409243VIPUNR | 409 | replica projects need service VIPs and this cluster runs none: its {field} {value} does not read, so no VIP range can be told apart from its fabric: {error} |
X409249VIPNSF | 409 | replica projects need service VIPs and this cluster runs none: it is not on the shc fabric, its fabric is {mode}, and a replica’s peers and Traefik dial its service’s VIP |
X409250VIPOVR | 409 | replica projects need service VIPs and this cluster runs none: its fabric {cidr} overlaps the service VIP range {range}, and a replica’s peers and Traefik dial its service’s VIP; a cluster made again with --address-block carves the two apart |
X409251VIPNAP | 409 | replica projects need service VIPs and this node runs none: no VIP applier runs on {platform}, and a replica’s peers and Traefik dial its service’s VIP |
X500231VIPSTO | 500 | service VIP {op} failed in the store: {error} |
X500234VIPAPL | 500 | service VIP rules not converged on this node, {reason} |
X503233VIPNST | 503 | service VIP {op} has no store yet, the daemon has not opened the control plane |
X503246VIPDRN | 503 | {deployment} was not stopped: its service VIP drain lapsed before the stop began, so its replicas may be back in the VIP tables, nothing was stopped, run the command again |
X503247VIPDRS | 503 | {deployment} was not stopped: its service VIP drain could not start, so its replicas are still in the VIP tables, nothing was stopped, run the command again: {error} |
X503248VIPDRU | 503 | {deployment} was not torn down here: the teardown names no node and this node’s identity is not known, so its replicas here could not be taken out of the VIP tables first, nothing was stopped |
X503289VIPSCP | 503 | {service} routes local within {scope} and holds no ready replica there for node {node}: its VIP refuses each connection on that node and never falls back to a replica outside the scope |
satellite collector/processor/shcscopeprocessor
Section titled “satellite collector/processor/shcscopeprocessor”Source: collector/processor/shcscopeprocessor/errors.codes
Count: 3
| Code | HTTP | Message template |
|---|---|---|
X400149SCPDIR | 400 | containers_dir must not be empty |
X400150SCPMAX | 400 | max_cached must be positive |
X400154SCPTTL | 400 | negative_ttl must be positive |