Skip to content
SHC Docs

Error code reference

Generated file. Do not edit by hand. Regenerate from the repo root with make docs/generate (or directly with CGO_ENABLED=0 go run scripts/gen-errors-md.go scripts/docsgen_wiring_pin.go and 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().

Source: core/coded
Count: 58

CodeHTTPMessage template
X200002INVFMT200invalid {format_type} format {value}, {detail}
X200003OPFAIL200operation failed {operation}{error}{output}
X200008VLTREN200failed to rename vault secrets {error}
X200009RESFAL200{operation} failed for {resource} {name} {error}
X200013PRSFAL200failed to parse {file} for {purpose} {error}
X200129CFGCHG200collector config changed {changed_keys}, restart required
X200920SUBFAL200subsystem {name} {operation} failed {error}
X400000BADREQ400bad request {detail}
X400003FLDUNK400--fields matched no key in this output, requested {fields}, available {available}
X400007VLTRES400failed to resolve vault reference, {reason}
X400008CTXREQ400context required to {operation}
X400011EMPMNT400empty mount specification
X400015NOTTYP400interactive confirmation required, pass --yes to go ahead without a prompt
X400038NMEREQ400name is required
X400051INVURI400invalid secret-ref uri {value}, {reason} {error}
X400071SCLMAL400service {service_name} has a malformed x-shc-scale block: {reason}
X400124VLTREF400could not resolve vault ref {ref}
X400225SCLOLD400--scale {service}={value} is the retired spelling, write --scale {service}={now}
X400955RTMDRV400runtime {runtime} has no driver in this daemon, so nothing can run it here
X400955RTMPIN400cannot 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
X400957INVDUR400invalid duration format {duration}
X403000FORBID403permission denied
X404000NOTFND404not found
X404023CLSNOF404cluster {name} not found in config, available {available}
X404101OPRNOF404operation {operation_id} not found or expired
X404128FILNOF404file not found {path}
X404912TNTNFD404tenant {tenant_name} not found
X408000REQTMO408operation timed out
X409000CONFLT409already exists
X429001RATLMT429rate limit exceeded, try again later
X499000REQCNL499request canceled
X500000UNKNOW500unknown error
X500002RNDDEC500render decode failed {detail}
X500005VARNLD500vars not loaded, call load first
X500051SVCNWR500{module} service not wired
X500052SVCNRS500{module} service returned nil result
X500095NOCRTS500missing cluster-CA certs, {reason}
X500104SUBCYC500circular or unresolvable subsystem dependency {stacks}
X500107TOKEXE500cluster tokenExec failed {detail}
X500901OPFAIL500{operation} failed {error}{output}
X500935INTUNH500internal server error {error}
X500938RSPENC500failed to encode {what} response {error}
X500939FSMKDR500mkdir failed {path} {error}
X500940FSWRTF500write_file failed {path} {error}
X500941FSREAD500read_file failed {path} {error}
X500942FSRMTF500rmtree failed {path} {error}
X500943FSCPYT500copytree failed {src} {dst} {error}
X500944FSLIST500listdir failed {path} {error}
X500947FSCHWN500chown failed {path} {uid} {gid} {error}
X503011NDIDUN503cannot route to node {node}, this daemon could not resolve its own node id and will not run the request locally
X503020ENTNRD503ent client not ready for {operation}
X503908LDRMOV503the cluster has no leader to answer this request right now, leadership is moving or quorum is lost, try again in a few seconds
X503911VOTCHG503this node is rejoining the cluster store as a {suffrage} while its voter role changes, so it cannot answer for a few seconds, try again
X503912STOUNR503this node’s request to the cluster store failed, {reason}
X503955RTMUNK503cannot read this node’s runtime record, so nothing runs here, {error}
X503999RTENYI503{feature} not yet wired
X504000DLNEXC504operation timed out
X507000NOSPCE507no space left on device

Count: 9

CodeHTTPMessage template
X400719WKSPAG400workshop {workshop} page {page} line {line}, {detail}
X401720WKSSGN401signing in to {portal} failed, {detail}
X403720WKSOWN403session {session} on {portal} belongs to another learner
X404718WKSNON404no workshop named {name}, the built-in ones are {known}
X404720WKSOFF404the portal {portal} offers no workshop {workshop}
X500718WKSTMX500tmux {step} failed, {detail}
X502720WKSPRT502the portal {portal} answered {step} with {detail}
X503720WKSFUL503the portal {portal} has no room for a session of {workshop} now, it said {notification}
X504720WKSWAT504session {session} did not start in {wait}

Source: modules/acme
Count: 6

CodeHTTPMessage template
X200858ACMRTY200certificate {name} not issued, retrying in {wait}, {error}
X200860ACMGON200certificate {name} not issued, the answering node {node} is gone, retrying in {wait}, {error}
X400856ACMPRV400acme provider {provider} is not configured, set acme.providers.{provider}
X409857ACMCHL409acme authorization for {name} offers no {type} challenge
X500859ACMSTO500acme certificate store {step} for {name} failed, {error}
X502855ACMORD502acme order for {name} from provider {provider} failed at {step}, {error}

Source: modules/adapter/importsaga, modules/adapter
Count: 29

CodeHTTPMessage template
X400148ADPROT400--install-root is gone, write --root
X400948ADPRUN400cannot run migration for {subject}, {detail}
X400950ADPMAN400invalid foreign app manifest, {detail}
X400951ADPMIG400invalid migration file {path} {error}
X400953ADPREQ400invalid adapter request, {detail}
X400960SAGEVI400import saga step {step} completed without evidence, so it is not done, a step that claims something about the world must measure it
X400961SAGPLN400invalid import saga plan, {detail}
X400966ADPSRC400cannot extract migration source for {app}, {detail}
X400968ADPOLD400--from {value} is the retired spelling, write {now}
X404950ADPMNF404no migration path for adapter {adapter} app {app}
X404951ADPNOA404no {adapter} apps found on the box, {detail}
X409060SAGORD409import saga step {step} cannot run until {needs} has completed with evidence, run shc import resume after resolving {needs}
X409061SAGBND409refusing 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
X409062SAGINS409refusing 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
X409063SAGDET409refusing 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
X409064SAGCMP409refusing the {step} compensation, {why}
X409065SAGCLB409the restore into {stack} did not survive verification twice, {detail}, stop the app’s own initialisation before restoring again rather than re-running the restore
X409066SAGRSM409import saga {saga} will not resume unattended, {why}
X500950ADPENU500failed to enumerate adapter {adapter} catalog {error}
X500951ADPTRN500failed to transpile foreign app {app} {error}
X500952ADPCAT500cannot read the {adapter} app catalog on the box, {detail}
X500957ADPMAT500failed to materialize adapted app {name} {error}
X500958ADPGRP500failed to assemble migration group for {name} {error}
X500962ADPXFM500migration transform {job} failed {error}
X500967ADPBND500no binding export for deployment {deployment}: {detail}; restate -i at install
X500967SAGJRN500import saga journal {op} failed, {detail} {error}
X500968SAGACT500import saga step {step} failed {error}
X501000ADPSSH501box ssh transport to {host} failed {error}
X501001ADPPUL501failed to pull data volume {volume} from box {error}

Source: modules/app/exposeflag, modules/app
Count: 757

CodeHTTPMessage template
X200021RDRLIT200plug {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
X200038SOKUNS200integration edge {plug_name} to {provider_stack_name} is unbound, {reason}, the render proceeds without it
X200039IDPUNR200restored 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}=
X200042NOLOGIN200restored 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
X200055VDPMIG200vdeployment 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
X200056VDPMGD200vdeployment sidecar directory migrated from {from} to {to}
X200058VDPKEY200vdeployment 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
X200059SOKDRF200socket {socket} of {provider}: {what} could not be rendered, {detail}; a consumer reads it as the empty string
X200063PLCWHY200placement put {tenant}/{stack} ({environment}) on {node} by rule {source}: {reason}
X200066DCKTHR200registry pull rate limit for stack {project}, retrying in {delay}
X200069PLCPRF200{tenant}/{stack} ({environment}) runs on {node}, which --prefer {prefer} does not name: {reason}
X200086PODPRJ200{deployment} has no replica projects, its compose runs as before: {error}
X200087PODROW200{deployment}‘s replica assignment rows were not written by its install, the leader’s scheduler binds them from its stored spec: {error}
X200088PODPIN200{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}
X200091JOBRAN200start job {job} of {deployment} ended 0 for run {run}
X200092DCKWAT200waiting for deployment {project} to converge for up to {budget}, containers {state}
X200093APPORP200deployment {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>
X200094DCKONE200deployment {project}: compose up --wait reported failure only for the completed {oneshots}, continuing with the convergence poll
X200095DEPRCY200deployment {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
X200096DEPRCK200deployment {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
X200097CVGRST200deployment {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
X200098CVGRSU200deployment {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
X200099STKRCN200deployment {subject} was parked at {parked} with no operation behind it and is now {settled}: {reason}
X200103SVCUND200deployment {tenant}/{stack}/{environment} no longer declares {services}, so the rows were removed and desired-vs-actual stops counting a replica nothing can satisfy
X200112APPSHD200app {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
X200113SCHPRG200schedules of uninstalled deployment {stack} in environment {environment} not removed{error}, remove them with shc schedule rm
X200115DEPIMG200deployment {project}: this deploy superseded {superseded}; kept {kept} for rollback (SHC_DEPLOY_IMAGE_KEEP), removed {removed}
X200116DEPIMK200deployment {project}: superseded images left in place: {refused}
X200117DEPIMS200deployment {project}: superseded-image cleanup skipped on this node: {reason}
X200120SPCINT200deployment spec for {tenant}/{stack} not forgotten{error}, its stored specs stay until a reinstall writes over them
X200121HKDEFR200deployment {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}
X200122HKDRAN200deployment {tenant}/{stack}/{environment}: ran {jobs}, the {hook} jobs its last update left for this start
X200124HKDWAI200deployment {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
X200130STRPRT200deployment {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
X200131STRPRE200deployment {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
X200132HKRRND200deployment {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
X200135UNICMP200uninstall of {tenant}/{stack}/{environment} did not read its rendered compose{error}, only the networks and volumes labelled for it were removed
X200136SPCRVT200deployment {tenant}/{stack}: the staged spec could not be put back{error}, the node agent may refuse the old containers until an update records again
X200138DEPDRP200deployment {tenant}/{stack} ({environment}) kept status {held}: dropped deploy outcome {outcome}, the row no longer held {expected}
X200140RNDSEL200the 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
X200141PUBTPL200{stack}: service {service} publishes {port} in its own compose, which a cluster that listens itself does not do, publish it with --expose {expose}
X200157VARHEL200the 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}
X200168SYSFRC200uninstalling {stack}, a module of the master tenant, with --force; the deployments that lose their provider with it: {consumers}
X200169PRVRBD200{consumer} still binds {provider} and was not bound to it again:{error}; run {command}
X200170PRVLOS200the deployments that lose their provider with {stack}: {consumers}
X200182OTLNIL200no telemetry collector runs in this cluster, so the OTLP export of {tenant_name}/{stack_name} ({environment}) has no destination and its telemetry is lost
X200183VLTPRG200vault 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
X200185RULPRG200placement 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}
X200186UNIUNA200uninstall 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
X200188RNDKPT200{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
X200189RNDDRP200the 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}
X200191DIRRMV200removed {path} on this node, the directory it kept of deployment {tenant}/{stack}/{environment}, which was uninstalled at {deleted_at}
X200192DIRKPT200{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
X200193CPYKPT200copy 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
X200194REPKPT200replicas of uninstalled deployment {tenant}/{stack}/{environment} on {node} not taken down, {reason}, they run until that node’s agent next applies its assignments
X200196TRERMV200removed {path} on this node, a move set it aside of deployment {tenant}/{stack}/{environment}, which was uninstalled at {deleted_at}
X200197OWNPRG200backup 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}
X200198BKSARM200backup 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}
X200199TREKPT200{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
X200204RLGCNS200a 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
X200205RLGHST200a 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
X200206RLGOWN200a 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
X200207RLGWRT200a hook of {provider} handed tenant {tenant} a registry login, and writing its connection {name} failed: {error}
X200208RLGNWR200a 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
X200209RLGBAD200a hook of {provider} printed {markers} that do not parse, so they were left out; the shape is ::shc-hook:registry-login:@=:::
X200210RLGDRP200a hook of {provider} took tenant {tenant}‘s registry login away, and removing its connection {name} failed: {error}
X200211SHRCNS200a 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
X200212SHRKEY200a hook of {provider} handed {target} a secret under {key}, which {reason}, so nothing was written
X200213SHROWN200a 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
X200214SHRWRT200a hook of {provider} handed {target} a secret, and writing it failed: {error}
X200215SHRNWR200a 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
X200217SHRDRP200a hook of {provider} took {target} away, and removing it failed: {error}
X200219SHRBAD200a hook of {provider} printed {markers} that do not parse, so they were left out; the shape is ::shc-hook:secret-share:/@:=::
X200221SHRSET200a hook of {provider} wrote {target} the secret with digest {digest}: {result}
X200222SHRRNF200a 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}
X200261PUBPND200deployment {deployment} is running, and its published ports still pending after {waited} are {ports}
X200262ROUPND200deployment {deployment} is running, and its routed hosts still wait after {waited} on the fabric policy of {nodes}
X200277SPCDOC200replica documents of {tenant}/{stack} not pruned{error}, older versions stay in the vault until the next update or uninstall prunes them
X200278SPCDOC200deployment {tenant}/{stack} ({environment}) is removed, its replica documents are still in the vault and will be retried
X200296PLCRUM200{tenant}/{stack} ({environment}) is placed without the disk check for its images on what could not be measured: {unmeasured}
X200303VOLSIZ200the app now sizes volume {volume} at {asked}, it stays at {current}
X200304VOLUNK200the app now sizes volume {volume} at {asked}, it stays at a size SHC has no record of: {reason}
X200334VOLPEND200deployment {tenant}/{stack}/{environment} has durable mounts {mounts} still on the node disk while this estate offers block storage, migrate them deliberately, for example {reason}
X200336VOLLOC200deployment {tenant}/{stack}/{environment} keeps durable mounts {mounts} on the node disk instead of new block storage, for example {reason}
X200337VOLRBK200rollback of failed install for stack {stack} could not release a block volume it created{error}
X200338VOLHST200service {service} mounts the host {kind} {source}, which SHC mounts as the data volume {volume}
X200339VOLKPA200uninstall of {tenant}/{stack}/{environment} kept {count} block volumes; {command} deletes them all
X200339VOLKPT200uninstall of {tenant}/{stack}/{environment} kept block volume {volume} on {provider}, {size}, because {reason}; {command} deletes it
X200340VOLINR200service {service} mounts {source}, which the platform provides: {how}
X200341CMPTRN200service {service} writes {key}; {did}
X200346PRVWVR200{app} service {service} is waived for {class} {value} by its own app.yaml declaration ({reason})
X200355OOPWDN200system openobserve admin password changed for admin user {username}, live password changed, record written, deployment updated
X200421DPFSTO200{stack} @ {environment} already exists, so --storage {storage} is ignored, an update keeps the storage its install chose
X200427JOBPIN200job run {run} of {deployment} ended but its container could not be confirmed gone, its fabric address stays held until the deployment is uninstalled
X200428JOBDEP200a job run of {deployment} could not be confirmed removed at its teardown, its fabric address is released with the deployment’s
X200441DROPPD200uninstall of {consumer} dropped {stores} on {provider}
X200441KEPTDT200{consumer} left {stores} on {provider}: {why}; a later deployment of this name refuses them until they are deleted
X200487VLTMNT200vault 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}
X200538SHYTWO200{app} has shc.yaml and compose.yaml; shc.yaml is the app and compose.yaml is not read
X200557INGSRC200the addresses the system ingress reaches a deployment from did not read, so the render trusts no forwarded header{error}
X200567STKPHS200{operation} of {deployment} took {phases}
X200653GLBCNT200deployment {deployment}: the replica count of its global services was not recorded{error}, shc ls compares their replicas with the count from before
X200676LICSEC200the licence section kept what it served for the {part}, {error}
X200713UPDSTL200{consumer}: plug {plug} on {provider} socket {socket} was rendered before this update moved {fields}, shc update {stack} -t {tenant} -e {environment} renders it again
X200716IMGVOL200service {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
X200717IMGREC200service {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
X200741RSTKEY200consumer {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
X200742RSTCNS200the consumers of restored provider {provider} could not be read: {detail}; the data is restored, consumer socket jobs were not run
X200745DAPUNR200the app tree of {deployment}‘s committed render could not be read on this node: {reason}, so nothing of it is read for {reader}
X200785DNTKEP200networks {networks} of {deployment} on node {node} keep their subnets after its teardown, {reason}; a teardown that removes them releases the subnets
X200787UNINTA200uninstall 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
X200788DNTHLD200node {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}
X200789DNTWID200node {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
X200790DNTENG200node {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
X200791RBKRUN200the 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
X200804DNSPLX200hosts of stack {stack} carry ports through {connections}, {reason}, so they publish no private dns record and private clients resolve the public one
X200805DNSDFO200newly bound host {hostname} has no dns record yet, its target is not decided this pass, the publish is owed and retried
X200819INTKEP200the {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}
X200828INTWAT200the {plug} edge to {provider} is waiting for {condition}: its socket job {job} said so, and SHC runs it again until it no longer waits
X200829INTWTF200the waiting {plug} edge to {provider} ({condition}) was run again and did not finish; SHC tries it again: {error}
X200900KCISUR200system Keycloak issuer origin changing {old} -> {new}, live SSO sessions invalidate and consumers must re-render, reconcile is converging, this is not a hard failure
X200901SHDNSZ200system host dns resolved zero target specs, nothing registered, retries on the next ingress endpoint change
X200902SHDNSF200system host dns record sync for {hostname} failed{error}, retried with backoff until it publishes
X200903DNSLFT200managed dns records for host {hostname} were not released ({reason}), they may still be live in the zone
X200905CLHFLP200cluster 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
X200907TRFHUP200reloading system Traefik after a dynamic config change failed{error}, routes and certs stay as traefik last read them until the next sweep re-signals
X200908DNSLAN200lan-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
X200910CONOVR200integration 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
X200911RBKPIU200rollback 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
X200912HKSKIP200pre_update job {job} skipped, service {service} of stack {stack} has no running container to exec into
X200913PROMIR200protection 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
X200915PRJCOL200deployment {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
X200916SYSCAP200module {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
X200921VAPKEP200vdeployment {stack}/{instance} retained, plug {plug} detaches without removing the instance it declares, remove it with shc uninstall {stack}/{instance}
X200926KCPWBG200system keycloak admin password rotation starting for app {app}, trigger {trigger}, steps live reset then record update then redeploy
X200927KCPWDN200system keycloak admin password rotation complete for app {app} admin user {username}, trigger {trigger}, live reset done, record updated, deployment redeployed
X200928VAPDFR200app {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
X200929VAPDWN200vdeployment {stack}/{instance} declared by plug {plug} is removed together with its host deployment, the uninstall takes every instance on the deployment down
X200930SOKSVC200socket {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
X200931ALICOL200provider {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
X200932RSTDIA200service {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
X200934ACCUNR200deployment of {app} has an unreadable or unverified app.yaml declaration, {reason}, so it renders gated: SSO required, no ungated paths
X200935UNIMOV200edge {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
X200938UPDBND200service {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
X200939BKYPKG200the 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
X200941SWMXLT200app {app} speaks Swarm, translated: {detail}
X200944ORPNIS200manifest {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
X200945ORPTMB200manifest {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
X200945QTAKNB200quota knob {key} is set but unreadable and was ignored, the app’s own figures apply
X200946ORPSTP200manifest {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
X200946QTASRC200service {service} {axis} quota {value} comes from {source}, not from this deployment
X200947ORPUNK200manifest {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
X200947QTACLM200service {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
X200948ORPLIV200manifest {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
X200948QTALRT200deploy.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
X200949VAPRET200vdeployment {stack} retained, {jobs} skipped, {reason}, the resources that cleanup would destroy are left in place
X200950APPUGW200app {stack} published open with no built-in auth, self_auth is false, anyone reaching it is unauthenticated
X200951HSTNOA200{stack} has no web address, give it one with: shc -t {tenant} update {stack} --expose
X200951VAPUNG200vdeployment {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
X200952SCHSYN200app crons for stack {stack} not reconciled into schedule rows{error}, app-declared crons may not fire until the next successful install or update
X200953LEAFRC200ingress served leaf for {host} not recorded {op}{error}, renewal subsystem will not track it until re-served
X200954HMINTN200ingress host_mapping intent for {host} not persisted{error}, multi-node reconcile will not materialize this route until recorded
X200955INGMAT200ingress reconcile could not materialize {tenant}/{stack}{error}, skipped this sweep retries next tick
X200955UNILOC200the 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
X200956CMPNGR200plug {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
X200956LEAFRN200ingress renewal could not re-sign leaf {tenant}/{host}{error}, skipped this sweep retries next tick
X200956UNINON200the 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
X200957CMPFLD200plug {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
X200957TRFRCR200traefik dns-01 reconcile recreate of system Traefik failed{error}, skipped this sweep retries next tick
X200958KCBPRC200keycloak basePath reconcile recreate of system Keycloak failed deployed {deployed} desired {desired}{error}, skipped this sweep retries next tick
X200959OOBPRC200openobserve basePath reconcile recreate of system OpenObserve failed deployed {deployed} desired {desired}{error}, skipped this sweep retries next tick
X200960NETPRE200shared network {network} pre-create did not complete{error}, installs will join it once it exists
X200960SECCHD200the secrets of {stack} were restaged from this node’s sealed cache because vault provider {provider} did not answer: {cause}
X200961DNSRTD200managed dns write for {tenant}/{stack}/{environment} suppressed, its uninstall is releasing those records
X200961SECCNS200the 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}
X200963NETUNW200provider network {network} is not visible from this host, rendering the consumer without joining it
X200966KCRORP200the 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
X200967KCRINH200fresh 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
X200967NAMDNS200deployment {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 ""
X200968KCRSIB200the 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
X200968NAMAMB200deployment {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 ""
X200969UNISHR200unintegration 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
X200970CONSIB200connection-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
X200970RMVNOP200{flag} removal {token} matched nothing on this deployment and was ignored, live entries are {live}
X200971KCUNPN200system 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
X200971UPDHED200deployment {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} to hold it at a known app
X200972RMVDON200{flag} removal {token} matched this deployment and was applied to its persisted state
X200972SYSDEB200module {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
X200974UPDCFG200update of {stack} changes its effective configuration: {delta}
X200975DURDEL200uninstall --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
X200977VARUND200{stack} carries {keys}, which {app} does not declare, so the render reads no such override and the app default applies
X200980DNSDEF200exposure=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
X200981DNSAMB200system ingress web listeners span connections {conns} and none is the one edge for stack {stack}‘s location, dns deferred until one is
X200982DNSPUB200managed dns record for host {hostname} was not republished{error}, whatever the last successful pass wrote is still what resolves
X200983DNSVIP200system ingress connection {conn} has no ready vip yet, dns for stack {stack} deferred until it provisions
X200983PLGSVC200plug {plug} pins consumer service {service} which is not in the rendered compose
X200984DNSIGP200system ingress port mappings could not be read from the committed deployment spec: {reason}
X200984PPINTN200proxied ports intent for {tenant}/{stack} not persisted{error}, leader proxy reconcile will not see this deployment’s LB mappings until recorded
X200986PRXTRU200the sources a PROXY v2 port may trust did not read, so the render trusts none{error}
X200986RBKBCK200rollback of the failed install of {deployment} did not return it to the spec it had committed because it could not {step}{error}
X200987DNSNIL200dns socket edge {plug} declares records but every one of them rendered empty, nothing was written this pass
X200988SHDNST200system host dns state could not be {operation}{error}, superseded host releases will retry on the next pass
X200989ACMPRV200ingress host {host} can never be issued a public certificate ({reason}), serving an SHC-signed leaf instead of requesting ACME
X200989DEPPRG200deployment lifecycle config for stack {stack} not purged after uninstall{error}, a reinstall may inherit a stale lease or protection flag
X200990DNSOVD200private dns records on the overlay plane publish {address}, derived from the system traefik node’s address, set dns.lan_address to pin it
X200990LSESTM200lease stamp for stack {stack} failed after successful deploy{error}, the deployment has no enforced ttl until re-stamped with shc lease renew
X200991PROSTM200protection flag for stack {stack} failed to persist after successful deploy{error}, protection unchanged until re-applied
X200992LSERTY200lease reap for stack {stack} failed, attempt {attempt}/{max_attempts}, retrying in {delay_seconds}s, {detail}
X200993RBKROW200rollback 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
X200994RBKSPC200rollback 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
X200995HSTSKP200route {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
X200996HSTDRP200persisted 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
X200998APKINT200archive digest for {tenant}/{stack} not persisted{error}, cluster-wide archive digest reads as unknown for this deployment until recorded
X200999KCRLFT200keycloak 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
X201002RTMFIX201deployment 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
X201004SSORXP201app {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
X201005RTELIT201route {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
X201006INGLIT201ingress 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
X201007SSOXHS201app {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
X201008SSOTPL201app {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
X201009DSHSSO201dashboardHost {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
X201009SSOCLK201app {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
X201010DSHLAN201dashboardHost {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
X201011ACMWCH201ingress 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
X201018ACMWDN201wildcard 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
X201020CTROBD201container observation for {tenant}/{stack}/{environment} service {service} dropped at container {container}, {reason}, {consequence}, further drops for this deployment are muted for 15m
X201021SVCRLK201service 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
X201022CTROBE201container 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
X201023CTRORP201container {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
X201024MNTDIG201deployment {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
X201025KCALAN201system 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
X201026CTRRST201restarted container {container}, service {service} of {subject}, unhealthy for about {elapsed}, past its wait of {after}, restart {restart} of this episode, the next waits {next}
X201027CTRRSF201restarting container {container}, service {service} of {subject}, unhealthy past its restart_after, failed {error}
X201028VIPNCV201this node’s routes dial no server until its service VIP state converges, {reason}
X201029CTRCAP201container {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}
X201030KCACON201{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
X201031KCACNS201the 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
X400004INSTNM400an instance name is required when installing vdeployment {app_name}, spell the target as --into --instance
X400005PARNOF400host deployment {parent_app} must be installed before the vdeployment of vapp {vapp_name} can be installed into it
X400010APPYML400app.yaml parse failed for app {name} {error}
X400016TYPMIS400socket type mismatch, plug expects {expected} but socket provides {actual}
X400017SOKDCL400plug {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}
X400018FLDREQ400field {field_name} is required but got null
X400019APPNAM400app name is required
X400021RDRURI400plug {plug_name} on provider {provider_stack_name} rendered redirectUris {rendered}, which cannot mint a safe OIDC client: {why}
X400023HKNOID400keycloak 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
X400024SOKUNS400plug {plug_name} wants socket {wanted} but provider {provider_stack_name} serves {served}, {hint}
X400025PLGUNM400integration with {provider_stack_name} cannot be inferred, the provider serves {served} and the app ships plugs {plugs}, name the plug explicitly with -i ={provider_stack_name}, or update the app so a plug matches a served socket
X400029HKBCURL400keycloak 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
X400030HKSAPUB400keycloak 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
X400031PRTMAP400invalid port mapping {value}, expected external or external-service or external-service-container, with optional conn@ prefix and /udp suffix
X400039CMDREQ400command is required
X400044HKSAROL400keycloak 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
X400045HKAUDM400keycloak 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
X400052ADNVRN400add-on version error, {detail}
X400054ADNMAL400add-on file {path} cannot be read, {detail}, an add-on that does not parse is refused rather than skipped
X400055ADNTYP400add-on {addon} is authored for {declared} but was named on an install of {requested}, an add-on token never resolves across install targets
X400056ADNAMB400{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 --instance
X400057ADNVAP400{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}
X400058ADNINS400add-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}
X400060ADNHST400add-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}
X400063ADNTOK400add-on target {token} is not /[@], the app and the add-on are one token
X400069INVNME400invalid stack name {name}
X400070SCLUNV400cannot verify the declared replica ceiling for {subject} ({source}); refusing the replica change. Run shc update {subject} to re-render the deployment, then retry
X400072APPRTN400app {app} declares requires.runtimes [{declared}] and cannot run under the {requested} runtime, install it with --runtime {suggest}
X400073SCLVAL400--scale {service}={value} is not a count, @[,…] or /: {reason}
X400074UNILFT400unintegration 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
X400075HKGRPM400keycloak 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
X400075SRCAMB400install source {source} with stack name {stack} is ambiguous, {reason}; a slash is <parent_stack_app>/, which needs --into --instance , or /, exactly one repo and one app, or name the repo with -r and pass the app bare
X400078INSACT400install refused, the request stated installed_by {actor} and {reason}
X400080HKROLM400keycloak 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
X400082HKOAUD400keycloak 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
X400083PODSCL400the pods of {subject} cannot scale as asked: {reason}
X400085PODPRJ400{deployment} cannot render as one compose project per replica: {reason}
X400087PODRTM400{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
X400091JOBORD400{deployment} cannot order its start: {why}
X400092IDNVAL400plug {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
X400093GRPMAX400group {group} of {subject} takes at most {max} members, not {asked}
X400094GRPSHP400group {group} of {subject} takes a count or counts per place, not {value}
X400095GRPSVC400{subject}: --scale {name} names a service group {group} stamps; scale the group: --scale {group}=
X400096GRPDUP400group {group} of {subject}: {detail}; a group and a service may not share a name
X400097GRPEMT400group {group} of {subject}: {detail}; a members block sits inside services: and stamps services
X400098GRPLNK400{subject}: service {service} shares a namespace or volumes with {other}, which is not in its member
X400099GRPREP400{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
X400100HKATTR400keycloak 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
X400101HKCROL400keycloak 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
X400103ARCREQ400app {app} supports only {required} but every candidate node is {available}, its images cannot run on this estate, add a node with a supported architecture
X400126CMPNRM400{deployment}‘s rendered compose cannot run as written: {reason}
X400127ENVINH400{deployment}‘s service {service} takes {key} from the environment the engine runs with: {reason}
X400132STKQRY400shc.stack.status refuses name, use stack_name
X400138PUBSEL400listen selector {selector} does not resolve: {reason}
X400140RTMSWM400runtime {runtime} is not supported, the runtimes are docker, podman, incus and apple
X400143PRFDEP400service {service} depends on {dependency}, which runs only when its profile {profile} is selected
X400144LBLFIL400service {service} reads labels from {path}, which SHC cannot read: {why}
X400145ADNTWO400add-on targets take one / token, write {app}/{addon}
X400151PRTHST400hostname {hostname} is shared by ports {ports} whose targets differ, give each port its own hostname or one shared listen
X400153VARJSN400app {app} declares json vars that hold values that are not a JSON object or list, {vars}, write each as one JSON object or list
X400156VARSEL400app {app} vars hold values outside their declared options, {vars}
X400157VARSLD400app {app} declares select vars that cannot be offered as a pick, {vars}
X400158VARUID400app {app} declares uuid vars that hold values that are not UUIDs, {vars}, use the 8-4-4-4-12 form
X400161TRFHDR400app {app} cannot log the access-log headers it is given, {reasons}
X400178INSNOD400an install does not name a node ({node}), say where the deployment may run with a rule, for example --where node={node}
X400191DEPLBL400label {key} is SHC’s: SHC derives it, so no operator sets it
X400212PUBPRV400--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
X400223SCLLOC400--scale {service}={value}: {location} names no place, no node is in a location by that name; the locations are: {known}
X400224SCLAMB400--scale {service}={value}: {location} could be any of the locations {candidates}; name one of them in full
X400226FLGOLD400{flag} is gone, write {now}
X400227OVRSVC400{flag} names nothing {app} has, {known}
X400229SCLENT400--scale {entry} is not =
X400240PODNET400{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
X400241PODPUB400port {mapping} cannot publish container port {port} of {deployment}: {reason}
X400242PODADR400{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
X400242SCLGON400the scale hook action is gone, use stop: and start:
X400256INTSEL400{file} sets {key}; a socket or plug is bound by name, never by a selector
X400259BKPFRM400backup of {subject} refused: converter {converter} reads one member from {from}, and {reason}
X400262BKPJPH400{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 .job.yaml
X400273STKOLD400--stack {stack} is gone, write --into {deployment} --instance {instance}
X400274INSREQ400--instance {instance} needs --into
X400276INTOBT400--stack {stack} and --into {into} cannot both be set, the deployment a vdeployment attaches to is --into
X400302BNDSRC400service {service} mounts {mount}, and the app directory has no {path}, nothing was changed
X400303STGVAL400--storage {value} is not {grammar}
X400304STGVOL400--storage names volume {volume}, which {app} does not declare, and {app} declares {declared}
X400305STGBKE400--storage names backend {backend}, which this cluster does not have, and the cluster has {backends}
X400307STGBND400--storage puts volume {volume} on {backend}, which cannot bind a block volume on this cluster
X400330XSHUNK400compose declares {key} at {path} which is not an SHC directive and will be ignored{hint}
X400331XSHLVL400compose declares {key} at {path} but SHC reads it {want} only
X400332XSHFLD400{key} at {path} declares unknown field {field}, it reads {known}
X400333XSHVAL400{where} at {path} cannot be honoured as declared, {why}
X400339DURCON400backup.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
X400341VDCUNK400{file} declares {key} at {where}, which SHC does not read and will silently ignore; it reads {known}{hint}
X400342VDCSHP400{file} declares {where} as {got}; SHC reads it as {want}, so as written it decodes to nothing
X400343INTPHS400{file} declares jobs.{phase}, which no runner executes and the parse silently discards; this surface runs {known}{hint}
X400343INTSHP400{file} declares {where} as {got}; SHC reads it as {want}, so as written it decodes to nothing
X400345DURSHP400backup.yaml {subject} {problem}
X400346PLCDST400{file} serves {iface}, a data store, without placement.colocate; name the fence kind its consumers share: node, location or none
X400346PLCEXC400{file} fronts an external provider and colocates by {kind}; an external provider is no node, so it colocates by location or none
X400346PLCEXL400{file} fronts an external provider without placement.location; name the fence it lives in from a var, which may render empty
X400346PLCKEY400{file} declares placement.{key}, which SHC does not read; placement takes {known}
X400346PLCKND400{file} colocates by {kind}; a catalog app may name only node, location or none, since custom fence kinds differ per estate
X400346PLCRSN400{file} loosens {iface}‘s colocation from {def} to {kind} without placement.reason; say why its services need not run near the socket
X400346PLCSHP400{file} declares placement as {got}; SHC reads a mapping of colocate, location and reason, each a string
X400346PLCSVC400{file} dials {iface}, colocated by {kind}, without a services list; the rule binds only the services the plug lists
X400346PLCSVN400{file} lists service {service}, which the app’s compose does not declare
X400348PRVSCK400privileges.docker_socket is {value}, and the scopes are self and full
X400348PRVWVB400privileges.waivers entry for service {service} is not a valid waiver, {detail}
X400350INTSEL400{file} declares {key}: on jobs.{phase} job {job}; a plug or socket job takes no selector, it runs where its integration’s endpoint runs
X400353OOUSRN400the 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
X400354OOPREF400every 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
X400357LBLSHC400service {service} writes the label {key}, which is the platform’s; a behaviour is a compose key
X400358LBLTRF400service {service} writes the label {key}; routes come from --expose
X400359LBLRSV400service {service} writes the label {key}, which SHC derives for every replica
X400360OOPWRF400the system openobserve refused the new admin password, it answered {answer}; nothing was changed
X400361INTFLD400{file} declares {key}: on jobs.{phase} job {job}, which no runner reads; the fields it reads are {known}
X400363APPKEY400{file} declares {key}:, a top-level key no reader looks for, so it would do nothing{hint}
X400366SYSEXP400{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
X400369RSZUNR400{deployment} service {service} {field} {value} is not a size compose runs
X400370REPCNT400service {service} {field} {value} is not a replica count compose runs
X400406DPFPRS400deployfile {path} could not be read: {detail}
X400408DPFREQ400deployfile {path}: {what} is missing or unusable: {why}
X400409DPFENV400deployfile {path} declares no environment {environment}; it declares {declared}
X400410DPFVAR400{where} references the variable {name} which is not defined. An undefined variable is a refusal, not an empty value ({remedy})
X400411DPFSLG400deployfile {path}: environment review needs --slug: the review host is .review., and git context is the caller’s to supply
X400412DPFAPP400deployfile {path}: app {app} not found, resolved from the working directory {wd} as the CI generator resolves it
X400414DPFENF400--env-file {path} could not be read: {detail}
X400418DPFTNT400deployfile {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}
X400418UPDABD400update 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
X400419DPFVER400deployfile {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
X400419VARMIS400{subject} requires {missing} not provided by this command: {vars}
X400420DPFINT400deployfile {path}: {key} = {provider} is not a usable provider reference: {why}
X400420RPTAPP400repoint 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
X400421RPTSRC400repoint 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
X400422RPTCMP400the 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
X400427DPFCYC400the 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
X400428DPFSET400deployfiles {first} and {second} both deploy {stack} in tenant {tenant}, environment {environment}; a set deploys each deployment once, so drop one of them
X400429DPFDOT400deployfile {path}: {key} is a dotted key, and vars nest like an app’s vars.yaml: write {nested}
X400471INTPRV400integration provision takes one -i = naming a deployed provider, got {spec}
X400472APPUPL400the uploaded app does not unpack into a tree: {error}
X400490EXPFMT400--expose {entry} is not usable: {reason}
X400492EXPOPT400--expose {entry} names unknown option +{option}
X400493EXPATR400--expose {entry} puts @ on a Traefik route, which has no meaning yet; drop the @ or write an L4 port
X400495EXPPTH400--expose {entry} puts a path on an L4 port, and a port has no path
X400496EXPLSP400--expose {entry} sets +local and +spread, but +local never forwards to another node and +spread sends to any node’s replica; keep one
X400497EXPWLD400--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
X400498EXPTGT400--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}
X400499EXPVIP400--expose {entry} publishes service selector {service_selector}, which answers only at its service VIP, and this cluster runs no service VIPs
X400530SHYUNK400{app} shc.yaml: {where} writes {key}, which is not a shc.yaml key{hint}
X400531SHYCMP400{app} shc.yaml: {where} writes {key}, a compose key shc.yaml does not take{instead}
X400532SHYXSH400{app} shc.yaml: {where} writes {key}, and shc.yaml has no x-shc keys{instead}
X400533SHYPRT400{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
X400534SHYHST400{app} shc.yaml: {where} mounts the host path {source}; a mount is a named volume, an app file (./…) or a platform mount (/etc/shc/…)
X400535SHYVAL400{app} shc.yaml: {where} sets {key} to a value SHC cannot honour: {why}
X400536SHYPRV400{app} shc.yaml: {where} writes {key}, {why}
X400537SHYDOC400{app} shc.yaml is not one YAML mapping SHC can read: {why}
X400539SHYCNV400{dir}: compose.yaml cannot be converted to shc.yaml: {why}
X400553UPDRBS400{deployment} cannot roll back, the settings its kept spec records could not be read: {error}
X400554UPDRBX400--rollback puts a kept spec back whole and takes no other change: drop {flags}
X400556UPDRNW400--rollback-on-failure rolls back when the update’s rollout fails, so it waits for the rollout; drop --no-wait
X400562SHCREQ400app {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
X400563SHCVER400app {app} declares requires.shc {required}, which is not an SHC release version X.Y.Z, so no node can run it
X400601BKPUND400{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
X400603BKPCNV400{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
X400713HLTPRB400service {service} declares an SHC health probe that cannot run: {reason}
X400714RPLUSE400{deployment}: {file} line {line} reads replica in {tag}, {reason}
X400715RPLKEY400{deployment}: {what} prints replica, which SHC reads before a replica is finished, print it into environment, command, entrypoint, healthcheck, hostname, working_dir or labels
X400725UPDCFG400app {app} sets an update this cluster cannot roll: {detail}
X400740PLGSTEM400integration name {plug} is not a consumer plug stem, write -i = using one of {plugs}
X400742PLGACC400plug {plug} accepts only {accepted} as its provider but {provider_stack_name} runs {runs}, bind it with -i {plug}= to a deployment of {accepted}
X400743PLGPRV400{file} declares providers as {got}; SHC reads a non-empty list of distinct app names, the provider apps this plug accepts
X400779EXEHKJ400runtime {runtime} cannot run the {hook} job {job}, a {context} job runs through the compose CLI only, nothing was deployed
X400782DNTIPM400network {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
X400793CNVEXP400app {app} backup.yaml converter {converter} refuses expect entry {entry}: {detail}
X400797RTMKEY400{deployment}: {what} differs by shc.runtime: {reason}
X400808ABNGON400{flag} is gone, nothing binds a deployment to a provider by itself, a plug is bound only by -i = or -i =@, drop the flag
X400809LFTGON400{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
X400832VARINPUT400variable {key} is not declared by {app}, run shc show {app} to list its variables
X400842PRFNAM400--profile {name} is not a compose profile name: a letter or digit, then letters, digits, ’_’, ’.’ or ’-‘
X400843CFGNDC400config {config} is used by a service and no top-level configs entry declares it
X400845CFGONE400config {config} needs one of file or content
X400846CFGPTH400config {config} has a file key that names no path
X400847CFGTXT400config {config} has content that is not text
X400848CFGSUB400config {config} {reason}
X400849CFGNAD400config {config} has a file relative to the app directory and this render has none
X400857CFGOUT400config {config} has a file that is not under the app directory
X400877DSKPLG400app {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
X400878DSKFLD400app {app} plug {plug} authors field {field} which the {token} socket contract does not declare, fix the field name or remove it
X400902SCLMAX400service {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
X400903INVAPP400invalid app definition with {detail}{error}
X400907DEPENV400environment is required to delete a deployment: stack {name} in tenant {tenant} occupies {environments}, name one with ?environment=
X400909PRTDFT400--expose {outside} names no service or port, so it goes to the app’s default service, and {reason}. Name the target in --expose {outside}=:, or mark the service to publish with x-shc-primary
X400914TMPFAL400template rendering failed for {name}{error}
X400935CLHNEW400cluster host {host} is not usable as the estate’s serving domain, {reason}, nothing was changed
X400936HSTNOP400no ingress candidate matches selectors {selectors}, write --expose =:
X400937HSTAMB400multiple ingress candidates match {candidates}, write --expose =:
X400938HSTPRM400services {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
X400939HSTPRP400service {service} declares x-shc-primary but no container port can be elected for it, {reason}
X400940HSTSEC400service {service} declares a secondary ingress path that cannot be honoured, {reason}
X400941HSTSCL400services {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
X400941SWMVOC400app {app} speaks Swarm in a way this cluster has no form for: {detail}
X400942SECSRC400secret {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
X400944CFGHST400config {config} takes its bytes from {source}, which does not travel with the project to the node that runs it; inline them with content:
X400945SECNAM400secret name {secret} must be letters, digits, dot, dash or underscore, starting with a letter or digit
X400952STKREQ400stack name required
X400954XNDSCK400integration with local-only socket {socket_name} cannot span nodes, provider on {provider_node}
X400960CONDTY400app {app} connection declaration {name} has unknown type {type}, declare a type the connections registry knows
X400961CONBND400app {app} declares no connection named {name}, declared {declared}, bind with -C name=connection
X400963SEEDEC400app {app} seed_once declaration is incomplete, {problems}
X400964VARIDN400app {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
X400965CONAMB400bare -C {connection} needs exactly one declared connection in app {app}, declared {declared}, use -C name=connection
X400966VARURO400app {app} declares url vars with no role, {vars}, qualify each as name@url: with one of {roles}
X400967VARROL400app {app} declares unknown variable roles, {vars}, use one of {roles}
X400968VARBOL400app {app} declares boolean vars that hold non-boolean values, {vars}, use true or false
X400969VAPREQ400app {app} plug {plug} requires a {vapp} vapp instance on its own deployment and none matches, create it with {fix}
X400972INTAMB400integration 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
X400973INTPLG400integration {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}
X400974HSTIDN400route removal {token} names a service or container port selector, a route is removed by its identity {identity} only
X400975STKNAM400stack name {name}, {reason}
X400976ENVNAM400environment name {name}, {reason}
X400978VARREQ400app {app} required vars not set, {vars}, supply them via --var, an add-on, or an integration
X400984PRTNOP400no service exposes container port {container_port}{service_selector}, cannot resolve the port’s target
X400985PRTAMB400multiple services expose container port {container_port}, {services}, name the service in --expose =:
X400986DNSPLG400app {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
X400986PRTCON400connection {conn} of type {type} has no proxy capability, port {mapping} needs a proxy-capable connection
X400986PRTHDR400port {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}
X400986PRXNOH400port {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}
X400986PRXPLN400port {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
X400987PRTUDP400proxy connection {conn} backend {impl} is tcp-only, port {mapping} cannot forward udp
X400988PRTDUP400port {external} on shared-vip connection {conn} is already claimed by deployment {stack} environment {environment}
X400989PRTALO400no free node port in {min}-{max} for port {mapping}
X400989PRTPRV400port {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
X400990PRTFIX400connection {conn} backend forwards without port remap, port {mapping} needs node port {external} which is already published
X400991PRTIDN400port removal {spec} names a service or container port, a mapping is removed by its identity {identity} only
X400991SECRPL400replica {replica} is not one path element, so its secrets cannot be staged
X400992HSTEXP400persisted 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
X400992PRTOWN400port {port}/{protocol} is {service}‘s on this node; publish another port
X400992SECNSC400replica secrets were asked for the deployment’s own set
X400993HSTFMT400invalid --expose declaration {value}, expected [/][=[:]]
X400993PRTADR400connection {conn} has no addresses to choose from, write the port without :{address}
X400994PLGREQ400app {app} required plugs not connected, {plugs}, connect each with -i plug=provider or point its vars at an external service via --var
X400994PRTONE400ports on connection {conn} name both {first} and {second}, a deployment holds one address of a connection
X400995DLGBAD400device_login declared by {declarer} is not published on {domain}: {reason}, the rest of the document still publishes
X400995HSTTGT400host {host} uses the removed =target override {target}, drop the suffix, dns follows the system ingress endpoint
X400996LSEPRT400lease operation on stack {stack} refused, environment {environment} is protected, pass --force to override
X400997HSTSEL400route {declaration} uses a retired selector spelling, write it as {canonical}
X400997LSETTL400invalid ttl {ttl}{error}, expected a duration like 72h or 30m
X400998TPLUND400app {app} compose references undefined values, {refs}, guard each with a default filter or supply the value
X400999CONREQ400app {app} required connections not bound, {connections}, bind each with -C name=connection or point its vars at direct credentials via --var
X403144RNDLDR403{deployment} is finished for node {node} only by the leader, and this node does not lead
X403215APPVTR403refusing 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
X403293VOLFRM403{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
X403332CBRRTM403node {node} runs {runtime}, which has no Docker API for the deployment’s broker socket
X403369POLRWT403{deployment} {subject} field {field} holds a value compose rewrites after the render read it
X403950INSGRT403installing 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}
X403974IMGEEO403module {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
X403976ENVEEO403named environment {name} requires an SHC licence with the environments capability, Hobby tier and up; community edition deploys everything into the default environment
X403978SYSTNT403app {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
X403979SYSSRC403module {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
X403980SYSENV403module {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
X403981BLTTNT403{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}/
X403982LDPEEO403integration 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
X403987DNSPRK403DNS publish for {hostname} is parked until its hourly retry or inputs change
X403989XIDEEO403integration 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
X403994TNTSRC403a tenant install cannot use the {kind} source {source}, {reason}
X403995DLGTIR403device_login declared by {declarer} is not published: only a system-tier deployment, in the master tenant and the platform environment, may declare it
X403995PKGLNK403app {app} carries the link {link}, which resolves outside the app, a tenant’s app may only link within itself
X403996TNTCMP403app {app} cannot run as a tenant’s app, {detail}
X403997TNTPRT403port {mapping} cannot be published by a tenant, {detail}
X404002APPNOF404application {name} not found
X404006SOKNOF404socket {socket_name} not found in {stack_name}
X404007PLGNOF404plug {plug_name} not found in {stack_name}
X404012APPDIR404app {name} not found, looked under {candidates}
X404013APPDPF404app dir not found, {path}
X404014MANNOF404no deployment manifest found at {dir}
X404015APPKPT404the app deployment {deployment} keeps could not be read, {reason}
X404019ADNNFD404add-on {addon} not found, available add-ons, {available}
X404021ADNEMP404no add-ons published in {location}
X404022ADNPIN404plug {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
X404041APPVSEL404app {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
X404064SRCNFD404source path not found {path}
X404070VDPNOF404vdeployment {instance} not found on host {host} in environment {environment}
X404143RNDNOF404{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
X404464INTPLG404{deployment} has no {plug} plug that {provider} serves: {reason}
X404906STKNOF404stack {name} not found in tenant {tenant} environment {environment}
X404907DEPNOC404stack {name} is not deployed in tenant {tenant}: it occupies no environment
X404907RPTBCK404deployment {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
X404946UNINDH404node {node} holds no deployment directory for {tenant}/{stack}/{environment}, so it tore nothing down
X404990SECLDR404secret {secret} is not in the vault yet; it is minted by the leader’s render, and this node does not mint it
X409001DEPROT409deployment {tenant}/{stack} is protected, unprotect it before destroy
X409002DEPUNK409protection state of deployment {tenant}/{stack} could not be determined{error}, refusing destroy
X409003STKEXS409stack {name} already exists in environment {environment}
X409004PRJCOL409deployment {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
X409004RPTSVC409repoint 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
X409005HKGATE409pre_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}
X409007DEPNOA409pre-uninstall safety backup for {tenant}/{stack} produced no usable archive, {evidence}, refusing teardown, pass --no-backup to tear down without one
X409008DEPNOG409no 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
X409009STKOFN409stack {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
X409010DEPNOS409deployment {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
X409012DEPNOB409the 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
X409039APPAMB409app {name} is offered at the same priority and version by {repos}, refusing to pick one
X409041APPVSPN409app {name} version {version} matches published revisions that render different images ({span}), refusing to pick one
X409042APPVSUB409app {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
X409045KCPWDS409system 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
X409046KCPWNL409system 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
X409070VDPEXS409vdeployment {instance} already exists on host {host} in environment {environment}, or its install or uninstall is still in flight
X409074VARRST409--var removal {key} cannot take effect, module {app} restates it from {source} on every update, remove it there instead
X409075SEDGAT409deployment {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
X409076STRSHR409deployment {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 .bucket= or --var .database=, or unbind the deployment that holds it
X409077BNDORP409deployment {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}
X409081PODBND409deployment {deployment}: its replica rows were not bound{error}, nothing was started
X409082PODNRW409replicas {replicas} of deployment {deployment} were rendered and have no assignment row, so the update cannot wait for them to read ready
X409091JOBFAL409start job {job} of {deployment} did not end 0, so nothing that starts after it was started: {reason}
X409092JOBNAM409start 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}
X409102HKSECO409keycloak 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
X409103HKOWNR409keycloak 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
X409103PLNSTL409the 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
X409120INSGON409deployment {stack} in tenant {tenant} environment {environment} was uninstalled while its install waited, so nothing is installed
X409136PUBOVR409{deployment} cannot listen on {port}/{protocol} at {nodes}: {holder} already does
X409137PUBAMB409--expose @{name} is both a connection and a location; rename one of them
X409142PUBHST409{hostname} is already served by {holder}
X409146EDGCAP409module {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
X409147SYSFIT409module {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
X409148RLTNFN409the rollout of {deployment} {standing}
X409152RFNRLT409the rollout of {deployment} re-finished for shcd {version} did not finish: {rollout}
X409167SYSUNI409{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
X409175GRPOLD409deployment {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.
X409176RNDOLD409deployment {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
X409179PLCRPL409no node can take replica {replica} of {deployment}: {rules} allows {nodes}, and {why}
X409194CPYLIV409this 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
X409238UPDRBF409the update of {deployment} failed, and --rollback-on-failure rolled it back to {spec}: {cause}
X409240UPDRPF409the rollout of {deployment} to spec {spec} finished but did not update {failed}
X409261ROLACT409deployment {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
X409262ROLPSD409deployment {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
X409303VOLSHR409volume {volume} is {current}, an update cannot shrink it to {asked}
X409304VOLGRW409volume {volume} is {current} and cannot grow to {asked} yet
X409305VOLNOD409volume {volume} already sits on a block volume, and putting it on the node disk would leave its data behind
X409311VOLQTA409volume {volume} cannot be capped at {size} on node {node} ({filesystem}): {why}
X409355OOPWDS409the 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
X409357OOPWNR409no 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
X409429PODDNS409{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
X409430PODDNR409{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
X409431PODINC409{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
X409440LEFTOV409{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}
X409459STKCUT409the {operation} of {deployment} was cut off when shcd stopped and did not finish; {command} runs it again
X409463INTPRB409the {plug} plug of {deployment} is already on {provider}, provision prepares a provider the plug is not on
X409464INTPRJ409{provider} serves {plug} through its {socket} socket, which declares no provision job, so nothing can prepare it for {deployment} before the edge moves there
X409465INTDSC409the {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}
X409556UPDSRK409the 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
X409741PLGCLASH409stored integration {plug} cannot be renamed to {target} because that plug already has an edge, remove the unwanted edge with shc update -i !
X409783DNTCHG409network {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}
X409846CPYMNT409a volume is still mounted, or its mount could not be read, at {mounts}
X409908DEPAMB409stack {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=
X409912HKNDEF409update 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
X409913GATHST409refusing 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 , nothing was changed
X409915GATIDP409refusing 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
X409946UNIRMT409node {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
X409949UNIRUN409deployment {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
X409950UNIELS409deployment {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
X409951UNIMOV409deployment {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
X409953OPRRUN409deployment {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
X409956CMPWTH409plug {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
X409958BNDREF409the {plug} edge to {provider} was refused by its job {job}, which changed nothing: {error}
X409961UPDSRC409update of {stack} would resolve a different source than the deployment runs: recorded {recorded}, resolved {resolved}, and it refuses to swap silently
X409962SECSTG409{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
X409963UPDVER409update of {stack} names version {version}, but the deployment runs the app from {source}, not the catalogue; write /{stack}@{version} or pass -r/--repo to move it to the catalogue at that version, or --from to change its source
X409965SECBSY409{deployment} is being rendered by another operation, which holds its secrets until the engine has answered; run this again when that one has finished
X409970INSEXS409deployment {stack} already exists in tenant {tenant}, in {environments}, and an install role only creates new deployments, so changing it needs stack:{stack}:manage
X409971APPRBV409update 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
X409972APPRWD409update 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}
X409973APPMOV409{app} is no longer in repo {from} and repo {to} serves it, so rebind with {rebind}
X409994DLGTWO409domain {domain} has {count} device_login declarers ({declarers}), so it publishes none of them
X409995DLGTNT409device_login for tenant {tenant} is not published on {domain}: the domain’s tenant is {domain_tenant}
X500009INTJOB500integration job {job_name} failed during {phase} with {error}
X500011JSNENC500json encode failed for {context}, {error}
X500012JSNDEC500json decode failed for {context}, {error}
X500013AGNPRS500failed to parse autogen store {path}, {error}
X500014AGNMAR500failed to marshal autogen store, {error}
X500015INTNET500attach integration networks failed, {error}
X500016SOKALI500alias socket hostname failed, {error}
X500017INTNST500integration binding not stored{error}
X500018VOLDEC500auto-declare volumes failed, {error}
X500030VOLPRP500resolve and prep volumes failed, {error}
X500031NETDEC500auto-declare networks failed, {error}
X500035BNDCPY500copy bind {rel} failed, {error}
X500039LDVARS500load vars failed, {error}
X500045VLTRSV500resolve vault autogen failed for stack {stack}{error}
X500047CMPRND500render compose failed, {error}
X500048CMPPRS500parse compose failed, {error}
X500051INGRSS500traefik ingress enrichment for stack {stack} failed, {op}{error}
X500058SOKPRS500parse socket {path} failed, {error}
X500059DCKCMP500docker {subcommand} failed, {error}, output {output}
X500067APPSSE500sse stream closed without terminal frame
X500068SCHCYC500module deploy scheduler dependency cycle among {stacks}
X500069SCHBLK500module {stack} not deployed, a dependency failed fail-closed
X500089UNISHP500unintegration job {job} of edge {plug} was not run, {reason}, and the state it undoes is still live
X500093CMPMAR500compose re-marshal produced unparseable yaml {error}
X500106DEPRCF500deployment {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}
X500109DPLVDT500deployment {stack} in tenant {tenant} environment {environment} never reached a health verdict within {budget}, {detail}, inspect with: shc status {stack} -t {tenant} -e {environment}
X500110JOBTMO500plug 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}
X500111VLTUNR500deployment {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}
X500112CLHUNK500the 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
X500113KCHBLD500keycloak 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
X500114CLHDIS500the estate’s replicated cluster host is {stored} but this node’s node_bootstrap.json says {local}, the replicated value wins and nothing was overwritten
X500115CTRUNH500container {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}
X500116DEPRCU500deployment {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
X500117CVGRSF500deployment {project}: the failed converge stopped {casualties} and {still_down} are still not running after the restore{output}, start them by hand ({command})
X500118INGDRK500System 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}
X500119CVGJRN500the 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
X500120STKPRK500deployment {subject} is parked at status {status} with no operation behind it: {detail}
X500121STKPRF500deployment {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
X500122DEPIMU500deployment {project}: superseded-image cleanup removed nothing: {detail}
X500124SKTTMO500socket 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}
X500125SPCREC500deployment 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
X500126HKMINT500hook {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
X500127HKRSTU500{where} of {deployment}: job {job} asked to restart {service}, which its restarts: does not declare; declare it under restarts: on the job
X500135SPCSTG500deployment spec for {tenant}/{stack} not recorded before its start{error}, nothing was started, run the update again
X500139PUBREC500published ports of {tenant}/{stack} not recorded{error}, listener state may be stale, run the update again
X500140RNDOPN500the 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
X500145RNDFIN500{deployment} could not be finished for node {node} from its stored render: {error}
X500150RFNDEP500{deployment} was not re-finished for shcd {version}, so its replicas run what an older shcd finished: {error}
X500151RFNPRP500the re-finish prep {prep} failed for shcd {version}, so no stored render is re-finished until it succeeds: {error}
X500159OPRACC500the daemon named no operation to follow, check shc operation ls before retrying
X500238UPDRBN500the update of {deployment} failed ({cause}), and its rollback to {spec} did not finish{error}
X500304VOLRDS500volume sizes for {tenant}/{environment}/{stack} could not be read: {error}
X500338VOLUNF500uninstall of {tenant}/{stack} ({environment}) could not release its block volumes{error}, the deployment directory is kept so a retried uninstall can finish
X500340VOLKPF500uninstall of {tenant}/{stack}/{environment} could not unmount the block volumes it keeps{error}, the deployment directory is kept so a retried uninstall can finish
X500355OOPWRC500the system openobserve’s new admin password could not be put on record, {reason}, so the live password was changed back and nothing was changed
X500356OOPWST500the 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}
X500357OOPWUP500the 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
X500474APPPCK500the app at {path} could not be packed to send to the daemon at {daemon}: {error}
X500558INGMOV500{deployment} was not moved off the ingress unit {unit} of node {node}{error}
X500703CATRSTS500no 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
X500707CATRNOA500node 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
X500728UNIREP500the uninstall of {tenant}/{stack}/{environment} left {left} on node {node}, {error}, run the uninstall again once that node’s replica runner is free
X500784DNTSPC500the stored spec of {deployment} could not be read to check its deployment networks’ subnets, {error}
X500821INTMOV500the {plug} edge was not moved from {from} to {to}: {error}
X500825INTEDG500the {plug} edge to {provider} failed its socket job, so this update was not applied: {error}
X500827INTBCK500the 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}
X500852DPLSTK500{failed} of {total} deployments failed{failures}
X500853DPLSET500{failed} of {total} deployments failed{failures}
X500854DPLNST500{count} of {total} deployments did not start
X500907STKFAL500deployment operation failed with {error}
X500908HKFAIL500hook {hook_type} failed with {detail}{error}
X500909HKHTTP500webhook hook returned HTTP {status} {body}
X500925KCPWRS500system keycloak admin password reset failed at {step}{error}
X500927UNILEK500unintegration 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
X500928HKOOMF500job {job} on service {service} was oom-killed inside the container {detail}
X500931HKOOMS500job {job} on service {service} reported success but was oom-killed inside the container {detail}
X500933VAPMAT500plug {plug} vapp instance {instance} failed to materialize on {stack}{error}, the deploy continues without it and the plug’s own jobs may fail
X500934VAPRST500instance {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
X500942SECRAM500secrets directory {dir} is not on tmpfs, and a secret is never staged onto disk{remedy}
X500943SECUNR500secret {secret} names vault key {key}, which did not resolve, so nothing was staged for it
X500943TMBWRT500could 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
X500944SECVLT500secret {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
X500944TMBRED500could 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
X500945PROMIV500deployment sidecar {path} holds an unreadable protection flag, {reason}, protection state is indeterminate
X500946PROCLR500deployment {stack} deployed but its protection flag could not be cleared{error}, the deployment is still protected and will refuse destroy
X500947VAPCLA500vdeployment {stack} uninstalled but its cleanup jobs {jobs} failed{error}, reclaim what they owned by hand, the instance record is gone
X500948VAPCLN500vdeployment {stack} cleanup job {job} failed{error}, the resource it destroys may still exist
X500949TKYRAM500traefik key directory {dir} is not on tmpfs, and a private key is never staged onto disk{remedy}
X500953APPYRD500app.yaml read failed for app {name} {error}
X500961NETPRF500shared network {network} could not be created{error}
X500963NETUNR500provider network {network} not reachable for the integration job
X500963SECRST500{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
X500964JOBYML500hook job {name} yaml {op} failed{error}
X500964SECPRM500{deployment}: {secret} could not be switched to what its render staged: {error}; what had been switched was put back and nothing was started
X500966PODNET500podman shared network {name} create failed{output}
X500966SECFIN500{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
X500967SECMNT500secrets 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
X500969DEPSTU500deployment state for {tenant}/{stack} exists but could not be read{error}, refusing, an unreadable manifest is not an absent one
X500973HKDREC500deployment {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}
X500976PROPTH500deployment sidecar could not be located, {reason}
X500977PROARM500deployment {stack} deployed but its protection flag could not be armed on this node{error}, the deployment is not protected
X500979DNSRMV500managed dns records for host {hostname} could not be removed on uninstall{error}
X500980PROVAL500config {key} holds a non-boolean value, protection state is indeterminate
X500981PRXEDG500proxy edge declarations unreadable, refusing to render without them, {cause}
X500981PRXFWD500the Macs’ published-port forwarder sources are unreadable, refusing to render the system Traefik without them, {cause}
X500981PRXUNT500the networks a PROXY v2 header is never trusted from are unreadable, so nothing is trusted without them, {cause}
X500981RSTSEL500restore 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
X500982DNSPUB500no 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
X500983NETPOL500docker 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
X500989PRTBND500port {mapping} needs node {node}‘s private ipv4 to bind its load-balancer publish to, {cause}
X500993LSEGUP500lease 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
X500995PRXREL500connection {conn} still publishes for deployment {stack}, its release failed{error}
X502358OOPWHO502the 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
X502739DMNLST502daemon listing failed: {cause}
X503117VLTRFD503refusing 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
X503148TRFREQ503Traefik is failed or missing after module installation; nodes cannot join this cluster on 443; re-run shc init
X503160RFNINP503{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
X503174RULGTE503a placement rule needs the daemon’s fence store to admit it, and none is wired here
X503178PLCDSP503placement put {stack} on {node}, and this process has no install dispatch to run it there; install through the daemon
X503275RSVDWN503refusing 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
X503356OOPWUN503the system openobserve could not be asked to change its admin password, {reason}; nothing was changed
X503429PODDNQ503{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
X503430PODDOC503{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
X503738DMNREQ503shc {verb} requires shcd, but shcd is not reachable; start it with {start} and run shc doctor to find out why it is down
X503901BNDNOS503{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
X503910CONMSK503connection mint seam not wired for connection {connection}
X503916HKSTOP503update 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}
X503941UNIOWN503uninstall 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
X503942UNIIND503the 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
X503943RNDLCK503the 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
X503947HLDDWN503{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
X503948DEPNOR503the 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
X503950UNIASK503deployment {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
X503954OPRCLU503the operation claim of {deployment} could not be read or written, {error}; nothing was started or written
X503957DPFASK503deployfile {path}: the dry run could not ask {cluster} whether this deployment exists, {cause}
X503987DNSSKW503dns socket edge {plug} cannot write: no dns service is wired in this process
X504102OPRFOL504the {action} goes on as operation {operation}, shc operation follow {operation} waits for it again and shc operation ls lists it while it runs
X504126JOBADM504job {job_name} did not start: its node spent the {allowance}s it allows before a job’s command, {error}
X504258ROUSTL504deployment {deployment} did not converge: routing nodes {nodes} applied no newer routing revision for {stalled}, and routing its replicas needs revision {revision}
X504259VIPNBK504deployment {deployment} did not converge: its replicas are ready, and service VIPs {services} had no ready backend for {stalled}
X504260HLTWAT504deployment {deployment} service {service} did not settle after waiting {waited}: last replica status {status}; {reason}
X504541CTRRTO504the liveness restart of container {container} did not return within {budget}, and no other restart of it begins until it does
X504557UPDSRW504the 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})
X504654CLHKCW504the cluster host is {host}, but the system Keycloak did not serve under it within {waited}; the host stands and the system Keycloak keeps converging
X504740DMNTKN504shcd 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
X507296PLCRCL507{deployment} refused before any image was pulled: {node} needed {short} more disk for its images and removing its unused images gave back {reclaimed}: {why}
X507360PLCSTR507{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

Source: modules/apparchive
Count: 3

CodeHTTPMessage template
X413737PKGBIG413the app archive of {deployment} is {size} bytes, over the {limit} byte limit a failover keeps in the cluster
X500736PKGSTR500the app archive of {deployment} could not be stored in the cluster: {error}
X500738PKGARC500deployment {deployment} cannot be delivered from its stored app archive, archive digest {digest}: {why}

Source: modules/audit
Count: 6

CodeHTTPMessage template
X400900INVDAT400invalid date format {value}
X400901AUDLMT400invalid --limit value {value}
X403987AUDEEO403the {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
X404100AUDNOF404audit record {id} not found
X500904AUDPRN500audit retention prune failed {op} {error}
X500905AUDCAP500audit row truncated by the containment cap, code {code}, {detail}

Source: modules/auth
Count: 116

CodeHTTPMessage template
X200929KCRLMW200keycloak realm {tenant} was provisioned with a setting not written: {what}
X200943OIDWAT200oidc provider at {endpoint} answered {answer}, asking again in {wait}, for up to {bound} in all
X200944KCPRED200keycloak predates SHC’s admin service client, so this admin call minted with the master admin’s password; run shc update keycloak -t master
X400058LGOTOK400back-channel logout token rejected: {reason}
X400059LGOSUB400back-channel logout token names neither a session nor a subject
X400131JWKCFG400jwks missing kcURL or realm
X400137STKTWO400the request names more than one stack ({stacks}); name the deployment once
X400166TRSENT400auth.trusted_realms entry {entry} must be =[:] naming another tenant, with entries comma-separated
X400861PADUID400auth.platform_admins entry {entry} must use / with the Keycloak user id instead of a username
X400910DEVCFG400auth login configuration invalid {detail}
X400911TLSCFG400auth login tls configuration invalid {detail}
X400912CAPINF400ca fingerprint invalid {detail}
X400921PADENT400auth.platform_admins entry {entry} must be / with a Keycloak user id
X400923SVCCLN400service client request invalid {detail}
X400925LDBREQ400ldap bind request invalid, {detail}
X400939CCLCFG400client credentials login configuration invalid {detail}
X400940CCLHTP400client credentials login refused: {endpoint} is not https, and the client secret would travel to it in clear
X400941CCLPIN400client 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 or --ca-fingerprint
X400946OIDREQ400OIDC client request invalid: {detail}
X400957IDPREQ400identity provider request invalid: {detail}
X400958IDPSEC400identity provider secret reference {ref} did not resolve to a value
X401004JWTMAL401malformed JWT
X401005JWKKID401jwks token missing kid
X401006JWKKNS401jwks kid {kid} not in keyset
X401058OIDCSIDE401forward-auth sidecar credential required
X401060SESREV401session has been revoked, sign in again
X401214KCPWST401keycloak rejected the recorded admin credential for {username}, the recorded admin password no longer matches the live keycloak database
X401900NOAUTH401not authenticated, run shc auth login
X401901TOKINV401invalid or expired token, run shc auth login to re-authenticate
X401903NOSESS401not logged in to tenant {tenant}: {reason}, run shc auth login --tenant {tenant}
X401910DEVAUTH401device authorization failed {status} {body}
X401911DEVDEN401auth login was denied at the browser consent screen
X401912CCAUTH401client credentials grant rejected {status} {body}
X403000AUTHZF403authorization failed, no context available
X403900NOPERM403permission denied for {scope} on {resource}
X403903NOUSER403authorization failed, no authenticated user
X403904NOTENT403authenticated user is not authorized for tenant {tenant_name}
X404916AUTRLM404realm {realm} does not exist in keycloak yet
X404922SVCNOF404service client {name} does not exist, run shc auth list-service-clients to list them
X404926LDBNOF404ldap bind {name} does not exist in tenant {tenant}, run shc auth list-ldap-binds -t {tenant} to list them
X404951OIDNOF404OIDC client {client_id} does not exist in tenant {tenant}
X404957IDPNOF404identity provider {alias} does not exist in tenant {tenant}
X408910DEVEXP408auth login timed out, the device code expired before login completed
X409910CAPINM409cluster ca fingerprint mismatch expected={expected} got={got}
X409911CAPINC409the 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
X409924SVCKND409client {name} is not a service client, so it is not deleted here
X409927SVCSCP409service client {name} already exists with rights other than {scope}; delete it with shc auth delete-service-client {name} and create it again
X409928LDBAPP409ldap 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
X409930LDBEXS409ldap bind {name} is already there in tenant {tenant} and its password is not read back, pass --rotate-secret to regenerate it
X409944KCPRED409keycloak runs without SHC’s admin service client env and still needs shc update keycloak -t master
X409945SVCADM409service 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
X409947OIDMST409OIDC client management refuses realm master; choose a tenant realm
X409948OIDRES409OIDC client {client_id} is reserved for the platform or Keycloak
X409949OIDPLG409OIDC client {client_id} in tenant {tenant} is owned by deployment {deployment} through plug {plug}; change that deployment
X409952OIDEXS409OIDC client {client_id} already exists in tenant {tenant}; import it instead of creating it
X409953OIDKND409client {client_id} in tenant {tenant} is not a supported standalone OIDC client: {reason}
X409956OIDAUT409OIDC client {client_id} in tenant {tenant} cannot change authentication in place; delete and create it, or import the new one
X409957IDPMST409on realm master an identity provider links existing users only; first_login must be link-only, because every master identity is platform root
X409959IDPRES409identity provider alias {alias} is reserved for the vendor portal
X409963IDPEXS409identity provider {alias} already exists in tenant {tenant}; import it instead of creating it
X409964IDPKND409identity provider {alias} in tenant {tenant} is not an OIDC provider
X409969IDPFLW409the SHC link-only first login flow in tenant {tenant} is incompatible or could not be made exact
X410059RLMGON410the realm lookup routes are retired, forward-auth reads the realms from its node’s auth section
X413137STKBIG413the request body is larger than any stack route accepts: {limit} bytes
X500050KCRLMP500realm provisioning failed for tenant {tenant} exit={exit_code} stderr={stderr}
X500051KCRLMD500realm deprovisioning failed for tenant {tenant} exit={exit_code} stderr={stderr}
X500052KCROLC500role create failed for tenant {tenant} role {role} exit={exit_code} stderr={stderr}
X500053KCROLD500role delete failed for tenant {tenant} role {role} exit={exit_code} stderr={stderr}
X500054KCROLB500batch role create failed for tenant {tenant} roles={role_count} exit={exit_code} stderr={stderr}
X500057FWDSEC500forward-auth login client secret unresolved {reason}
X500062FWDENUM500forward-auth redirect-uri enumeration unresolved {reason}
X500063FWDRMIS500forward-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}
X500064FWDRSTP500forward-auth redirect-uri restamp failed for trigger {trigger} {reason}
X500138STKSPL500the stack-scoped request gate could not spool the request body: {error}
X500200JWKDEC500jwks decode failed, {error}
X500201JWKEMP500jwks fetch empty keyset
X500202JWKNUS500jwks fetch no usable signing keys
X500203JWKRSN500jwks rsa {param} decode failed, {error}
X500204JWKECC500jwks ec unsupported curve {curve}
X500205JWKECP500jwks ec {param} decode failed, {error}
X500206JWKKTY500jwks unsupported kty {kty}
X500207JWKCLM500jwks claims are not a JSON object
X500209AUNTRN500auth no http transport wired
X500210KCADMF500kcadm {operation} failed in {tenant} for {subject} stderr={stderr}
X500211KCADPS500parse kcadm output for {operation} in {tenant} failed {error}
X500906KYCLKC500keycloak not configured
X500910DEVNET500auth login request to {endpoint} failed {error}
X500911OIDPRS500auth login parse {stage} response failed {error}
X500913CAPINF500ca pin fetch failed {detail}
X500914SVCCLP500service client provisioning failed for {name} {detail}
X500935SVCSEL500sealing service client {name} into vault key {key} failed: {detail}
X500938SVCLED500recording service client {name} as scoped failed: {detail}
X500939SVCLED500service client {name} was deleted but its scoped record was not dropped: {detail}, run shc auth delete-service-client {name} again
X502001KYCERR502keycloak error {status_code}
X502002JWKSTC502jwks fetch status {status_code}
X502912OIDDISC502oidc discovery failed {detail}
X502954OIDKCA502Keycloak OIDC client operation {operation} failed for {tenant}/{client_id}: {detail}
X502957IDPKCA502Keycloak identity provider operation {operation} failed for {tenant}/{alias}: {detail}
X502958IDPDSC502issuer {issuer} discovery failed: Keycloak could not read its OpenID configuration, or it names another issuer
X503005KYCUNA503keycloak unavailable {error}
X503061LGOREV503logout could not determine whether the credential is still live: {reason}
X503900SVCKCN503system keycloak unavailable, cannot provision the service client
X503913CARTNW503ca root provider not wired
X503914CARTNA503global root ca not available {detail}
X503915OIDPUB503keycloak public url not resolved {detail}
X503927LDBKCN503system keycloak unavailable, cannot reach its ldap binds
X503929LDBDEP503cannot tell whether an installed app holds ldap bind {name} in tenant {tenant}: {reason}, retry
X503935SVCSEL503the vault is not available here, so the service client credential cannot be sealed
X503936SVCLED503cannot read whether service client {name} is scoped: {reason}, so its token is refused, retry
X503937SVCLED503the store of scoped service clients is not available here, so no scoped client was minted
X503950OIDOWN503cannot establish ownership of OIDC client {client_id} in tenant {tenant}: {reason}; retry after repairing deployment state
X503955OIDKCN503system Keycloak unavailable; cannot manage tenant OIDC clients
X503958IDPKCN503system Keycloak unavailable; cannot manage identity providers
X503959IDPGAT503identity provider entitlement gate is not wired
X503960AUTNRD503the sign-in service is not ready yet, retry shortly
X503961PRMDGR503permissions for {scope} on {resource} could not be read while the identity provider is degraded, retry shortly

Source: modules/backup/commands, modules/backup
Count: 338

CodeHTTPMessage template
X200043CNVFAL200converter {converter} did not complete for {stack_name}, {detail}
X200045PRPFAL200preparation did not complete for {stack_name}, {detail}
X200060RCVFBK200app archive extract did not succeed for {stack_name}, falling back to catalog, {detail}
X200062VLTXSK200vault secrets export skipped for {tenant}/{stack_name}/{environment}, {detail}
X200063BKPQSC200backup quiesce degraded for {stack_name}, {op} {error}
X200064CFGCAP200deployment config capture skipped for {tenant}/{stack_name}/{environment}, {detail}
X200065MAPRPL200mapping replay did not complete for {stack_name}, {detail}
X200066RSTPRM200restore could not reapply captured permissions on {mount}, {detail}
X200068HBDSKP200host bind {path} skipped from backup capture, {reason}
X200070DPLREG200deployment re-registration did not complete for {stack_name}, {detail}
X200071BKPARC200backup {backup_id} master archive build failed, {detail}
X200072BKPFGT200backup {backup_id} row deleted but its backing data at {location} could not be removed, {detail}
X200073MFSKIP200manifest dump skipped for backup {backup_id}, {detail}
X200074BKPPRN200restic prune of {repo} did not complete after retention, {detail}
X200075BKPSEL200backup {backup_id} could not be sealed into the configured repository, {detail}
X200075MANSKP200manifest inventory check skipped for backup {backup_id}, {detail}
X200076BKPLSE200reclaimed stale backup lease for {tenant}/{stack_name}, backup {backup_id} had not heartbeated for {stale_seconds}s and was blocking backup/uninstall
X200077RSTJSK200restore job {job} skipped, this archive does not carry its {converters}, {reason}
X200078BKPLIV200backup {backup_id} was not captured as a consistent point-in-time ({state}), restoring anyway
X200080BKPQBR200the freeze did not survive the capture of {stack_name}, {detail}, the archive is stamped live
X200081BKPSTP200backup {backup_id} held the freeze on {stack_name} for {held_seconds}s, past the hold deadline, {disposition}
X200082BKPSTR200deployment {stack_name} is running again after backup {backup_id} stopped it for the capture, down {down_seconds}s
X200083BKPNRS200the 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
X200083RSTVUNR200restore verification could not read {path}, {detail}, proceeding as {taken}
X200084BKPQRS200deployment {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
X200085BKPPRS200deployment {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
X200086BKSDED200a 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
X200087BKPNOD200backup {backup_id} of {stack_name} carried no application data: all {skipped} data subjects were skipped, the archive holds deployment metadata only
X200088BKPDED200released 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
X200089BKPSPW200backup free-space preflight skipped, {detail}
X200089BKPSVL200backup captures plaintext credentials for {tenant}/{stack_name}/{environment}: secret vars [{keys}] could not be sealed into the vault, {detail}
X200090BKPORF200backup {backup_id} left {size} bytes at {path} that its row did not name; reclaimed by id
X200090BKPRTY200re-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
X200091BKPCOW200backup 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
X200092BKPSSW200swept abandoned scheduled-backup staging for {backup_id} at {path}; no live run owns it, a leftover of a crash or restart
X200100RSTVPOP200restore 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
X200101RSTIDSC200restore did not replay the archive’s deployment identity sidecar onto {stack}, {taken}
X200102SYNXTN200backup sync skipped {skipped} tagged for {foreign} while syncing as tenant {tenant}, a cache row is tenant-scoped so none was adopted
X200104RSTDUW200deployment {stack}: the post-restore durability witness could not be recorded ({detail}), so this restore cannot say whether its data survived the bring-up
X200105BKPPRW200backup protection audit ({check}): {finding}. shc doctor run --category backup reproduces this
X200108BKPIDX200backup {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}
X200110BKPCMP200backup {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
X200110RSTLDR200restore did not replay {file} from the archive onto {stack}, {taken}
X200111BKPSCP200backup 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
X200112BKPSTS200restic snapshot {snapshot_id} is recorded at its apparent size, because restic could not report what it stores, {detail}
X200113BKPMKY200backup mirror {repo}: {detail}
X200119IMPOWN200import of {archive} could not keep the captured owners and modes, a restore of it lands them as this daemon’s, {detail}
X200124BKPMIX200backup {backup_id} is sealed without a member index, so browsing it copies the whole archive to staging, {detail}
X200125MTSCPY200browsing backup {backup_id} copies the whole archive to staging because {reason}
X200127RSTSOK200restore left out {sockets} of {mount} ({sample}), a socket holds no data and its app makes it again when it starts
X200128BKPDBS200backup is taken without database {database} of plug {plug} on {provider}, {reason}
X200297RCVRUM200recover of {stacks} runs without the disk check for its images on what could not be measured: {unmeasured}
X200300BKPRAW200backup {backup_id} of {stack_name} holds raw mount bytes where converter {converter} did not complete, {detail}
X200452BKPTHR200backup of {stack_name} found {replicas} stopped after the thaw and started it again
X200478RSTINT200the 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
X200498RLCCFG200backup.repo is {configured}, not {target}: new captures still go there
X200657BKPVDR200mount {mount} of {deployment} is captured as its directory, the volume {volume} no node holds {why}
X200659BKPVRL200the volume {volume} attached to {node} for the capture of mount {mount} stays attached there, {reason}
X200683CNVEMP200converter {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}
X200743RCVSHD200recovered {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
X200744RCVSHA200the 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}
X200873RSTUPD200the update that follows the restore of {stack_name} did not complete, {detail}; run shc update {stack_name}
X200874RSTSVL200restore of {tenant}/{stack_name}/{environment} left plaintext credentials at rest: secret vars [{keys}] could not be sealed into the vault, {detail}
X200898RSTMAP200restore of {deployment} writes backup {backup_id}‘s mount {from} into {to}
X200899RSTSTA200restore of {deployment} starts it: its operator had stopped it, and a restore ends with the deployment serving
X400048RCVINP400invalid recover input {op} {error}
X400049RCVMAN400failed to load manifest from {path}, {op} {error}
X400077BKPSCD400refusing 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
X400078BKPSNR400refusing 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
X400079BKPSKD400scheduled 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
X400105BKPSCR400refusing 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
X400106BKPSCG400refusing 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
X400107BKPMRF400backup mirror refused before it copied anything: {reason}
X400116RLBKTO400rollback requires --to backup id or relative time
X400134BKPRTM400restore runtime {runtime} is not a runtime, the runtimes are docker, podman, incus and apple
X400146BKPWRT400restic mounts are read-only, use shc backup mount without --writable
X400258BKPSEL400{file} sets {key}:, which backup.yaml does not take; a group backup reads one member by its converter’s from:
X400402BKPPTH400backup 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
X400402BKPRUN400backup already running for stack {stack_name}, held by {holder}
X400403BKPFAL400backup failed {op} {error}
X400404RSTRFL400restore failed {op} {error}
X400405BKPINV400backup {backup_id} is invalid {op} {error}
X400407BKPIDR400at least one backup_id is required
X400415IMPFAL400import failed {op} {error}
X400416IMPCNT400import of {path} refused, the archive’s container is not sound, {evidence}: {remedy}
X400417BKPOUT400{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
X400426RSTRWP400backup.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}
X400430BKPMUT400exactly one of --id, --file, or --before is required
X400431BKPCDP400cannot use both --all-connected and --with-dependants
X400432BKPCRF400backup.repo {repo} names a connection but is not {form}, with a bucket of 3 to 63 lowercase letters, digits, dots and hyphens
X400433BKPGRF400cannot use --file with graph flags
X400434BKPIDS400at least one --backup id or -b is required
X400435BKPMTI400one of --id or --file is required
X400437BKPSTK400--stack required
X400438BKPSTH400SHC_STATE_HOME not set
X400440RCVPRT400recover plan port conflict {detail}
X400441BKPSGO400cannot combine -s/--stack with --with-connected/--with-dependants, a group restore targets each member’s own recorded deployment
X400442BKPHLD400backup of {stack_name} aborted, the freeze reached its hold deadline after {held_seconds}s and --fail forbids stopping the deployment to finish the capture
X400442RSTPTH400restore --paths named {unknown} which this archive does not carry, it carries {subjects}, nothing was stopped or replayed
X400443BKPNDD400nothing 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
X400443RSTCKM400backup {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
X400444BKPNVE400nothing 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
X400449RCVOLD400{flag} {value} is the retired spelling, write {flag} {now}
X400486BKPNRP400backup 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
X400487BKPPAT400backup 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
X400489BKPART400invalid hook_artifacts entry {artifact}; use a literal relative mount/path
X400491BKPFLR400backup create --{flag} was removed in 0.1.28: {why}. Drop it from the command
X400494RLCARG400backup relocate: {detail}
X400719BKPASX400backup restore --as restores a backup id as a new deployment and cannot be combined with --{flag}
X400800BKNOMN400invalid backup archive, missing manifest.json {error}
X400801BKINVJ400corrupt manifest {error}
X400802BKGCNF400consistency id mismatch, expected {expected}, found {mismatched}
X400803BKGINV400invalid .bkg file {op} {error}
X400804BKGEMT400.bkg file contains no backups
X400805EXPFAL400export from restic failed {reason}
X400806IMPFAL400import to restic failed {reason}
X400817MTSNWR400mount session {session_id} is not writable
X400818MTSPTH400invalid path {path} in mount session {error}
X400822MTSSRC400invalid mount source {source} {detail}
X400830MTSPRC400restic mount subprocess failed to start {detail}
X400837MTSDNG400refusing 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
X400844MTSLOC400backup {backup_id} of {deployment} cannot be restic-mounted: location {location} is not a restic repository and snapshot; .bak files cannot be restic-mounted
X400850BKMARH400invalid AR archive header
X400851BKMARS400invalid AR header size {size}
X400852BKMART400invalid AR header terminator
X400853BKMARZ400AR member {name} is {size} bytes, past the {limit} the container size field can express
X400854BKMIDX400empty backup index
X400860VLMREQ400invalid volume mount request {detail}
X400862PDMREQ400pod mount request requires a container id
X400865VOLSOV400restore storage override {storage} cannot be honored {reason}
X400867RSTEMPT400restore verification failed for mount {mount}, backup had data but the restored volume is empty, replay did not land
X400868RSTJOBM400restore verification failed for job {job} target mount {mount}, the converter snapshot had data but the target is empty, restore job did not land it
X400869RSTMISM400restore verification failed for backup {backup_id}, {detail}
X400870CNVIMG400backup job {name} image template {template} rendered empty, the deployment vars context could not resolve it, refusing to invoke docker
X400871VLTRSF400vault secrets not restored for {tenant}/{stack_name}/{environment}, the deployment’s startup credentials are missing, {detail}
X400872RSTVSRC400restore verification for {mount} could not read the staged snapshot, {detail}, whether the replay landed cannot be proven
X400873RSTWIPE400restore emptied mount {mount} and could not measure what replaced it, {detail}, the replay cannot be proven to have refilled what the wipe removed
X400874RSTJREF400restore job {job} refused, {detail}, the restore is stopped rather than reported complete over data it did not land
X400875RSTSTGP400restore 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
X400876RSTNOFB400restore 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}
X400879RSTDUR400restore of {backup_id} failed after the bring-up, {detail}
X400880EXPNAT400native export is not available for app {app}, {detail}
X400881EXPCMP400native export of {backup_id} cannot locate the engine archive holding its database, {detail}
X400882EXPDBS400native export needs a per-database dump of {database} and engine archive {engine_backup_id} carries none, {detail}
X400884BKPRND400backup job {name} was not run, it could not be rendered against the deployment’s render context: {detail}
X400885RSTLNK400restore refuses to write {entry} through a symbolic link
X400886RSTUNR400restore of {stack} refused, {artifacts} {why}, so the restore would report complete without that data
X400890VLMTTL400mount lease {ttl} is not between one second and {max}
X400895RSTHLD400restore cannot safely replay {entry}, {detail}
X400898RSTMAP400restore of {deployment} refused before anything was stopped: --map {from}={to} {reason}
X400951VLFPTH400path {path} refused, {reason}
X400955BKPSPR400backup.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
X400956VLFKND400{path} is {what}
X400959VLFROT400{op} of {path} refused, it is the volume itself
X400961VLFREQ400missing {what}
X400966BKPSKR400backup.secrets_key takes a secret reference such as ref+vault://backup/secrets-key, never the key itself
X400972INVCRN400invalid cron expression {detail}
X400973RLBKTM400invalid time format {time}
X401946BKPIRL401backup repository {repo} named at {scope} is locked: {detail}
X404050OPRNOF404operation {operation_id} not found
X404400BKPNOF404backup {backup_id} not found
X404401STKNOF404stack {stack_name} not found
X404403BKFNOF404backup file not found {path}
X404410BKPCST404no backups found with consistency_id {consistency_id}
X404413RSTNOF404restic snapshot {snapshot_id} not found
X404415REPONF404repository not found {repo}
X404424RSTGON404restic repository {repo} is gone: {detail}
X404439BKPNOB404no backups found
X404446BKPNSC404backup 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
X404447BKPGSC404{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
X404800RLBKNF404no backup found for stack {stack_name} before {before}
X404816MTSNOF404mount session {session_id} not found
X404819MTSFNF404file {path} not found in mount session
X404831MTSNOH404no active mount handle for {handle}
X404887BKPREP404this node holds no replica of deployment {deployment}, so backup job {job_name} has no project to run in
X404951BKPOTN404backup restore target tenant {tenant} not found
X404952BKPONF404orphan backup {backup_id} not found
X404952VLFNOF404{path} is not in the volume
X404953BKPIRN404orphan backup {backup_id} is in a repository no backup.repo names now: run shc backup orphan scan
X404954BKPFNO404backup file {path} is not on {node}, the node that reads it
X404957VLFNLO404volume {volume} is not laid out on this node
X408419RSTTMO408restic operation timed out after {elapsed}, on {limit}
X408821MTSEXP408mount session {session_id} has expired
X409054OPRNCN409operation {operation_id}, the {kind} of {stack_name}, cannot be cancelled: {reason}
X409080VFYUNP409backup {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
X409104BKPRUN409operation {operation} already holds this backup scope, wait with shc operation follow {operation} before retrying
X409107BKPMRR409a backup mirror is already running on this node
X409409BKPCST409backups have different consistency ids and cannot be grouped
X409445BKPNVR409no 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
X409447BKPNAM409{name} names more than one backup: {backups}. Name the deployment with -s, or give the backup’s ID
X409470BKPKLK409another backup key rotation or removal is in progress ({error}); nothing was changed, try again when it finishes
X409487BKPCRS409deployment {stack} cannot restore a crash image; start it and back it up again
X409488BKPSTR409deployment {stack} was not confirmed stopped for the whole capture, the archive was discarded; back it up again
X409495RLCREF409backup relocate refused, nothing was rewritten: {repo} {detail}
X409499BKPHLD409mount {mount} is on node {node}, which is not held for this stopped backup
X409527CNVLIV409backup converter {name} refused after the scale window, {detail}
X409658BKPVDT409mount {mount} is on the volume {volume}, which no node holds and which keeps what it was last written, and {reason}
X409691CNVNDT409backup of {stack_name} failed: converter {converter} found no data to capture and the capture’s frozen copy holds none either, {detail}
X409716BKPRNE409deployment {tenant}/{stack}/{environment} already exists, so no backup is restored as a new deployment under that name
X409732BKPELS409backup {backup_id} is in {repo} on node {node}‘s own disk, which this node cannot read: {detail}
X409839MTSCKS409derived backup {backup_id} failed checksum verification: recorded {want}, recomputed {got}
X409843MTSDUP409backup {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
X409866HBDCON409host bind restore conflict for {path}, {detail}
X409867HBDATT409host bind restore refused to wipe {path} for stack {stack}, {detail}
X409876RSTHKR409restore of {deployment} refused by its pre_restore hook before anything was stopped or written, {reason}
X409884VOLPER409backup 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>
X409886VLMNMT409volume {volume} is attached to this node but nothing is mounted at {path}, so there is none of its data to show
X409888BKPENT409backup job {job_name} cannot run as compose service {service} in replica project {project}, that name is one of the replica’s entries
X409889BKPKEY409backup 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
X409890RSTFRN409restore 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}
X409891RSTNRH409restore 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
X409892RSTORN409restore of {deployment} refused: pod {pod} ordinal {ordinal} runs on node {node}, and its restore could not be routed there
X409893BKPOHN409{operation} of {deployment} refused: {mount} is the directory of no group member a replica on this node holds
X409894BKPCLN409backup {backup_id} is kept, a clone operation still needs its archive or the clone state that would free it cannot be read, {reason}
X409895BKPGRP409backup of {deployment} refused: it reads one member of group {group} and none can be read, {reason}
X409896VLMHLD409volume {volume} is held by {holder}, so it cannot be mounted on this node
X409897RSTMNT409restore 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 =
X409898RSTORD409restore of {deployment} refused: the archive carries pod {pod} ordinal {ordinal}, which is no group member of the target
X409899BKPRPL409backup of {deployment} refused: it cannot capture the data of replica {replica} on node {node}, {why}
X409948BKPOLK409backup {backup_id} is locked: it needs {needs} at {scope}
X409953VLFEXI409{path} is already in the volume and was left as it is, replace it with overwrite
X409954BKPKFE409not 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
X409954VLFDTC409volume {volume} is detached, so no node holds its files
X409955VLFNEM409folder {path} is not empty, delete it with recursive to remove what is in it
X409958BKPSNO409backup {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
X409958VLFMNY409volume {volume} is laid out on nodes {nodes}, name one of them with node
X413425RSTOUT413restic {command} printed more than {limit} bytes of metadata; command stopped
X416962VLFRNG416range {range} names no bytes of a {size}-byte file
X499052OPRCNL499operation {operation_id}, the {kind} of {stack_name}, was cancelled by {actor}
X500042RCVFAL500recovery failed for {stack_name}, {op} {error}
X500045RCVCYC500recover deploy scheduler dependency cycle among {stacks}
X500047RSTJOB500restore {phase} job failed {error}
X500051SSEFAL500sse stream failed {detail}
X500065BKPQAB500backup capture aborted for {stack_name}, consistency-expected pause failed {error}
X500160BKPLNG500backup work failed for {items}, correct the reported failures before retrying those items
X500173RLBSTP500the rollback of {stack} failed in {step}, which left the deployment {state}
X500204BKSCSK500scheduled 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
X500205BKSCTO500scheduled 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
X500380BKPATM500backup of {stack_name} read nothing: its application quiesced for one atomic snapshot and {detail}
X500410RSTERR500restic command failed {detail}
X500411EXPFIL500export failed {op} {error}
X500412RSTLCK500restic repository is locked {detail}
X500414RSTPAS500restic authentication failed {detail}
X500415RSTBKN500failed to connect to restic backend {detail}
X500416RSTENV500backup credential {key} did not resolve, {detail}
X500417RSTPRN500restic prune failed {detail}
X500418RSTRST500restic restore failed {detail}
X500420CACHSY500failed to sync backup cache {detail}
X500421RSTINT500restic {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
X500430BKPCMR500read compose failed {error}
X500431BKPMKD500mkdir backup dir failed {error}
X500432BKPSNV500snapshot volumes failed {op} {error}
X500433BKPUNT500untar failed {error}
X500434BKPCUP500post-restore docker compose up failed {error}
X500435BKPSNS500snapshot {volume} failed {error}
X500436BKPGSF500refusing to restore the consistency group {consistency_id}: {stack} cannot be protected first: {reason}. Nothing has been restored. {kept}
X500437BKPRPB500refusing to roll {stack} back: {reason}. Nothing has been changed
X500437BKPVRS500restore {volume} failed {error}
X500438RSTRLX500restore could not loosen mount {mount} for the replay, {detail}
X500439BKPNDR500no backups dir for the deployment, {error}
X500440BKPDKR500docker {args} failed {error} {output}
X500440BKPSDR500docker sidecar operation failed {error} {stderr}
X500441BKPRSC500restic exited {error}
X500442BKPSQL500{operation} failed {error}
X500443RSTPBK500restore could not put back the modes it loosened on mount {mount}, {detail}
X500444BKPDCL500backup daemon client {op} failed {error}
X500446BKPDHT500backup daemon response status {http_status} {error}
X500452BKPFRZ500backup of {stack_name} may have left the deployment paused, {detail}
X500452BKPTHD500backup of {stack_name} left {replicas} down: it stopped at the thaw and did not start again, start it
X500453BKPSTF500backup stop/start of {stack_name} did not complete, {detail}
X500454BKPKRT500backup key rotation failed {detail}
X500455BKPKRP500backup 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
X500456BKPKPT500backup key rotation left {survivors} still able to open their repository, {detail}
X500457BKPKST500backup key could not be recorded {detail}
X500458BKPHOM500{job} on service {service} reported success but was oom-killed inside the container {detail}
X500458BKPQJL500backup 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}
X500459BKPUNQ500backup of {stack_name} could not un-quiesce the deployment, it may still be read-only, {detail}
X500460BKPEOM500{job} on service {service} was oom-killed inside the container {detail}
X500460BKPPJL500backup 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}
X500465BKPCRP500backup of {stack_name} has data subjects with no bytes behind them: {subjects}
X500466BKPPLC500backup 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
X500467BKPHKF500backup hook {phase} of {stack_name} did not complete, so whatever it was responsible for staging is not in this archive: {detail}
X500468BKPQAW500backup 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
X500469BKPABN500backup {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
X500469BKPQSK500backup 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
X500470BKPCOV500backup 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
X500472BKPUNV500backup {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
X500473BKPNOA500backup {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
X500474BKPSRQ500scheduled 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
X500475BKPUNU500could not {op} the unusable stamp for {stack}: {reason}
X500476BKPUNS500refusing 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
X500477RSTJNL500restore of {stack} refused before anything was stopped or written: its restore journal could not be written, {reason}
X500478BKPPRO500backup protection audit ({check}): {finding}. shc doctor run --category backup reproduces this
X500479BKPSTM500backup {backup_id} was restored, but no backup row {backup_id} in tenant {tenant} took its restored_at
X500480BKPNSL500backup {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
X500497RLCFAL500backup relocate failed at {step}: {detail}; rows already rewritten stay rewritten, run it again to finish
X500718BKPRNL500restoring backup {backup_id} as {stack} failed and left {tenant}/{stack}/{environment} installed, shc uninstall {stack} -t {tenant} -e {environment} -y removes it: {error}
X500793CNVACC500converter {converter} of {stack} cannot inspect expected input {entry}: {detail}
X500820MTSOPF500mount operation failed {op} {error}
X500823MTSCMT500mount commit failed {op} {error}
X500833MTSUMT500umount failed for {path} {detail}
X500834MTSDEP500fuse mount prerequisite {binary} is not installed on this node, {hint}
X500835MTSRDY500restic mount at {path} never became ready, {detail}
X500836MTSVIS500mount at {path} is not browsable by the caller, {detail}
X500837BKPSCP500{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}
X500838MTSMAT500materialising the edited tree failed {op} {error}
X500846MTSPAS500backup mount for {deployment} refused: no restic password configured for this deployment
X500847MTSREP500backup mount for {deployment} refused: no restic repository resolved for this deployment
X500848BKPDBD500backup could not dump database {database} of plug {plug} on {provider}, {error}
X500861VLMRMT500remote volume on node {node} could not be exposed {error}
X500862VOLCAP500volume backed capture failed for {mount} on node {node} {reason}
X500863PDMSNP500container filesystem snapshot failed {detail} {error}
X500864VOLPRV500provision before restore failed for {mount} provider {provider} {reason}
X500883VOLDIR500volume 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
X500886RSTNFN500restore of {deployment} replayed its data and did not finish, {step} failed, {detail}
X500891VLMBND500could not bind {source} at {path}, {detail}
X500897VLMATT500volume {volume} is detached and could not be attached to {node} to mount it, {reason}
X500934RLBKPR500failed 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
X500935RLBKRS500rollback failed during restore of {stack_name} {error}
X500960VLFIOE500{op} {path} failed: {error}
X501400UNGFIL501ungroup endpoint requires file upload
X501832MTSPLT501fuse mount unsupported on platform {platform}
X502107BKPMRI502backup mirror incomplete: {repos}; each copy is still a valid, older repository
X502112BKSFWD502backup schedule leader relay failed for {op}, {detail} {error}, nothing was changed; retry, or run the command on the leader node
X502300RCVSHP502recover of {stacks} lands on node {node} and could not run there: {reason}
X502496RLCOPN502backup relocate could not open {repo} with the configured backup credentials, nothing was rewritten: {detail}
X503053OPRLKP503operation {operation_id} is not on this node and not every other node could be asked for it, {detail}, ask again
X503479BKPROW503backup {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
X503489BKPDMN503shc 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
X503890BKPREM503backup job {job_name} in project {project} was interrupted, the replica it ran in was removed from this node, retry the job
X503941BKPINW503the orphan index is not wired in this process: no repository list resolves here
X503947BKPIRU503backup repository {repo} named at {scope} is unreachable: {detail}
X503956BKPIRF503{count} could not be read: {repos}
X507295RCVROM507recover 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
X507299RCVNRM507recover 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
X507460BKPSPC507refusing 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
X507559BKPPSP507refusing 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
X507826MTSSPC507not 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

Source: modules/branding
Count: 14

CodeHTTPMessage template
X200880BRDUNB200branding edge {plug} resolves unbranded with {reason}
X400880BRDNAM400invalid brand name {name} must match {pattern}
X400881BRDFIL400invalid branding file {file} with {reason}
X400882BRDSIZ400branding file {file} too large {size} bytes exceeds {limit}
X400883BRDENC400branding file {file} is not valid base64 {error}
X403880BRDENT403brand 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
X403881BRDWLB403brand {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
X403882BRDDEN403the s3 connection {connection} rejected the brand store credentials with {detail}
X404881BRDNOF404brand {name} not found
X404882BRDCON404branding requires an estate connection with an s3 provider and {which} is visible to the master tenant
X404883BRDBKT404branding bucket {bucket} does not exist on the s3 connection {connection}
X409881BRDAMB409multiple estate s3 connections could hold the brand store {names} and branding will not guess
X502880BRDOBJ502brand store S3 operation failed while {op} with {detail}
X503880BRDNAV503branding not available with {reason}

Source: modules/ca/caapi, modules/ca
Count: 24

CodeHTTPMessage template
X200106CAESCD200best-effort delete of pfSense-side CA copy failed for tenant {tenant} ref {ref}, remove it manually
X200107CAKEYT200keyType is advisory for key-escrow and was ignored for tenant {tenant} so the backend chose the algorithm
X200109CAINTX200tenant CA {tenant} intermediate nears expiry on signer connection {conn}, reprovision before it lapses
X200110CARPRV200tenant {tenant} CA re-provisioned, clients trusting the old root must install the new one
X200114GRTRMT200global root re-minted to recover a keyless trust anchor, clients trusting the old root must install the new one
X200118CASPLT200tenant {tenant} CA intermediate key did not pair with its certificate, re-derived it from the global root
X400102CAMANL400manual CA import invalid {op} {error}
X400111CARPSR400invalid reprovision source {detail}
X400113CARSVD400tenant ca name {name} is reserved for a system ca
X404112CACRTN404no certificate found for name {name}
X409112CARPRN409operation {operation} already reprovisions the CA of tenant {tenant}, wait with shc operation follow {operation} before retrying
X500096CAGENM500failed to mint CA material {op} {error}
X500097CALEAF500failed to sign leaf certificate {op} {error}
X500098CASTOR500failed to store CA for tenant {tenant} {op} {error}
X500099CALOAD500failed to load CA for tenant {tenant} {op} {error}
X500100CAVLTU500vault is not available so CA private keys cannot be stored or read
X500103CASGNU500ca-signer backend not available for tenant {tenant} connection {conn}
X500104CASIGN500failed to csr-sign intermediate for tenant {tenant} {op} {error}
X500105CAESCR500key-escrow CA operation failed {op} {error}
X500108CAWEDG500tenant CA {tenant} is wedged with keys absent for provenance {provenance}, run shc ca reprovision
X500175CARPLN500the reprovision of the CA of tenant {tenant} stopped on an internal fault {detail}
X500176CARPST500the reprovision of the CA of tenant {tenant} failed in {phase} after {done}
X503090GRTNRD503global root not ready {op} {error}
X503113CANDNI503the per-node leaf listing is not wired in this process, run it against a daemon that has joined its cluster

Source: modules/capabilities
Count: 2

CodeHTTPMessage template
X500211CAPFTC500capabilities no fetcher provided
X503940CAPDIS503{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.

Source: modules/capacity
Count: 10

CodeHTTPMessage template
X200195CAPROP200idle autoscale node {node} was cordoned, and a pending replica fits it, so it is returned to service
X200196CAPUNC200autoscale cordoned node {node} and did not drain it, and it {why}, so it is returned to service
X200197CAPDRN200autoscale node {node} has held no replica or volume since {since}, past the {cooldown} cooldown, so it is cordoned and drained
X409193CAPRFS409{deployment} is pending, and run again it was refused: {refusal}; it stays pending and runs again each pass, uninstall it to cancel it
X409195CAPDSP409{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
X409196CAPLFT409node {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
X409197CAPPND409{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
X500199CAPSTO500capacity store {op} failed{error}
X503198CAPNST503the capacity store is not wired on this daemon
X503199CAPDRF503the {step} of idle autoscale node {node} failed: {error}; the next capacity tick tries again

Source: modules/catalog
Count: 5

CodeHTTPMessage template
X400272INTOGN400--host is gone, write --into {value}
X400960CATINP400catalog invalid input {reason}
X404960CATNOF404catalog application {application} not found
X409960CATAMB409catalog application {application} is ambiguous across repos {repos} with digests {digests}
X500960CATOPF500catalog {operation} failed

Source: modules/catalogbuild
Count: 2

CodeHTTPMessage template
X400611CATBARG400invalid catalog build request {reason}
X500611CATBLD500catalog build failed {reason}

Source: modules/certbroker
Count: 8

CodeHTTPMessage template
X200473CRTSTG200delivered {delivered} certificate for host {host} while its resolver requests {requested}, it will not validate against a public trust store
X200477CRTROT200rotated delivered certificate for host {host} to serial {serial} class {class} reloading {reloaded} services
X400470CRTDCL400invalid certs declaration in app {app} {detail}
X403471CRTSCP403deployment {deployment} is not granted host {host}
X404472CRTHST404no delivered certificate material for host {host} in tenant {tenant}
X500474CRTSRC500certificate source failed {op} {error}
X501476CRTNIW501cert-delivery broker is not wired, see docs/proposals/2026-08-06-cert-delivery-broker.md
X503475CRTPND503certificate issuance pending for host {host}

Source: cli
Count: 3

CodeHTTPMessage template
X403219HUDREG403cannot read {path} for the active cluster {cluster}, make it readable by this user or run shc ctx --reset
X404217HUDEDT404no editor found, set $EDITOR
X501216HUDTUI501this build carries no hud tui, rebuild with make build

Source: modules/clone
Count: 88

CodeHTTPMessage template
X200607CLNSRV200the 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
X200628CLNARC200the 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
X200652CLNSCV200could not remove scratch volume {volume} of {tenant}/{environment}/{stack} on node {node}{error}
X200656CLNMVK200the 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}
X200664CLNRKP200replica 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
X200672CLNRAS200replica project {project}: the target’s copy from shc.move-operation={operation} {action} at {path}; it is kept and nothing deletes it
X400600CLNCON400deployment {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
X400602CLNCAN400{operation} cancelled
X400608CLNRNT400invalid runtime {runtime}, expected one of docker, podman, incus or apple
X400620CLNDSC400a move off a dead node is not possible, {reason}
X400626CLNBIG400the 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
X400630CLNXSC400refusing 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
X400647CLNNOD400a clone does not name a node ({node}), the copy is placed by the source’s rules; add one with --where node={node}
X400649CLNOLD400--rename {value} is the retired spelling, write --rename {now}
X404600CLNSRC404stack {name} not found
X404607CLNNOD404node {node} not found
X409600CLNCOL409stack {name} already exists in {tenant_name}/{environment}
X409601CLNAUF409could not generate unique name for {stack_name} after 100 attempts
X409606CLNSRB409refusing 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
X409615CLNCAP409refusing to {verb} {stack}: replica {replica} on node {node} holds data the backup cannot capture, {why}; the source is untouched and nothing was written
X409617CLNDND409node {node} is not dead, its cluster_state is {state} and not unreachable
X409618CLNDPR409node {node} is not dead, it answered a probe at {addr}
X409621CLNDUR409the 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
X409623CLNPRO409teardown refused, deployment {tenant}/{stack} is protected, run shc unprotect {stack} first
X409624CLNPRU409teardown refused, cannot determine whether {tenant}/{stack} is protected ({reason}), refusing rather than risk destroying protected data
X409639CLNRLK409refusing to relocate {deployment}: a relocation on {node} {holds}, and nothing has been stopped or moved; {next}
X409640CLNMNT409{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
X409641CLNSTL409refusing 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
X409642CLNRLL409the 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
X409643CLNUNR409the 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
X409645CLNOCC409{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
X409646CLNRLF409the 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
X409647RELDUR409deployment {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
X409648RELBKP409deployment {name} cannot relocate, it has no backup to restore its durable volumes [{volumes}] from
X409650RELSHR409deployment {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
X409651RELCON409deployment {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 -i ! or leave {name} on {node}
X409652CLNDIR409backup of {stack}/{environment} cannot run, {detail}; nodes asked: {nodes}
X409654CLNRNR409the copy {deployment} runs and its rules are not recorded: {why}; record them with shc constraint set --scope deployment on {deployment}
X409655CLNRLO409replica 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
X409657RELCNF409the 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
X409661CLNRST409replica project {project} cannot move: stop on {node} was not verified: {error}
X409662CLNRVO409replica project {project} cannot copy: target volume {volume} already exists
X409663CLNRMV409replica project {project} cannot move: {why}
X409665CLNDHL409{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
X409668CLNSRG409deployment {deployment} cannot move bring-up-first: {why}
X409669CLNCRT409{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
X409671CLNRWK409relocating {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
X409672CLNROW409relocating {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
X409673CLNRDY409relocating {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
X409674CLNWRT409relocating {name} moved {landed} and no member of {group} took its writer role back: {error}
X409675CLNRNC409{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 -i !, rename, then connect it to {target}
X409680CLNSTG409deployment {deployment} cannot move its storage: {why}; nothing was stopped
X409682CLNDRP409refusing 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}
X409690CLNRBK409refusing to roll {operation_id} back, {reason}
X409692CLNFRC409deployment {deployment} moves to {to} only by copying {volumes}, which its storage does not follow; pass --force to copy them, nothing was stopped
X500601CLNROL500rollback failed {reason} {error}
X500602CLNBKP500backup failed during clone/move {op} {error}
X500603CLNRCV500recovery failed during clone/move {op} {error}
X500604CLNUNI500uninstall failed during move {reason} {error}
X500605CLNRNM500rename failed {op} {error}
X500609CLNRND500clone random suffix failed {error}
X500610CLNFAL500{operation} failed {error}
X500612CLNREQ500{operation} request failed for {source}
X500613CLNRPF500{operation} reported failure
X500614CLNDEG500refusing 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
X500614CLNNWR500{operation} service not wired
X500616CLNMOV500deployment move step failed {op} {error}
X500622CLNDMV500move off a dead node failed at {op} {error}
X500625CLNLND500move aborted before destroying the source, the recovery reported success but {reason}
X500626CLNHLT500move aborted before destroying the source, the target is not proven healthy, {reason}
X500627CLNSRV500the move failed and its rollback could not prove the source is serving again, {reason}
X500629CLNDST500refusing the destructive step of the move, {reason}
X500630CLNDAT500move aborted before destroying the source, the target’s data is not proven, {reason}
X500630CLNJRN500the move journal could not be {operation}: {detail} {error}
X500631CLNRCM500reclaim could not complete, {reason}
X500631CLNRSM500the interrupted move {operation_id} of {stack} was not resumed automatically, {reason}
X500632CLNRNF500the rename of {source} to {target} cannot be finished, {reason}
X500633CLNJNF500no interrupted operation {operation_id} is recorded on this node: {detail}
X500634CLNFWD500refusing to finish {operation_id} forward, {reason}
X500636CLNNAR500moving {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
X500637CLNARF500refusing 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
X500638CLNRBF500the roll-back {operation_id} of {stack} stopped at the {step} step and is kept, {reason}
X500639CLNUNS500relocating {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
X500647RELRST500deployment {name} is installed on {node} and restoring its durable volumes from backup {backup} failed, {error}, restore it with shc backup restore {backup}
X503181CLNRUL503a rule change that relocates needs the daemon’s fence store to place the move, and none is wired here
X503640CLNRLU503the relocation lease on {deployment} is unavailable: {reason}
X503644CLNPLC503refusing a move planned by {planner}: this node cannot check that the plan still stands, and nothing has been stopped or moved
X507632CLNSPC507refusing 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

Source: modules/cluster/commands, modules/cluster
Count: 121

CodeHTTPMessage template
X200030JNSELF200enroll for {node} resolved the joiner’s own raft address {raft_addr} as its join address, dropping it, this node cannot see the cluster leader
X200031VOTUNK200voter grant ledger unreadable while enrolling {node}, joining as a non-voter, which the suffrage pass promotes if the voter set needs it {error}
X200032TKNREL200could not release the bootstrap token after a failed enroll of {node}, it stays consumed and the retry needs a freshly minted token {error}
X200033CAPOVR200enrolling {node} left the estate over its licensed {limit}, holding {have} against {cap}, concurrent joins are measured against the roster as it stood before them
X200034CAPREL200could 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}
X200035NODNMR200node name {name} was claimed by a simultaneous enroll, retrying with the next free suffix
X200036CLSOVC200the 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
X200044CRTCHK200cluster cert rotation check failed {op} {error}
X200047CLSDLF200{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
X200048JNSTOR200store tier plan unreadable while enrolling {node}, joining as a store replica, which the tier pass moves to client if the plan says so {error}
X200166LVRMVD200node {name} ({id}) was removed from the cluster by another node: its cluster services and deployment containers stopped and its membership state moved to {archive}
X200216CLSSUC200suffrage {kind} of {node} done: {steps}
X200218CLSSTC200store 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
X200941CRTRNW200internal api mtls leaf renewed for {node} valid until {not_after} via {via}
X200942CRTSGN200cluster ca signed an internal api mtls leaf for {node} valid until {not_after}
X200948CRTRLD200internal api mtls leaf reload failed {error}
X400017NODDEP400node {name} is still named by {count} deployment rows: {deployments}; {basis}. {remedy}
X400021ALRCLS400this 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
X400022INVTKN400invalid or expired join token {reason} {error}
X400042VLTLKD400vault is locked, unlock with shc vault then re-run shc init
X400064VLTPWS400vault master password must be at least {min} characters
X400136STRROL400store role {role} is none of voter, replica or client
X400270INGHST400--host is gone, write --ingress-host {value}
X400278JNSCHM400join endpoint {endpoint} is not https, the bootstrap token is only sent to the cluster’s HTTPS entrypoint
X400291NODRSV400node name {name} is reserved, it is the name on the cluster’s join certificate
X400292NODDNS400node name {name} is too long, its cluster dns label {label} is over {limit} characters
X400384FBROLD400{end} is the retired spelling, write {now}
X400400CLSDRN400invalid drain request for node {node}
X400401CLSDRP400drain 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
X400402CLSDRB400this 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
X400421CLSCRD400invalid {verb} request for node {node}
X400422CLSRUN400runtime {runtime} is not supported on the new line; use docker, podman, incus or apple
X400423CLSDRM400drain 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 -c deploy.disruption=rolling, drain a different node, or re-run with --force to accept the disruption deliberately, nothing was changed, the node is still schedulable
X400589MSHMAC400mesh client up runs on macOS
X400591MSHSUD400mesh client cannot tell which operator runs it, {reason}
X400593MSHPKY400mesh client private key does not parse
X400612INICFR400--connection-file {file} could not be read, {error}
X400613INICFD400--connection-file {file} {problem}
X400614INICON400connection {name} from {file} was not made, {error}
X400615INISTO400--storage {name} is not a volume connection, the volume connections are {have}
X400616INIREP400--repo {value} {problem}
X401022TKNCNS401bootstrap token already consumed for node {node_name}
X401023TKNEXP401bootstrap token expired for node {node_name}
X401047CRTIDM401cert rotation rejected, caller identity does not match any registered node {reason} {node}
X403003LDRNLY403operation requires the cluster leader, current leader is {leader}
X403092ENRSIP403enrollment rejected, claimed physical_ip {claimed} does not match connection source {source}
X403283CLSPSM403peer status refused: {caller} is not a node of this node’s signed membership table
X403285ENRNAT403enrollment 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
X403590MSHCSU403mesh client up needs root to open a utun, run it with sudo
X403991LVEEEO403leaving a cluster requires SHC EE, this binary carries no multi-node leave orchestrator
X404020CLSNOF404cluster node {name} not found
X404024CLSLOG404no logs for {service} on {node}, {path} is not there and the journal of unit {unit} has no entries{error}
X404028NODNOF404node {name} not found in cluster
X404201CLSNNF404cluster member {name} not found in raft membership
X408400CLSDRT408drain timed out waiting for deployments to clear
X408422CLSDRH408drain timed out waiting for deployments to clear, {held} is still on the node
X409013STRVOT409{node} is outside the control plane, so it cannot be pinned a voter
X409025LVDEPS409cannot leave, this node still hosts {count} deployments named {deployments}; {remedy}
X409029CLSGEN409refusing 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
X409166LVRMNM409a removal notice for node {notice} reached node {local}, nothing was stopped
X409200CLSQUR409refusing to demote, {voters_after}/{required} voters would remain
X409201CLSRMQ409refusing to remove voter, {voters_after}/{required} voters would remain
X409202CLSRMR409refusing to remove voter, {reachable_after}/{required} reachable voters would remain
X409204NODNMC409could 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
X409206CLSRBN409cannot 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
X409207NODLST409{node} is the only node of this cluster, and a cluster cannot forget its last node, nothing was changed
X409216CLSSUB409cannot remove {node} while another suffrage change is in flight, retry once shc cluster status shows none
X409400CLSDRD409node {node} is already drained
X409400CLSREC409force-leader recovery already in progress
X409403CLSPRT409refusing 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
X409405CLSLDR409refusing force-leader recovery, {leader} answers as the cluster’s leader, so quorum is not lost and there is nothing to recover
X409407CLSRVU409refusing force-leader recovery, its split-brain safety gate could not be evaluated ({reason}), so this node cannot prove the other voters are dead
X409408CLSCRD409refusing to {verb} {node}, its availability is {state} and only {use_instead} may change that
X409410CLSDRS409the drain of {node} was stopped by {by} after {moved} of {planned} had moved, and what moved stays where it went
X409411CLSASH409autoscale 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
X409427CLSDTA409drain 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
X409588MSHNGW409no live gateway is on mesh0, an operator client reaches the cluster through one
X500008NODREM500failed to remove node {op} {error}
X500021CLSINT500cluster internal error {op} {error}
X500022CERGEN500failed to generate certificate {op} {error}
X500023JNFAIL500failed to join cluster {op} {error}
X500024LVFAIL500failed to leave cluster {reason} {error}
X500027RMLVFL500failed to request remote leave for node {name} {reason} {error}
X500028TKNGEN500failed to generate join token {op} {error}
X500046CRTCAU500cert rotation failed cluster ca unavailable {op} {error}
X500047CACSTR500cluster ca store {op} {error}
X500048CACUNP500cluster CA not provisioned {reason}
X500049CAROTF500cluster CA rotation {op} {error}
X500050CCALOS500cluster 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 /shc.db, the promote ingest’s source, or else from a backup {reason}
X500051GRROTF500global root rotation {op} {error}
X500060CRTNLF500internal cert renew failed on a follower and there is no local fallback, the cluster leader is the only signer {op} {error}
X500201CLSREC500force-leader recovery failed {op} {error}
X500202CLSPRO500promote to voter failed {error}
X500203CLSDEM500demote from voter failed {error}
X500207CLSRBS500promote-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}
X500211RFTTLF500raft tls required by this cluster but node cert material is unavailable, re-run shc node join --force {error}
X500216CLSSUF500suffrage {kind} of {node} failed at step {step}, the next pass retries {error}
X500400CLSDRO500drain failed for node {node}: {reason}{error}
X500406CLSDRP500drain 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}
X500407CLSDRJ500the 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
X500408CLSDRU500the 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
X500409CLSCRO500{verb} failed for node {node} {reason} {error}
X500592MSHPRC500mesh client peers refresh as the operator failed {error}, {stderr}
X500911RNDFAL500os entropy source unavailable {error}
X500912CRTATM500atomic cert write {step} {error}
X502277JNSIGN502the join answer from {endpoint} is not signed by the cluster the join token names, nothing in it was used, {detail}
X503021CLSQRM503cluster 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
X503022CLSUNO503cluster 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
X503070RCNDMN503daemon not reachable {error}
X503090CLSJNP503joiner {node} raft port {raft_addr} unreachable from leader, join cannot converge until reachable
X503091CCAJNW503joiner awaiting leader cluster CA {reason} {error}
X503093CRTLUN503internal cert renew deferred, cluster leadership not yet confirmed on this node {op}
X503200RFTTLW503raft 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}
X503218CLSSTH503store tier move of {node} to {role} held since {since}, {reason}, every later tier move waits until it ends
X503284CLSPSR503peer status unavailable: {reason}
X503425CLSDBU503drain 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
X503426JNRSTR503the enrol of {node} was cut by this node’s own restart, the join is tried again once the node is back
X503427CLSDRZ503drain of {node} moved nothing because {freeze}, {node} is still {availability}, drain it again once the freeze lifts
X503705CLSLGN503the logs of {node} were not read, the node was not reached {error}
X504207CLSRBT504promote-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
X504216CLSSUT504suffrage {kind} of {node} timed out after {timeout} waiting for raft to list it with its new suffrage, the next pass retries

Source: modules/clusterfs
Count: 10

CodeHTTPMessage template
X200675CFSTIK200clusterfs on node {node} did not build, it keeps serving its current revision: {error}
X200677CFSBLD200clusterfs build of revision {revision} on node {node} took {took} and {reads} store reads, outcome {outcome}: {sections}
X409670CFSMOV409clusterfs build at revision {from} discarded, the control plane moved to {to} while it rendered
X409681CFSWRS409clusterfs build discarded because the render wrote snapshot tables {tables} that its snapshot could not apply
X500668CFSRAM500clusterfs cannot render its secret sections on {root}: {error}
X500671CFSSEC500clusterfs section {section} failed to render, the node keeps its current revision: {error}
X500672CFSWRT500clusterfs {op} failed: {error}
X500674CFSREV500clusterfs revision counter {op} failed: {error}
X500676CFSPKY500clusterfs build refused: {path} holds a PEM private key, and a private key is never published into clusterfs
X503673CFSNOR503clusterfs 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

CodeHTTPMessage template
X500606SCNHELP500scan helper failed {reason}
X503675SCNDBR503scan database unavailable {reason}, run shc scan db update <archive>

Source: modules/collector
Count: 7

CodeHTTPMessage template
X500392COLEPH500export destination {endpoint} names no host
X500393COLEPP500export destination {endpoint} names no port and no scheme that implies one
X503120COLRCN503per-node collector reconcile failed at {step}, {reason}, retrying on the next sweep
X503121COLEXG503collector export is disabled by the license.offline policy, {posture}
X503122COLVMS503node 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
X503123COLREJ503the 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
X503126COLBRG503the engine’s answer carries no network configuration, {answer}

Source: modules/completion
Count: 2

CodeHTTPMessage template
X400009INVSHL400unsupported shell {shell}
X500700FILWRT500completion cannot write {path}, {err}

Source: modules/condition
Count: 3

CodeHTTPMessage template
X200936CNDUNK200{unknown} could not be evaluated: {summary}
X500936CNDOPF500condition {operation} failed
X500937CNDOPN500{open} open at {worst}: {summary}

Source: modules/config
Count: 21

CodeHTTPMessage template
X200051CFGSEA200config key {key} moved into the vault, its row now holds a reference
X400002VALINP400invalid input {detail}
X400028CFGCON400--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}
X400033CFGUNK400config key {path} is not a known configuration key, possible typo, value stored anyway
X400037CFGINR400config key {path} is stored but not in effect, {reason}
X400041INVSCP400invalid scope {scope}
X400043CFGUND400config key {path} is stored, but SHC cannot determine whether any component reads it
X400050CFGSTP400config key {path} can only be set in yaml config files
X400066CFGSCP400config key {path} is never read at {scope} scope, nothing would consult this row, set it at {readable} instead
X400067CFGVAL400config key {path} is never acted on with value {value}, the row would store and read back while changing nothing, accepted values are {accepted}
X400068CFGMIN400config key {path} is {value}, below {floor} at {floor_value}, {why}, so set it to at least {floor_value} or lower {floor} first
X400155CFGNRD400nothing in this version of shc reads config key {path}, the {section} section has no reader for it
X400831CFGOLD400config key {path} is gone, use {replacement}
X400905SCPREQ400{field} is required
X400949UNKSCP400unknown scope {scope}
X409016CFGPLN409config key {key} holds a credential in plain config, it moves into the vault when the vault unlocks
X409017CFGRSM409restored config keys {keys} refer to vault secrets this restore did not bring back, restore the backup’s secrets or set the keys again
X409072CFGOWN409config key {path} is owned by {command} and is state, not config, so --config-set will not write it, {invariant}
X409073CFGRTD409config key {path} is no longer configuration, {destination}
X500952CFGOVL500config overlay {op} failed {error}
X503018CFGVLT503config key {path} holds a credential and the vault that keeps it is locked, unlock the vault and set it again

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

CodeHTTPMessage template
X200464HLDUNSCOPED200s3 connection served its own unscoped credential to {tenant}/{app} at {endpoint}: no bucket scope was declared by the app or granted by the operator
X200485CFRKEP200cloudflare r2 revoke retained {what}, {reason}
X200488CFRUND200custom domain {domain} is attached to r2 bucket {bucket} but no grant declares it, left attached
X200917CONRET200connection {connection} retire record failed, {error}
X200920CONPRG200purged deferred credentials of {count} retired connections older than {ttl}
X200944DNSZOWN200zone {zone} is already managed by connection {other}, connection {name} leaves it out of its listed zones
X200945DNSZRFR200connection {name} zone list was not refreshed, {error}, its zones are kept as they were
X400446AWSCRD400connection is missing the access_key or secret_key admin credential
X400460HLDCRD400held s3 connection is missing its access_key or secret_key credential
X400461HLDRCH400s3 connection endpoint {endpoint} unreachable or credential rejected: {error}
X400462LLMCRD400held llm connection is missing its llm_endpoint or api_key credential
X400463LLMRCH400llm connection endpoint {endpoint} unreachable or credential rejected: {error}
X400464REGRCH400container registry {registry} unreachable or credential rejected: {error}
X400465REGCRD400docker-registry connection is missing its username or password credential
X400466HLDSCOPE400s3 {which} is not a valid scope document; it expects {“buckets”:[…]} or {“unscoped”:true}
X400467PFSCRD400pfsense connection is missing its endpoint or api_key credential
X400468PFSNFD400pfsense 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
X400469PFSREJ400pfsense 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
X400470PFSRCH400pfsense REST API v2 at {endpoint} unreachable: {error}
X400470SOSBUCKET400bucket name {bucket} is not a legal s3 bucket name and cannot be scoped
X400473PFSTLS400pfsense connection cred {field} is not a usable TLS pin: {error}
X400480CFRCRD400cloudflare connection is missing its token
X400481CFRACC400cloudflare token resolves {count} accounts, connect with --cred account_id= to pin one
X400483CFRZON400custom domain {domain} is under no zone this connection holds ({zones})
X400484CFRSCP400cloudflare r2 scope refused, {reason}
X400486CFRNAM400derived bucket name {name} is not a valid r2 bucket name: 3 to 63 characters of a-z, 0-9 and -
X400547CRDARG400--cred entry {position} {reason}; the forms are key=value, key=- and -, and a secret comes from the file --value-file names
X400548CRDSEC400credential {field} {why} and is never taken on the command line: pass it as --cred {field}=- --value-file or as a JSON object of fields with --value-file
X400549CRDDUP400credential {field} is given more than once; give each field in exactly one --cred entry or document
X400550CRDSRC400cannot read credentials from {source}: {reason}
X400551ZNEOLD400{flag} is gone, write {now}
X400552ZNEDUP400zone {zone} {reason}; name each zone once on --zone
X400555ZNECON400connect cannot remove zone {zone} with a trailing !; use connection zones, or pass --zone ! with the whole declared set
X400761CONENDPOINT400endpoint in credentials is refused, use --endpoint
X400771DNSPURREQ400dns connection with --zone requires --purpose public|private
X400901CONTYP400unknown connection type {type}
X400904CONCRD400connection type {type} requires credential {field}
X400906DNSZREQ400local DNS connection requires at least one --zone
X400908DNSCRED400dns connection {type} credentials failed to validate
X400912DNSPURP400dns connection purpose {purpose} is not public or private
X400913DNSAZPUB400refusing to auto-create dns zone {zone} on connection {connection}, only a connection declared --purpose private may mint a zone
X400914DNSOVP400dns connection type {type} answers only private clients on its overlay, purpose public refused, pass --purpose private
X400916CONBND400grant boundary for connection {connection} is not valid json
X400921CONMNT400connection {connection} failed to mint capability {capability}
X400940DNSZARG400zones 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
X400941DNSZVIS400zone {zone} is not visible to connection {name}‘s credentials, nothing was changed
X400942DNSNCP400connection {name} of type {type} has no dns provider, so it has no zones to update
X400946CONLOC400connection type {type} has no load balancer, --location binds only a proxy connection’s edge{cred}
X400947CONBKR400connection {connection} of type {type} cannot hold a backup repository, backup.repo names a connection of type s3
X400956CONLCP400--location {location} binds the edge to no node’s location: {why}
X403465HLDNOSCOPE403s3 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
X403468HLDCAP403app declared s3 buckets {declared} but the grant boundary permits only {boundary}; the intersection is empty
X403472PFSDNY403pfsense REST API v2 at {endpoint} refused this caller with HTTP 403: {reason}
X403473BCKCAP403backblaze application key lacks {capability}, required to {op}
X403488HLDPLUG403the app’s s3 plug addresses buckets {buckets} that the grant boundary does not permit; the boundary names {boundary}
X403910CONGRT403connection {connection} not granted capability {capability} for tenant {tenant}
X403922CONUNS403granting {capability} on connection {connection} serves the connection’s own unscoped credential; {remedy}
X403925CONBKT403the 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
X404475BCKBKT404backblaze bucket {bucket} is not visible to the connection key
X404902CONNOF404connection {name} not found
X404911CONMCP404connection type {type} cannot mint capability {capability}
X404915CONGNF404no grant for connection {connection} capability {capability} tenant {tenant}
X409260CONSEL409connection name {name} is a selector at {scope}
X409903CONUSE409connection {name} is in use by {where}
X409907DNSZTIE409zone {zone} already managed by connection {other}
X409914DNSZDROP409connection {name} owns zones {zones} that this connect leaves out; name them, or pass --zone ! to replace the whole set
X409923CONMID409connection {connection} credential was minted as capability {minted_capability}, cannot reuse it for capability {capability}; unbind the plug and bind it again
X409943DNSZRACE409connection {name} kept changing while its zones were being updated, nothing was written, run it again
X500448AWSMNT500aws s3 mint {step} failed {error}
X500449AWSIAM500aws iam mint {step} failed {error}
X500467HLDMINT500s3 scoped minter {provider} failed: {reason}
X500471SOSAPI500exoscale iam {op} failed: {reason}
X500472SOSOPER500exoscale iam {op} operation ended in state {state}
X500474BCKAPI500backblaze b2 {op} failed: {reason}
X500482CFRAPI500cloudflare r2 mint {step} failed {error}
X503905CONVLT503vault is not available, cannot store connection credentials
X503918DNSCHK503dns connection {type} could not be checked against its provider, try again in {after}: {reason}

Source: modules/console
Count: 4

CodeHTTPMessage template
X403522CONROLE403the console is an operator surface and this identity holds no access to it, it needs tenant:read or higher in this realm
X403523CONMANAGE403estate settings are a management surface and this identity holds no access to them, they need tenant:manage in this realm
X404559CONAPI404{path} is not an API route on this daemon
X503524CONAST503the 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

Source: modules/containerbroker
Count: 19

CodeHTTPMessage template
X200990CBRWRM200container broker could not prepare image {image} on pool {pool}: {reason}; the pull succeeded but starts may be slower
X200995CBRSWP200container broker could not remove everything it made for {caller} on this node{error}, the node tries again within a minute
X400984CBRREQ400container broker run request is missing required field {field}
X400991CBRVER400container broker answers Docker API versions {oldest} to {newest}, not {asked}
X403984CBREEO403the job-container broker requires SHC EE with the container_runtime entitlement for tenant {tenant}; community edition runs per-job containers through shell executors only
X403985CBROFF403the job-container broker is not enabled on this estate, opt in with shc config set container_broker.enabled true at global scope
X403987CBRFLD403container broker refuses field {field}
X403989CBRLIM403container broker refuses the container limit {limit}
X403994CBRFIT403container broker refuses the container: node {node} has no room for its {resource}
X403998CBRSLF403deployment {deployment} declares privileges.docker_socket: self, so its docker socket answers its own containers only, not {method} {path}
X403999CBRREP403{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
X404987CBROBJ404container broker object {object} was not found
X409993CBRSCK409container broker socket path {path} holds something that is not a socket, and it was left as it is
X409996CBRNET409container broker deployment {deployment} has no network of its own on this node for the container to join
X501992CBRNSV501container broker does not serve {method} {path}
X503986CBRNYI503the job-container broker executor is not implemented in this build, the run was fully authorised but nothing can execute it yet
X503988CBRENG503container broker cannot use the engine: {reason}
X503989CBRNOD503container broker deployment has no replica here, holder nodes: {nodes}
X503997CBRLAG503container 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

Source: core/addrblock
Count: 8

CodeHTTPMessage template
X400349ADRBLK400address block {block} is unusable, {reason}
X400450ADROVL400{overlaps} of address block {block}, {remedy}
X409450ADROVL409node {node}: {overlaps} of this cluster’s address block {block}, move the node off that network or make the cluster again with {remedy}
X409451ADRHLD409address block {block} overlaps {held}, a block this cluster already holds
X409455ADRNOD409address block {block} is not added, on node {node} {overlaps}
X409457ADRPOL409node {node}: {overlaps}, move the node off that network
X500453ADRCRV500this 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
X503456ADRASK503address block {block} is not added, node {node} could not be asked for its networks, {reason}

Source: core/api
Count: 16

CodeHTTPMessage template
X200067QRYTOK200query-string token used for auth on {path}, prefer the Authorization header
X200288STRBOT200this 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
X401000UNAUTH401internal api requires a cluster-ca client certificate or the internal token
X403038LICLCK403estate changes are locked, {reason}, refusing {path}, running workloads keep serving and backups stay downloadable, run shc license status for what to do
X404941APISCP404this peer is served one route on this listener, and {path} is not it
X404942APIMTH404this daemon serves no method {method}, the methods it serves are listed in its OpenAPI document at {openapi}
X409940APIGEN409this 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
X500040CMDFAL500command failed with exit {exit_code}, {command} {stderr}
X500079FSMKDR500mkdir failed at {path}, {detail}
X500083APILSN500listen {name} on {addr} failed, {error}
X500084APIUDS500listen unix {path} failed, {error}
X500085APICHM500chmod {path} failed, {error}
X500086APIEXT500{name} listener exited {error}
X503287STRHLD503this 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}
X503906VLTLCK503vault is locked, refusing {path}, run shc vault unlock, or unattended shc vault unlock --password-file <path>, or --password-file - to read stdin
X503907QRMLST503raft quorum unavailable, refusing {path}, retry once the cluster is healthy

Source: core/appcatalog
Count: 1

CodeHTTPMessage template
X400761APPMAN400{path} is not an app; an app carries app.yaml

Source: core/appref
Count: 1

CodeHTTPMessage template
X400076REPTWO400{ref} names repo {token_repo} but -r/--repo names repo {flag_repo}; drop one of the two

Source: core/collectorcfg
Count: 1

CodeHTTPMessage template
X500110COLCFG500collector config render failed {reason}

Source: core/composeunits
Count: 1

CodeHTTPMessage template
X400228OVRVAL400{flag} is not {want}; nothing was written

Source: core/config/readerscan, core/config
Count: 3

CodeHTTPMessage template
X200763ENVOLD200retired environment variables are set in shcd, {remedy} in its service unit or EnvironmentFile, or its launch environment, then restart the daemon
X400035REFEMB400config key {key} contains an embedded secret-ref which is not resolved, only whole-value refs resolve
X400763ENVOLD400retired environment variables are set, {remedy}

Source: core/containerendpoint
Count: 2

CodeHTTPMessage template
X500087RTENDP500no {engine} api endpoint found, probed {probed}
X500088RTENGB500container engine binary {binary} not found, searched {searched}

Source: core/daemonclient
Count: 8

CodeHTTPMessage template
X200962CLIOLD200this 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/
X400963CTXYML400cannot parse {path} for the active cluster {cluster}, fix its YAML or run shc ctx --reset
X403933DMNACC403permission denied opening the shc daemon socket
X403963CTXREG403cannot read {path} for the active cluster {cluster}, make it readable by this user or run shc ctx --reset
X500932DMNRPC500daemon client {op} failed
X502932DMNRSP502daemon returned an error response {daemon_status}
X503931DMNDWN503the shc daemon is not reachable {target_clause}{dial_clause}{next_step}
X504934DMNNOAN504the shc daemon {target_clause} accepted the connection but did not answer{dial_clause}

Source: core/db/rqlitedriver, core/db
Count: 37

CodeHTTPMessage template
X409990MIGRST409this 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
X409991MIGNEW409this 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
X409992PRELIN409this node {formed} this build’s {line} reset line, {evidence}; {remedy} (https://selfhostedcloud.org/guide/operations/upgrades/#reset-lines)
X500929DBSNAP500control-plane db snapshot failed {error}
X500959MIGNVF500migration integrity verification disabled by escape hatch
X500960DBOPEN500failed to open database handle {error}
X500961DBPING500failed to ping database handle {error}
X500963MIGRDF500failed to read migration {name} {error}
X500964MIGTBL500failed to create migrations table {error}
X500965MIGCHK500failed to check migration {name} {error}
X500967MIGAPL500failed to apply migration {name} {error}
X500968MIGREC500failed to record migration {name} {error}
X500970MIGSCN500failed to scan migrations rowset {error}
X500971MIGITR500failed to iterate migrations rowset {error}
X500972MIGWLK500failed to walk migrations fs {error}
X500974DBTIMS500db.Time cannot scan {type} into time
X500975DBTIMP500db.Time cannot parse {value} with any known sqlite layout
X500981DBMAIN500db maintenance pool not initialised
X500982DBANLZ500db ANALYZE failed {error}
X500983DBVACM500db VACUUM failed {error}
X500984MIGSNS500migration {name} not listed in atlas.sum
X500985MIGLDG500applied migration {name} drifted, ledger checksum {want} but on-disk content is {got}
X500986MIGSUM500migrations atlas.sum missing or invalid {error}
X500987MIGSTL500atlas.sum entry {name} has no matching migration file
X500988MIGSHA500migration {name} checksum mismatch, atlas.sum records {want} but file hashes to {got}
X500991SCHCOL500table {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
X501004BATBGN501failed to begin atomic batch {error}
X501005BATSTM501atomic batch statement {index} failed {error}
X501006BATCMT501failed to commit atomic batch {error}
X501007RQLNTX501rqlite engine has no interactive transactions, {op} refused, use db.Pool.Batch for multi-statement atomicity
X501008RQLBAT501rqlite atomic batch request failed {error}
X501019CFSSNX501table {table} is outside this build’s snapshot, it was excluded or created after the snapshot was taken
X501023RQLNPM501rqlite named parameters unsupported in statement {statement}
X501032RQLNAK501rqlite returned {returned} of {statements} statement results for {op} with error {error}, the outcome is unknown and the statements may not have committed
X501042RQLSTL501local read refused by rqlite, {error}
X501043RQLMAT501materializing the blob column {column} failed {error}
X501047DBRSNP501the snapshot a clusterfs build reads the store through failed: {error}

Source: core/eegate
Count: 1

CodeHTTPMessage template
X403026DMNEEO403{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

Source: core/eestub
Count: 1

CodeHTTPMessage template
X403028CLIEEO403shc {command} requires SHC EE, this binary is the community edition

Source: core/enginemarker
Count: 1

CodeHTTPMessage template
X500020ENGMKR500engine marker read failed {reason}

Source: core/executor/apple, core/executor/incus, core/executor
Count: 86

CodeHTTPMessage template
X200018INCCRT200the 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
X200107INCWTR200removed {count} health watcher trust entries whose watcher is gone: {entries}
X200124INCHLP200{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
X200162INCAVR200dropped 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
X200165INCEXK200the exit of {entry} in {project} could not be kept on its instance, and a reboot would lose it: {reason}
X200256INCDLK200removed incus-compose lock {lock} whose holder pid {pid} on this host is no longer running
X200373INCIPL200Incus recorded member {member} as holding image {fingerprint} with no file there; deleted its records in {projects} and fetched it again
X200380INCDNR200the {verb} for {project} found Incus’s setup of {network} failing on attempt {attempt} of {tries} ({why}); it runs again in {wait}
X200382INCLKR200the {verb} for {project} found Incus’s global database locked on attempt {attempt} of {tries}: {answer}; it runs again in {wait}
X200391INCTOK200cancelled {count} image download tokens incus-compose’s copies left running in {project} on member {member}
X200399INCGAT200the member-local listing {path} waits for this member’s Incus to answer GET /1.0 before it is sent: {why}
X200400INCUSE200the usage of {instance} is read through Incus, not on the host: {reason}
X200658INCARM200the health watcher {watcher} of {entry} in {project} has run no check for {idle}, even once woken, and was told to end and start again
X200714EXECAR200{service} of {project} keeps {path} on volume {volume} from now on, with what anonymous volume {source} held there
X200799INCPPL200the 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
X200800INCANN200the incus runtime keeps the annotations of {entry} in {project} as user. config; {keys} name no key it can take there and are dropped
X200801APLANN200the apple runtime keeps the annotations of {entry} in {project} as labels; {keys} name a label already written and are dropped
X200802EXEPST200the pre_stop hook {hook} of {container} did not end cleanly, {reason}; the stop goes on
X200803EXEHOK200the {runtime} runtime runs no {hook} hook, so SHC runs those of {services} in {project} itself
X200806EXEPRC200SHC pulled {image} but could not record the pull, {reason}; the next up pulls it again
X200810EXERTY200the pull for {subject} got a transient registry answer on attempt {attempt} of {tries}, pulling {where}: {answer}; it pulls again in {wait}
X200815INCWAK200the health watcher of {entry} in {project} has run no check for {idle} and could not be woken: {reason}
X200816INCWOK200the health watcher of {entry} in {project} had run no check for {idle}, past its {interval} interval, and was woken
X200824EXERWT200the {runtime} runtime writes {key} of {service} in {project}; {did}
X200846INCFIL200a files request to incus failed and is tried again in {delay}, try {try} of {tries}, {reason}
X200847INCFOK200a files request to incus answered on try {tries} after it failed with {reason}
X200872INCDNS200stopped dnsmasq {pid} on member {member}: it still served bridge {bridge}, which Incus no longer has, and held {addresses}
X200872INCORB200removed orphan bridge {bridge} ({subnet}) on member {member}: Incus holds no network of that name
X200898INCRMK200deleted 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
X201032INCUPT201up of {project} took {took}: {phases}
X201033INCDWN201down of {project} took {took}: {phases}
X206714IMGLFT206the {runtime} image prune removed {removed} of {meant} images and left {left}
X400770EXERUN400runtime {runtime} has no executor in this daemon
X400772EXEENV400exec into {container} refused env entry {key}, {reason}
X400773EXEARG400exec into {container} was handed no command
X400774APLKEY400the apple runtime refuses {project}: {found}
X400775APLCMP400the apple runtime cannot run {project}: {detail}
X400776INCKEY400the incus runtime refuses {project}: {found}
X400776INCMNT400the incus runtime refuses {entry} in {project}: volume target {target}, {reason}
X400776INCUSR400the incus runtime refuses {entry} in {project}: user {user}, {reason}
X400777INCCMP400the incus runtime cannot run {project}: {detail}
X400778INCEXE400exec into {container} refused, {reason}
X400781EXECRT400the engine refused to create a container of {project}: {refusal}
X400783EXEIMG400{project} names the image {image}, which no registry can be asked for: {reason}
X400786INCPID400the 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
X400788APLPID400the 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
X400789EXEHST400the {runtime} runtime runs on {on} nodes, and this node runs {here}
X400795INCIMG400the incus runtime cannot read the image {image} of {entry} in {project}: {reason}
X400796EXELOG400the {runtime} runtime does not support logs {option}
X400797EXEPDM400the podman runtime refuses {project}: {found}
X400840INCSRC400the incus runtime cannot start {project}: a bind source is missing on this node, {missing}
X400842INCPOL400the incus runtime cannot make the volumes of {project}: incus.volume_pool names pool {pool}, which this node’s Incus does not have
X403782EXELGN403{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}
X403786EXEFBD403{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}
X409715EXECNV409{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
X409781INCPRT409the incus runtime cannot publish {port} for {entry} in {project}: {holder}
X409834EXEENR409{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
X409841INCPLC409the incus runtime on cluster member {member} is not given its instances: {unmet}
X500256INCDLK500cannot 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
X500399INCNTF500{method} {path} refused: only a GET listing of /1.0/instances or /1.0/operations carries an Incus cluster User-Agent
X500492INCERR500{entry} in {project} did not start: its instance {instance} still read {state} {window} after its start, and it recorded no exit
X500771EXECMD500{verb} for {subject} failed, {detail}
X500776INCLXC500lxc could not start {entry} in {project}: {reason}
X500779INCENV500the incus runtime cannot stage the environment of {entry} in {project}: {reason}
X500787INCSTS500the incus runtime cannot keep the exit status of {entry} in {project}: {reason}
X500804EXEPOS500a post_start hook of {container} in {project} failed, {reason}; the container is stopped
X500805EXEPRS500the pre_start hook {hook} of {service} in {project} exited {code}; {service} is stopped
X500833EXEENS500the environment of {service} in {project} is not staged in RAM, {reason}
X500872INCDNF500cannot stop dnsmasq {pid} on member {member}, which still serves bridge {bridge} that Incus no longer has and holds {addresses}: {reason}
X500872INCORF500cannot remove orphan bridge {bridge} ({subnet}) on member {member}: {reason}
X502811EXEPUL502the pull for {subject} failed {attempts} times on a transient registry answer, the last pulling {where}: {answer}
X503107INCWTR503the health watcher trust pass failed {step}: {reason}
X503373INCIPL503the incus runtime cannot put the image {image} ({fingerprint}) of {project} on member {member}: {reason}
X503380INCDNB503the {verb} for {project} is refused: Incus could not set up {network} on any of {attempts} attempts ({why})
X503382INCLKD503the {verb} for {project} found Incus’s global database locked on all {attempts} attempts: {answer}
X503391INCTOK503cannot cancel the image download tokens incus-compose’s copies left running in {project} on member {member}: {reason}
X503399INCGAT503the member-local listing {path} was not sent: this member’s Incus has not answered GET /1.0 ({why}): {reason}
X503400INCUSE503Incus could not tell the state of {instance}, which is asked again in {wait}: {reason}
X503780INCRST503cannot start {container}, its environment is not staged on this node: {reason}
X503784EXEASK503{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}
X503789INCREG503the incus runtime cannot pull the images of {project} from {registry}: {reason}
X503843INCPOL503the incus runtime cannot place the volumes of {project} in pool {pool}: {cause}
X504099INCDLN504incus-compose {verb} for {project} did not finish within {bound} and was stopped
X504304INCIMW504incus-compose {verb} for {project} did not finish within {bound} and was stopped: it waited on image {image}, which Incus operation {operation} holds
X504794INCHLT504{entry} in {project} did not read healthy within its healthcheck’s window of {window}: {reason}
X504809EXESTL504the pull for {subject} stalled {tries} times, its processes read and wrote nothing for {window} {where}

Source: core/fwdhook
Count: 1

CodeHTTPMessage template
X500396FWHDRP500this node’s forward hook may drop traffic between containers on one bridge, {culprits}, run shc doctor for the full probe

Source: core/herd/herdhttp
Count: 1

CodeHTTPMessage template
X429281APILIM429{provider} API account {account} is rate limited for {wait}, hold set by {header}

Source: core/hostactivate
Count: 14

CodeHTTPMessage template
X403027CLIPRV403shc {verb} must run as root, re-run as sudo shc {verb} or set SHC_STATE_HOME for a rootless dev sandbox
X409131UNTAVL409the 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
X409135LNCAVL409the 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
X500131STWRFL500the shc daemon cannot write its state directory {error}; stop it with systemctl stop shc and re-run shc init
X500132UNTSTP500could not stop the shc unit before replacing its state directory {error}; stop it with systemctl stop shc and re-run shc init
X500133UNTSTA500could not tell whether the shc unit is running {error}; refusing to replace its state directory
X500134UNTSTR500could not start the shc unit again after init refused {error}; start it with systemctl start shc
X500136LNCSTP500could 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
X500137LNCSTR500could not start the shcd launchd job again after init refused {error}; start it with sudo launchctl bootstrap system /Library/LaunchDaemons/org.selfhostedcloud.shcd.plist
X500687PODSCK500systemctl 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
X500978PODDRP500podman systemd drop-in setup failed at {step} {error}
X501036SVCPLT501host service activation is not implemented for {platform}, start and enable the shc daemon with this host’s service manager
X501037LNCJOB501launchd job setup failed at {step} {error}
X503138DMNEXT503the 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}

Source: core/hostplat
Count: 3

CodeHTTPMessage template
X501391CLSPLT501cluster fabric {fabric} is not supported on {platform}, {reason}, use --fabric none for a single node
X501392CLJPLT501joining 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
X501395ROLCAP501{node} cannot take {role}, its host lacks the {capability} capability, {needs}

Source: core/incusapi
Count: 2

CodeHTTPMessage template
X400461INCAPI400{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
X503462INCSCK503{verb} on the incus runtime cannot read Incus on {socket}, nothing was changed: {cause}

Source: core/jinja
Count: 13

CodeHTTPMessage template
X400147JNJRET400template input {name} is gone, use {now}
X400500JNJMAP400jinja path {path} traversal blocked, {key} is not a map
X400501JNJKEY400jinja path {path} traversal blocked, key {key} missing
X400502JNJLOAD400jinja template loading is disabled, refused {ref}
X400503JNJBIG400jinja render exceeded the {limit} byte output cap
X400504JNJTIME400jinja render exceeded the {limit} time budget
X400505JNJPANIC400jinja render panicked: {detail}
X400506JNJCAP400jinja strict-undefined inventory is partial, {dropped} of {examined} references were not examined
X400507JNJPRS400jinja template {where} failed to parse: {detail}{hint}
X400510JNJEMIT400jinja template {where} could not be attributed to its expressions: {reason}
X400511JNJSHAPE400jinja template {where}: {culprit} changes the YAML structure the template defines, {fault}; a substituted value must stay inside the scalar it is written into
X400512JNJMBR400members block at line {line}: {detail}
X400513JNJREF400jinja template refused the render: {reason}

Source: core/labeltext
Count: 2

CodeHTTPMessage template
X400189LBLSYN400label {label} is not key=value or key!: {problem}
X400190LBLDUP400label {key} is named twice, a node carries one value of an operator key

Source: core/log
Count: 1

CodeHTTPMessage template
X503118LOGCAP503log 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

Source: core/nic
Count: 2

CodeHTTPMessage template
X400992NICNOF400interface {name} not found or has no IPv4 address
X500930NICDET500network interface detection failed {reason}

Source: core/nodefact
Count: 2

CodeHTTPMessage template
X400252CLDGON400--provider is gone, write --cloud {value}
X400299FNCJON400--fence is gone, write --label key=value or --control-plane

Source: core/objchange
Count: 2

CodeHTTPMessage template
X500171OBJUNK500object change {code} for {kind} {op} is not registered, nothing was recorded
X503170OBJAUD503audit entry for {kind} {name} was not written, code {code}, {error}

Source: core/openstack
Count: 3

CodeHTTPMessage template
X400335OSKCFG400openstack auth config invalid, {reason}
X404325OSKEPT404openstack service {service} endpoint not found in catalog for region {region} interface {interface}
X502335OSKAPI502openstack api call {op} failed http {status} {detail} {error}

Source: core/otelboot
Count: 2

CodeHTTPMessage template
X403128OTLORG403export refused, the request is not for the managed openobserve origin this exporter was built for
X503127OTLHLD503export held, this node has no credential for the managed openobserve yet, its vault is locked or holds none

Source: core/pagecache
Count: 1

CodeHTTPMessage template
X500130PGCHLD500{held} bytes of {file} are still in the page cache after {passes} passes over {took}

Source: core/replicalabel
Count: 4

CodeHTTPMessage template
X400243REPLNO400no replica matches {selector}: {replicas}
X400255REPLNM400{name} names a replica, and --where names one too; pass one of them
X409258REPLND409replicas matching {selector} are held on {nodes}; run this operation there
X503259REPLRD503replica label reader is not wired

Source: core/rqlited
Count: 29

CodeHTTPMessage template
X409047RQDCLI409this node is a store client and runs no raft engine, so it cannot {op}, run it on a voter or a replica
X501009RQDBIN501rqlited binary not found, install the shc package or set SHC_RQLITED_BIN
X501010RQDSTR501rqlited exited during startup with code {code} {error}
X501011RQDTMO501rqlited not ready within {timeout}
X501012RQDCFG501rqlited manager misconfigured {reason}
X501013RQDSPN501failed to spawn rqlited {error}
X501014RQDBOO501rqlite /boot ingest of {path} failed {error}
X501015RQDBKP501rqlite backup to {path} failed {error}
X501016RQDLDR501rqlite leader/roster query failed {error}
X501020RQDCRA501rqlited exited unexpectedly with code {code}, relaunching
X501021RQDRLF501rqlited relaunch failed, retrying {error}
X501022RQDRNR501relaunched rqlited not ready {error}
X501024RQDPRB501rqlited readiness probe {url} returned HTTP {status}
X501025RQDGET501rqlite api GET {url} returned HTTP {status} {body}
X501026RQDMKR501engine flip marker {marker} not removed {error}
X501027RQDPRA501rqlite promote retry abandoned, cluster has {nodes} members and the ingest window is gone, continuing as a member on {sqlite}
X501028RQDDMF501cluster scaled back to one node, storage engine demoted to plain sqlite on {sqlite}, scheduling daemon restart to complete the flip
X501029RQDPMF501storage engine promoted to rqlite for the joining node, marker {marker} written, scheduling daemon restart to complete the flip
X501030RQDDGR501rqlite engine started degraded, rqlited not ready within startup budget, retrying bring-up in background {error}
X501031RQDNRD501rqlite engine not ready, background bring-up in progress
X501034RQDSLF501cluster join addresses named this node’s own raft address {addr}, dropping it, rqlited cannot join itself
X501035RQDNOJ501no raft join address left for the joining node in {state}, re-run shc node join against the cluster leader
X501038RQDGRC501the 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
X501039RQDNLD501local rqlited no longer leads
X501040RQDLBF501local leader batch failed, {reason}
X501041RQDBRF501rqlited binary not found, install the shc package or set SHC_RQLITED_BIN, refused {refused}
X501044RQDCLD501store client started degraded, no member of its store list answered within {budget}, restarting once one does {error}
X501045RQDCDR501store client could not remove the rqlite data {dir} it kept as a replica {error}
X501046RQDCUP501replica did not catch up with the leader’s revision {want} within {timeout}, its copy reads {have}, serving anyway

Source: core/secretscratch
Count: 1

CodeHTTPMessage template
X500146SCRRAM500{subject} holds resolved secrets and was not written, because the secret scratch directory {dir} cannot take it: {reason}

Source: core/selector
Count: 11

CodeHTTPMessage template
X400240SELSYN400{selector} is not a selector: {problem} at byte {position}
X400241SELRES400selector {selector} names {place}, which cannot be answered: {reason}
X400242SELFLG400{flag} is gone, write {now}
X400244SELCLN400{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
X400245SELEMP400{flag} entry {entry} needs a selector after {service}:; write {service}! to drop it
X400246SELONE400{flag} entry {entry} names more than one service; write one service per entry as <service>:<selector>
X400247SELENT400{flag} entry {entry} has an invalid selector: {problem}; write <service>:<selector> with a valid selector
X400248SELDUP400{flag} states the deployment-wide rule twice; join the selectors with &
X400249SELCON400{flag} states different selectors for {service}; write one selector for that service or pod
X400250SELSVC400{flag} entry {entry} is per-service placement; set per-service rules with shc install or shc update
X400257SELNAM400{flag} names unknown service or group {service}; write one of the app’s services or groups: {services}

Source: core/svcexec
Count: 12

CodeHTTPMessage template
X201004SVCCPL201staged artifact directory {path} could not be removed from service {service} after the job ran, {detail}, operator data may remain inside the running container
X501050SVCEXRT501cannot exec into service {service}, runtime {runtime} has no service-exec dialect
X501052SVCJREQ501service-context job is missing required field {field}
X501053SVCJCTX501job {job} declares context {context}, which cannot be dispatched
X501054SVCJARG501service {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
X501055SVCJRUN501cannot run container job {job}, runtime {runtime} has no one-off container dialect
X501056SVCCPY501service {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
X501057SVCCPS501artifact transfer for service {service} failed, {detail}
X501058SVCJVL501job {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
X501059SVCENVF501the 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
X501060SVCNCT501service {service} of {deployment} has no container to exec into on this node{detail}
X501061SVCCPR501service {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

Source: core/tenantscope
Count: 1

CodeHTTPMessage template
X400976TNTNON400no tenant named, pass -t TENANT, or X-SHC-Tenant on the API

Source: core/timescale
Count: 2

CodeHTTPMessage template
X400109TMSCAL400a 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
X400137TMSNUM400SHC_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

Source: core/usagecharge
Count: 1

CodeHTTPMessage template
X500926USGCHG500usage charge matched no row for tenant {tenant}

Source: core/validation
Count: 3

CodeHTTPMessage template
X400764ENVPRD400environment {name} is gone, write prod
X400982NAMINV400invalid {kind} name {name}, {reason}
X500982VLDINT500validation internal error {error}

Source: core/volume
Count: 34

CodeHTTPMessage template
X400310VOLCOL400invalid mount spec {spec}, too many colon-separated fields
X400311VOLAXS400invalid mount spec {spec}, malformed access field
X400312VOLEXT400invalid mount spec {spec}, unexpected field {field}
X400313VOLPRM400invalid mount spec {spec}, perm field {field} is not numeric
X400314VOLFLD400invalid mount spec {spec}, too many trailing fields
X400315VOLOWN400invalid mount spec {spec}, owner field mismatch uid {uid} gid {gid}
X400316VOLEMP400apply prep called with empty source
X400317VOLPMD400parse mode {mode} failed, {error}
X400318VOLMOD400empty mode string
X400319VOLUID400parse uid {uid} failed, {error}
X400321VOLGID400parse gid {gid} failed, {error}
X400328VOLACC400volume mount {mount} declares access {access}, which is not supported, use rwo, single-node read-write, or rox, read-only multi-attach
X400337VOLDCL400x-shc-volumes {subject} {problem}
X400338VOLSIZ400volume mount {mount} declares size {size}, which is not a capacity, use a form like 10Gi 512Mi 1T or a byte count
X403322VOLSMT403absolute mount source {source} is not permitted for tenant {tenant}
X403323VOLESC403mount source {source} escapes the deployment sandbox
X403325VOLPMU403mount source {source} is not a platform mount, known: {known}
X403326VOLPMW403platform mount {source} must be mounted read-only: append :ro
X403327VOLTLSU403no certificate-delivery grant for mount source {source}
X403328VOLPMS403platform mount {source} is reserved for the system tenant, refused for tenant {tenant}
X403329VOLSGL403volume source {source} is not a usable converter reference, {name} must be a single directory name
X403331VOLBRK403deployment {tenant}/{environment}/{stack}‘s docker socket cannot be brokered here
X403334VOLNST403mount source {source} is not one directory name, a mount cannot sit inside another
X403335VOLFRO403mount source {source} is not a single file of the app, mount it read-only, append :ro
X409034VOLNMT409refusing volume prep, {path} is not a confirmed mountpoint, attach may have silently failed
X409347VOLSCF409volume {source} already holds {entry}, which is not the image’s {kind}, the seed leaves it as it is
X409348VOLSND409the image’s {path} is a {kind}, not a directory, so no volume can be seeded from it
X500310VOLCMD500{op} {path} failed {error}
X500311VOLOWR500resolve owner {owner} failed {error}
X500312VOLUSR500user lookup {user} failed, {error}
X500313VOLGRP500group lookup {group} failed, {error}
X500314VOLMDR500resolve data mount failed, MountsDir not set
X500316VOLMNT500mountpoint check for {path} failed, {error}
X500317VOLSED500volume seed of {source} from image {image} failed, {error}

Source: modules/ctx
Count: 1

CodeHTTPMessage template
X404903CTXNAC404no active cluster, {detail}

Source: daemon/wiring, daemon
Count: 57

CodeHTTPMessage template
X200133SYSRBT200system routes value {variable} carries a backtick, which closes a traefik rule matcher, so the routes built from it were not rendered
X200311VOLSWP200volume size sweep: {recorded} recorded, {unreadable} unreadable, {unsupported} on a provider that cannot report a size
X403992MSHEEO403peer 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
X403993CLNEEO403clone/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
X409129VOLRCL409rebind claim lost {when} relocation {error}
X409554DRNFIL409{stack} was not moved off {node}, {reason}
X409638CLNRLD409this node already holds {entry} in {stack}‘s deployment directory {dir}, and a relocation never writes over it; move the directory aside and move again
X409670CLNPRS409relocating {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
X409677CLNTHN409{stack} came up on node {node} without {missing} it had before, so the move or clone that carried it there is refused
X500381CLNSHW500wrote {wrote} of the archive’s {size} bytes
X500382DRNCMP500{verb} of {stack} on {node} failed {stderr}
X500383DRNSTR500{deployment} did not start again {error}
X500623CLNXFR500clone 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
X500635CLNRLC500move could not relocate {stack} onto node {node}, {reason}; it is restarted on the node it was on
X500641CLNRLF500relocating {stack} onto node {node} failed and nothing of it runs there, {reason}
X500912KCTRPL500keycloak trust pool unavailable {reason}
X500913KCDIAL500keycloak backchannel refused dial to non-SHC_HOST address {addr}
X500914KCNOSH500managed keycloak requires SHC_HOST but it is unset
X500992DMLOCK500another shcd already holds the singleton lock {path}, refusing to start a second instance
X500994DMCNFG500daemon config load failed {error}
X500995DMDBOP500daemon db.Open failed {error}
X500996DMRALC500daemon subsystems.RegisterAll failed {error}
X500997DMRAPN500daemon panic during RegisterAll {detail}
X500998DMWIRE500daemon lifecycle.Wire failed {error}
X500999DMMKDR500daemon mkdir {path} failed {error}
X501016DMBSTR501node_bootstrap.json at {path} cannot be read {error}
X503054OTLINI503otel init failed, continuing without telemetry {error}
X503055SUBSTP503subsystem stop returned error {error}
X503056OTLSHD503otel shutdown error {error}
X503057OTLEXP503otel export failing, telemetry is being dropped, {suppressed} further failures suppressed since the last report {error}
X503059DNSCFG503dns service skipped, nil config
X503060QTANPL503quota service skipped, nil db pool
X503061RPONPL503repo service skipped, nil db pool
X503062RETNPL503retention service skipped, nil db pool
X503063SRCNPL503search service skipped, nil db pool
X503064CLSNPL503cluster service wired without pool, node repo unavailable
X503065CENRSK503cluster enroll handler skipped, cert provider or node repo unavailable
X503066MSHNRG503mesh orchestrator skipped, node registry not wired
X503067MSHNPC503mesh orchestrator skipped, peer client not wired
X503068MSHCST503mesh orchestrator construct failed {error}
X503069VLTAUS503vault audit writer skipped, audit service not wired
X503070QTANPL503quota cron deps skipped, nil db pool
X503071STKMVS503stack move translator skipped, runtime state nil
X503073PEERHTT503internal-API peer call failed {host} {path} {op} {error}
X503074PEERCRT503internal-API peer client cert load failed {op} {error}
X503074SCLWIN503x-shc-scale window scaling service {service} failed {error}
X503075STKCTL503backup stack-controller {op} failed for {project} {error}
X503077CASRCR503ca-signer connection cred read hit a transient vault fault for tenant {tenant} connection {conn} field {field} {error}
X503078LDRNDL503leader internal-address resolve could not list the node table, falling back to the raft-host heuristic {error}
X503084OTLNOA503managed openobserve destination resolved with no auth header on this node, its telemetry is dropped until the vault unlocks here
X503085SHFSMT503shared-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
X503086VOLORF503volume {volume} mount {mount} provider {provider} is orphaned after move, cloud volume not deleted, verify and clean up with shc volume rm {volume}
X503087RETNBK503retention cannot delete an archive: the backup service is not wired yet, row kept
X503096REGRCR503registry connection cred read hit a transient vault fault for tenant {tenant} connection {conn} field {field} {error}
X503097USRNPL503user service skipped, nil db pool
X503098CATNPL503catalog service skipped, nil db pool
X503129DRNNWR503{seam} not wired on this daemon

Source: modules/deploymentspec
Count: 11

CodeHTTPMessage template
X400546DSPRBA400{digest} names more than one kept spec of {deployment}: {matches}
X400734DSPENC400the spec of {deployment} could not be encoded: {error}
X404543DSPRBD404{deployment} keeps no spec {digest}, it keeps {kept}
X404547DSPRBG404{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=, it keeps {kept}
X404733DSPNOF404{deployment} has no stored spec: nothing rendered it on this line
X404735DSPPRV404{deployment} cannot put spec {digest} back: it is no longer stored
X409544DSPRBC409{deployment} runs spec {digest} already
X409545DSPRBU409{deployment} cannot roll back while spec {digest} is not committed, an operation is still changing it
X500731DSPWRT500the spec of {deployment} could not be written: {error}
X500732DSPRED500the spec of {deployment} could not be read: {error}
X503730DSPSTO503deployment spec {op} has no store yet, the daemon has not opened the control plane

Source: modules/depnet
Count: 3

CodeHTTPMessage template
X409786DNTCLS409network {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
X500780DNTSTO500deployment network ledger {op} failed, {error}
X503781DNTFUL503node {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

CodeHTTPMessage template
X200145DNSRDY200dns host {host} was not answered by nameserver {nameserver} within {wait}, check the zone’s delegation and nameservers
X200146DNSAUT200dns host {host} could not discover the nameservers of zone {zone}, check the zone’s delegation and outbound port 53
X200150DNSCMO200dns provider {endpoint} did not commit staged record writes, the writes stand and the commit is retried in {wait} {error}
X200904DNSTDN200dns record write skipped for host {host}, cluster teardown release already ran
X200905DNSRLZ200cluster teardown release reached zero dns zones, {hosts} intended hostnames were not released
X200906DNSRLI200cluster teardown release still incomplete after {attempts} attempts, records may still be live
X200907DNSRTU200dns delete for host {host} resolved through retired connection {connection}, its live connection is already gone
X200918DNSRTS200retired dns connection source unreadable during release, {reason}
X200919DNSRTP200retired dns connection {connection} credentials not purged after release, {reason}
X200920DNSGTO200dns takeover of host {host} from {found_owner} at generation {found_generation} as {owner} at generation {generation}
X200921DNSPRV200private dns record for host {host} skipped, no address is known for the {plane} plane served by connection {connection}
X200922DNSAZF200private dns zone {zone} could not be registered on connection {connection} {error}
X200923DNSAZA200private dns zone for host {host} not auto-created, connections {connections} are all eligible, declare the zone explicitly with connection connect --zone
X200924DNSPOO200dns.private_records is false for host {host} but connection {connection} is the only plane publishing it, suppressing would leave the host unresolvable, publishing anyway
X200925DNSPFL200private dns record for host {host} on connection {connection} failed, the public record published {error}
X200926DNSAZW200private dns zone {zone} for host {host} not auto-created, no zone registrar is wired in this process
X200927DNSAZN200auto-created private dns zone {zone} on connection {connection} for host {host}
X200928DNSPSK200dns plane for host {host} on connection {connection} skipped, the connection has no working dns provider, the remaining planes still publish {error}
X200929DNSWBD200dns write for {name} deferred, this sweep has spent its budget of {budget} record writes
X200930DNSWBS200dns sweep wrote {written} records and deferred {deferred} under its write budget, the next pass continues
X200937DNSWBX200dns sweep still defers {deferred} record writes after {passes} passes with no progress, replay stopped until the ingress changes or leadership moves
X400032DNSZON400dns zone not found for domain {domain}
X400034DNSTGT400cannot resolve target {target} to ip or hostname
X400036DNSMAN400no dns provider manages zone for {hostname}
X400110DNSZNC400zone_id must be set on record for create
X400111DNSZNU400zone_id must be set on record for update
X400112DNSZND400zone_id must be set on record for delete
X400113DNSZNO400zone_id must be set on record for create_or_update
X400114DNSSET400set_records requires at least one content, use delete to clear an rrset
X400117DNSNBT400netbird zones hold only a, aaaa and cname records, {record_type} refused
X400118DNSNBR400netbird record name {name} refused, _shc-owner and _acme-challenge labels are reserved in a netbird zone
X400119DNSPFT400pfsense zones hold only a and aaaa records and ownership claims, {record_type} at {name} refused
X400120DNSPFR400pfsense record name {name} refused, the _shc-owner label is reserved for ownership claims
X400121DNSPPA400dns record for host {host} refused on public connection {connection}, {address} is a private address
X400841DNSOLD400{field} is gone for {provider}, write {replacement}
X400922DNSUNK400unknown dns provider {provider}
X400926DNSREQ400{config_key} is required for {provider} dns provider
X400987DNSMRC400dns socket cannot write record {name}: {reason}
X403040DNSOWN403dns records for host {host} owned by {found_owner} not {owner}
X403041DNSUNO403no ownership txt for host {host}, refusing to delete unowned records
X403042DNSPRN403skipping prune of unowned {record_type} record {content} for host {host}
X403043DNSRPP403skipping reap of pinned host {host}
X403044DNSRPL403leaving predecessor-owned host {host} alone, ownership cannot be proven for {owner}
X403046DNSTKO403taking over dns records for host {host} from predecessor {found_owner} as {owner}
X403047DNSGEN403dns 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
X403048DNSSBY403dns {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
X403049DNSPTO403dns {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
X403050DNSIHT403taking over dns records for host {host} from {found_owner}, whose claim stands on the host itself, as {owner}
X403986DNSGNT403tenant {tenant} is not granted dns provider {provider}; the master tenant grants it via shc config set dns.grants.{tenant}.{provider} true at global scope
X404038DNSZNF404no dns zone manages host {host}
X404039DNSREC404no dns record found for host {host}
X404047DNSNFD404dns provider reports {detail} not found
X404860DNSACH404no public dns connection with dns-01 credentials manages host {host}
X404988DNSMZN404no dns connection owns a zone covering {host}; bind a dns-capable connection whose zone is a suffix of it
X409861DNSACB409dns-01 challenge name {name} holds another value the provider cannot keep beside ours
X409872DNSOWW409wildcard 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
X409873DNSOWC409ownership 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
X409966DNSWNS409wildcard host {host} cannot be published through dns provider {provider}, shc publishes wildcard records only through a provider whose zone answers from wildcards
X409967DNSWAP409wildcard 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
X409968DNSWAD409wildcard host {host} publishes only A and AAAA records, a CNAME wildcard would capture the dns-01 challenge lookups under it
X502870DNSTYR502moving host {host} from {from_type} to {to_type} failed, the {from_type} record still answers {error}
X502871DNSTYL502moving 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}
X503030DNSAPI503dns provider api error {detail} {error}
X503031DNSCFG503no dns provider configured
X503032DNSACT503dns 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
X503033DNSUPD503rfc2136 dynamic update failed {detail} {error}
X503034DNSRPS503dns reap refused, no managed hostname source is wired
X503035DNSRPK503dns reap refused, managed hostname read failed {error}
X503036DNSRPZ503dns reap refused, managed hostname set is empty
X503037DNSRPB503dns reap refused, {orphans} of {total} owned hosts would be deleted, pass force to override
X503038DNSOID503dns owner id is not configured, set dns.owner_id before any dns write
X503039DNSINV503dns inventory refused, deployment host read failed {error}
X503045DNSCMG503dns provider {endpoint} has not committed staged record writes after {attempts} attempts, they go live with its next commit {error}

Source: modules/docker
Count: 15

CodeHTTPMessage template
X400060CTRINP400invalid docker request {reason}
X400067CTRFSP400invalid container fs request {reason}
X400311REGCRD400registry connection {connection} has no username, so it cannot authenticate any pull
X404060CTRNOF404container {container} not found
X404061CTRFSF404path {path} not found in container {container}
X409310REGTIE409registry connections {first} and {second} both claim {server}; docker holds one credential per registry, so which one authenticates would be nondeterministic
X500061DKRCFG500docker client configuration error {reason}
X500062DKRCLL500docker {operation} failed {reason}
X500063CMPFAL500docker compose {subcommand} exited {exit_code} {reason}
X500064EXCFAL500docker exec on {container} failed {reason}
X500065EVCNCT500docker events channel closed {reason}
X500066EVCMAX500docker events {attempts} consecutive reconnect failures
X500067CTRFSO500container fs {op} on {container} failed {reason}
X500312REGBAS500docker registry config could not be parsed or rendered: {reason}
X500313REGWRT500registry credential file {path} could not be written: {reason}

Source: modules/doctor
Count: 17

CodeHTTPMessage template
X200985DCRRTM200this node runs the {runtime} runtime and no docker, {check} skipped
X400271HSTHDR400--host is gone, write {now}
X400921DCRUNK400no diagnosis named {diagnosis}
X400922DCRNDS400diagnosis {diagnosis} has no destructive fix, its class is {class}; use --fix
X409717DCRRUN409doctor fix {operation} is running on node {node} since {since}, shc doctor follow {operation} waits for it
X410565DCRGON410no node holds operation {operation} any more, its daemon restarted or it ended more than five minutes ago, shc doctor run shows what is left
X500917DCROPF500doctor {operation} failed
X500918DCRNWR500doctor diagnose dependency not wired {dep}
X500923DCRNDY500rbac deny enforcement not verified: {reason}
X500924DCRNRA500rbac app reachability not verified: {reason}
X500926DCRCTL500container listing unavailable on this node, {check} skipped
X503919DCRKCD503system keycloak not running, {check} skipped
X503920DCRNAV503doctor fixes require a running daemon
X503927DCRNPR503doctor origin-probe is not wired on this daemon
X503928DCRKCR503keycloak could not be read, {check} not verified: {reason}
X503929DCRNLC503no diagnosis named {diagnosis} here, and the daemon that holds the module checks is not reachable
X504849DCRFOL504the fix goes on as operation {operation}, shc doctor follow {operation} waits for it again and shc operation ls lists it while it runs

Source: modules/events
Count: 11

CodeHTTPMessage template
X400046EVTTYP400event type {type} is none of {types}
X500007EVTBUS500event bus not running, {reason}
X500015EVTBCS500event broadcaster {stage} failed {error}
X500016EVTHND500event handler panicked {reason} {error}
X500017EVTPRN500event prune failed {op} {error}
X500018EVTCAP500event row truncated by the containment cap, code {code}, {detail}
X500019EVTSUP500suppressed {count} duplicate occurrences of {code}, coalesced by the events containment layer
X500020EVTDROP500pending-broadcast backlog cap shed {dropped} non-audit rows to hold the cap of {cap}
X500021EVTSHD500event bus shed {dropped} events and could not publish the report {error}
X500023EVTTRM500{summary} and could not publish the report {error}
X500026EVTTSK500event and its task rows not written together: {reason}

Source: modules/export
Count: 42

CodeHTTPMessage template
X400501EXPINV400invalid exporter configuration {detail} {error}
X400503IMPREQ400missing required import parameter {param}
X400504EXPREQ400missing required export parameter {param}
X400505IMPJOB400import job {job_name} failed {error}
X400507NOEJOB400exporter {exporter_name} has no exporter jobs defined
X400508NOIJOB400exporter {exporter_name} has no importer jobs defined
X400509ARERRO400ar archive error {op} {error}
X400515WRPSPC400wrap spec malformed {spec}
X400516EXPNDR400data dir {path} is not a directory
X400516WRPNOF400wrap input not found {path}
X400519EXPSVL400job {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
X400521IMPMTY400import 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
X400522IMPDIR400import 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
X400528EXPUND400exporter {exporter} declares no {direction} parameter {param}, its {direction} parameters are {declared}, nothing was run
X400529EXPTYP400exporter {exporter} declares {direction} parameter {param} as {type}, and {value} is not one, nothing was run
X400544IMPVKY400import vault key {key} is not referenced by the deployment app vars
X400545IMPVFL400import vault output for key {key} is missing, unreadable or not a regular file
X400555IMPVEM400import vault output for key {key} is empty
X400559IMPVSC400import vault key {key} resolves at {scope} scope in the deployment app vars; an import seals only deployment-scoped keys
X404500EXPNFD404exporter {exporter_name} not found in stack {stack_name}
X404523EXPREP404this node holds no replica of deployment {deployment}, so export job {job_name} has no project to run in
X404540IMPNON404no .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
X409108EXPRNG409operation {operation} already holds this export scope, wait with shc operation follow {operation} before retrying
X409524EXPENT409export job {job_name} cannot run as compose service {service} in replica project {project}, that name is one of the replica’s entries
X409525EXPKEY409export 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
X409541IMPSTP409import into {deployment} refused before any job ran: it is stopped, and its {job} job talks to its services; start it first
X409542IMPREF409import into {deployment} refused by its {job} job: {reason}
X409543EXPNRN409{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
X500170EXPLNG500the {action} stopped on an internal fault {detail}
X500511EXPRUN500export run failed {reason} {error}
X500512IMPRUN500import run failed {reason} {error}
X500513EXPNST500export service not wired
X500514EXPSTR500export stream failed {reason} {error}
X500515EXPCKM500data checksum mismatch got {got} want {want}
X500517WRPSTG500wrap staging failed {reason} {error}
X500518EXPLST500export list failed {dir} {error}
X500520EXPMTY500export {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
X500530IMPVIO500import vault seal failed during {operation}
X500531IMPVRB500import vault seal failed and previous values could not all be restored
X500532IMPVJB500import vault output job failed; its output is private
X500533IMPVDR500import vault private directory could not be created
X503526EXPREM503export job {job_name} in project {project} was interrupted, the replica it ran in was removed from this node, retry the job

Source: modules/fabric/engine, modules/fabric/policy, modules/fabric
Count: 54

CodeHTTPMessage template
X200357FABNKY200node {name} enrolled without a fabric public key, no fabric chunk allocated, re-enroll with a fabric-capable cli to repair
X200361FABGLU200fabric host firewall glue not installed, cross-node container traffic may be dropped, {reason}
X200370FABXNG200fabric bridge-crossing guard not in force, a pinned container can reach another tenant’s container on a different local bridge, {reason}
X200376FABQRT200fabric pin {service} of {deployment} left out of the policy, {reason}
X200377FABBNF200fabric bridge netfilter not in force, same-node traffic on one bridge bypasses the fabric policy, {reason}
X200378FABSRT200fabric source-route rejection not in force, a source-routed packet is judged by its first hop and delivered to its next, {reason}
X200379FABCLS200node {node} loaded the fail-closed fabric table, all flows within {cidr} are dropped until its policy can be applied
X200384FABFLW200fabric flows not reconciled, a connection to a released address or across a withdrawn permission may linger, {reason}
X200385FABBRQ200fabric bridge row {interface} for tenant {tenant} on node {node} left out of the policy, {reason}
X200387FABREV200fabric pins of {deployment} released without moving the clusterfs revision, nodes learn of it at the next revision, {reason}
X200389FABLFT200network {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
X200404FABRTQ200fabric routed row {interface} for tenant {tenant} on node {node} left out of the policy, {reason}
X200405FABLOP200published loopback routing not converged, {reason}
X200423FABCRV200fabric chunk {chunk} of node {node} changed without moving the clusterfs revision, the other nodes route it at their next sweep, {reason}
X200555FABEND200{pass} flow pass on node {node} ended {proto} flow {src} -> {dst}, delivered to {backend}, answered to {client}, {reason}
X200556FABIGU200the 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
X400351FABCID400fabric cidr {cidr} is unusable, {reason}
X400355FABKEY400fabric wireguard key for {holder} is invalid, {reason}
X400356FABMOD400unknown fabric {fabric}, must be one of shc|none
X400364FABPOL400fabric policy input invalid, {reason}
X400365FABTEN400fabric policy isolation boundary violation, {reason}
X400371FABSWM400fabric swarm is not supported on the new line, use --fabric shc or none
X400372FABXTN400cross-tenant connection refused, {consumer} in tenant {consumer_tenant} cannot be wired to {provider} in tenant {provider_tenant}, the fabric blocks every flow between tenants
X400373FABNPL400fabric node-plane ruleset input invalid, {reason}
X400383FABEXP400fabric explain request invalid, {reason}
X400386FABENG400node {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
X400387FABNFT400node {node} cannot carry the shc fabric, {reason}, install the nftables package with apt-get install nftables or dnf install nftables
X400388FABINI400node {node} cannot run deployments on podman, {reason}, install catatonit with apt-get install catatonit or dnf install catatonit
X400389FABOFF400the 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})
X400390FABMTU400node {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
X400391FABPCY400node {node} needs python3’s PyYAML and python-dotenv to run podman-compose {compose}, install them with {command}
X400395FABATT400the shc fabric cannot be set up on a node running {runtime}, {reason}, leave --fabric unset to form the cluster without it
X400396FABPDC400node {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
X400397FABPRC400node {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
X400398FABAVK400node {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
X409358FABNON409node {name} cannot join, the cluster fabric is none which allows a single node only, re-init with --fabric shc for multi-node
X409374FABNGR409deployment {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
X409375FABUNP409deployment {consumer} cannot reach {provider} service {service} on the fabric, that service holds no fabric pin, update {provider} first so it renders onto the fabric
X409399FABPRU409the 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
X409401FABCLM409deployment {deployment} render stopped, a later render holds its fabric pins, this render writes no compose and runs none
X409402FABADR409apple replica address refused, {reason}
X409406FABDUP409node {node} cannot join, its shc0 public key is already live on node {holder}
X500352FABREP500fabric allocation repository error {op}{error}
X500353FABFUL500the 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
X500354FABDEV500fabric wireguard device {op} failed{error}
X500359FABPIN500fabric service pin error {op}{error}
X500360FABBRG500fabric network {name} could not be ensured{error}
X500362FABPST500cluster fabric posture error {op}{error}
X500366FABVFY500fabric policy ruleset failed self-verification, {reason}
X500367FABPCY500fabric policy {op} failed{error}
X500397FABPCI500podman-compose {compose} could not be installed at {path} on node {node}, {reason}
X502393FABPCS502podman-compose {compose} fetched from {url} for node {node} has sha256 {got}, not the pinned {want}, so it is not installed
X502395FABPCF502podman-compose {compose} for node {node} could not be fetched from {url}, {reason}
X503382FABGUR503deployment {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}

Source: modules/failover
Count: 2

CodeHTTPMessage template
X409138FOVNST409the dead-source move had not started
X500388FOVSTP500failover could not {step}, {error}

Source: modules/fence
Count: 52

CodeHTTPMessage template
X200184FNCKCK200the label reconcile a node change asked for failed{error}, the reconcile that runs every minute retries it
X200195FNCOUT200replica {replica} of {deployment} is bound to {node}, which its {scope} rule {rule} removes
X400159FNCSET400{flag} does not apply to label value {fence}, it applies to {applies}
X400182FNCPOD400{deployment} cannot be placed as asked: {reason}
X400186FNCSHR400{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
X400187FNCRTM400{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
X400188LBLKEY400label {key} is SHC’s: it comes from {from}, so no operator sets it
X400251FNCGON400shc fence {verb} is gone: {replacement}
X400253CNSCOP400--scope {scope} is not a constraint scope, the scopes are cluster, tenant and deployment
X400254CNSFIT400scope {scope} does not fit its target: {why}
X400260SELNAM400selector name {name} must be 1 to 63 of a-z 0-9 . _ - starting with a letter or digit
X400261SELSCP400selector scope {scope} {problem}
X400265SELEMP400a node selector is empty
X400266SELGRP400a node selector cannot use a grouped place
X400267SELVIS400selector {name} names {place}, which is not visible here
X400268SELCYC400selector {name} names itself
X400269SELGON400shc selector {verb} is gone: {replacement}
X400298FNCFIT400{deployment} cannot be placed: service {service} requests {request} {resource}, larger than every node; largest node capacity is {capacity} {resource}{quota}; nothing was written
X403163RULGLB403a constraint at {scope} needs platform:manage; a tenant’s tenant:manage covers that tenant and its deployments
X403197GRNOUT403label value {label} is reserved for {grant}, and tenant {tenant} is outside that grant: {rule} is refused
X403261SELAUT403{what} needs platform:manage, a tenant selector needs tenant:manage in that tenant
X404153FNCNOF404label value {fence} not found, shc label ls --all lists every label value
X404154FNCNOD404node {node} not found, shc node ls lists the nodes
X404161RULNOF404constraint {id} not found, shc constraint ls lists the constraints
X404164FNCDEP404deployment {deployment} not found, name it as -t -e
X404260SELNOF404selector {name} not found
X409155FNCORG409label value {fence} is {origin}, {verb} applies to {applies}
X409156FNCRUL409label value {fence} is named by constraints, remove them first: {rules}
X409157FNCSTR409{verb} would strand running deployments outside their eligible set: {strands}, move or drain them first
X409171FNCEMP409no node can take {deployment}: {steps}
X409172FNCNOD409{node} is outside the nodes {deployment} may run on: {steps}; shc update --where relocates it, after showing the plan
X409173FNCRCV409shc recover lands {deployment} on {node}, and its rules leave {node} out: {rules}; nothing was installed, replace them and run the recover again: {commands}
X409174FNCARC409shc recover lands {deployment} on {node}, and the rule its archive carries, where {rule}, leaves {node} out; nothing was installed; nodes the rule keeps: {nodes}
X409177FNCCPE409removing {nodes} would empty the control-plane label, add the nodes that take over first
X409179PLCPND409{deployment} is pending, no node fits it now: {nodes}{quota}; nothing was installed, shc constraint explain shows each node{instead}
X409180FNCMOV409{deployment} runs on {current}, and this request would put it on {node}; a rule change relocates a deployment: shc update --where
X409183FNCNDY409no 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
X409184FNCSEP409{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
X409185FNCSHR409{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
X409192LBLMOV409the labels of {node} changed while this request ran, nothing was written; run it again
X409199GRNOUT409label value {label} cannot be reserved for {grant} while deployments outside the grant name it, clear those constraints first: {outsiders}
X409255CNEMPT409where {expr} at {scope} leaves no node{deployments}{hint}
X409256CNSCHG409constraints changed while this was being set; run it again
X409262SELLOC409selector name {name} is a location a node is in
X409263SELSHD409selector {name} is already defined at {where}
X409264SELCON409selector name {name} is a connection
X409265SELCHG409node selectors changed while this one was being written; run it again
X409269SELUSE409selector {name} is named by {users}, remove them first
X500165FNCSTO500label index {op} failed {error}
X503185FNCLDR503the label reconcile runs on the leader, and {reason}; the reconcile that runs every minute converges the label index
X507294FNCROM507{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
X507318FNCDSK507{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

CodeHTTPMessage template
X400213HUDFAB400interactive form cancelled
X500214HUDFRN500interactive form failed, {error}

Source: modules/forward
Count: 9

CodeHTTPMessage template
X400084INVSRN400invalid service name {name}
X400086EMTFWD400empty forward specification
X400088FWDPRT400invalid port {port}
X400089FWDPRR400invalid port {port}, must be 1-65535
X400090FWDFMT400invalid forward specification format {spec}
X400091FWDINF400cannot infer port for service {service}, {detail}
X400910FWDREQ400forward requires {reason}
X400911FWDOLD400{spec} is the retired spelling, write {now}
X500910FWDOPF500forward operation failed {reason}

Source: modules/freeze
Count: 5

CodeHTTPMessage template
X500792FRZSTO500the placement freeze state could not be {op}: {error}
X503790FRZMOV503automatic moves are frozen since {since}: {reason}
X503791FRZEXP503the leader acts on no lease expiry: {reason}
X503793FRZRAT503no automatic move may start now: this minute’s automatic moves are spent; it is tried again on the next pass
X503798FRZLDR503no 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}

Source: modules/health/reconcile, modules/health
Count: 20

CodeHTTPMessage template
X200046NODCRW200node {node_id} certificate warning, {reason}
X200506OTLPST200managed 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
X200507OTLPDG200managed 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
X200924RSTRMT200deployment {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
X200933SYSDWN200module {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
X400060HLTNDA400no dial address
X409903PRTCNF409port {port}/{protocol} is already allocated to another deployment
X409932CPSFOL409control-plane snapshot refused on {node}, {leader} leads the cluster and the snapshot is taken on the leader; run it on {leader}
X500507OTLDIW500failed to write managed OTLP config drop-in {path} at {stage} {error}
X500932CPSFAI500control-plane snapshot on {node} failed, {reason}
X503014NODNAV503node {node_id} unavailable
X503050HLTNID503node health probe identity mismatch, got {got_id}, want {want_id}
X503058SNPCFG503control-plane snapshot in cluster mode with no cluster-dump port wired
X503060HLTNCK503no health checker wired
X503061NODNVS503node {node_id} still unavailable, {suppressed} checks suppressed over {unavailable_for}
X503064DBVSKP503db vacuum skipped, {reason}, freed pages are never returned to the filesystem
X503092NODCRT503node {node_id} certificate critical, {reason}
X503119HLTCSK503health 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
X503932CPSLDR503control-plane snapshot refused on {node}, {reason}; the snapshot is taken on the leader
X503932CPSNWR503control-plane snapshot refused on {node}, no snapshot directory or database dump is wired on this node

Source: modules/inspect
Count: 2

CodeHTTPMessage template
X400910INSREQ400inspect requires a stack name
X500910INSDSP500inspect display failed {op}{error}

Source: modules/internal_rpc
Count: 35

CodeHTTPMessage template
X400186RPCFRM400malformed rpc frames {detail}
X400977RPCJSN400malformed rpc request body {detail}
X400978RPCFNM400missing rpc function name
X400979RPCRDF400rpc body read failed {detail}
X403192TRFPER403transfer {handle} was issued to another node
X403193TRFMSH403the transfer route answers only on this node’s mesh address, not {local}
X403227RPCJTR403join {function} answers only on the public listener, not on {transport}
X403282RPCPCT403the peer status port answers only a caller with a verified cluster node certificate
X403945RPCTRN403rpc {function} requires the internal mTLS listener, got transport {transport}
X403946RPCCAP403rpc {function} requires capability {capability}, which this caller was not granted
X404183RPCUNK404unknown rpc function {function}
X404191TRFUNK404no transfer {handle} is staged on this node
X404240RPCJNF404no join function {function}
X404281RPCPNF404no peer status function {function}
X410190TRFEXP410transfer {handle} has expired
X410290RPCFLW410rpc {function} has no followed call {call} on this node: the node restarted since the call began, or its answer expired
X413147RPCBND413rpc {function} carries at least {size} bytes of transfers, past the {bound} it may make this node pull; nothing was pulled
X413188TRFSIZ413transfer payload grew past its declared {declared} bytes
X413900RPCBIG413rpc body exceeds the {limit}-byte cap
X416198TRFRNG416range {range} does not fit a {size}-byte transfer
X429228RPCJRL429join requests from {source} are over the limit, try again in {wait}
X429280RPCPRL429peer status requests from {source} are over the limit, try again in {wait}
X500185RPCBLB500rpc {function} carries binary data but {detail}
X500196TRFIOE500transfer {op} failed: {detail}
X502184RPCENV502rpc {function} to {addr} returned an unreadable reply: {detail}
X502194TRFSUM502transfer {handle} arrived with sha256 {got}, not the {want} its holder reported
X502199TRFPUL502pulling transfer {handle} from {addr} failed: {detail}
X503182RPCBSY503rpc busy: {peer} already has {in_flight} calls in flight on this node, retry after {retry_after_ms} ms
X503189TRFBSY503transfer busy: the {class} queue {detail}, retry after {retry_after_ms} ms
X503195TRFKEY503transfer data key unavailable: {detail}
X503197TRFOFF503no transfer store is open in this process
X503220RPCOPN503{what} to {addr} was not sent: the peer’s circuit is open after repeated failures, retry after {retry_after_ms} ms
X503229RPCJSG503the answer to join {function} cannot be signed: {detail}
X504292RPCFLL504rpc {function} on {addr} is followed for its answer, and the node did not answer for {budget}: {detail}
X507187TRFQTA507transfer staging refused: {size} bytes would exceed {limit} ({detail})

Source: modules/job
Count: 26

CodeHTTPMessage template
X200005JOBFAL200job {job_name} failed during {phase} {error}
X200074JOBTHR200registry pull rate limit for job {job_name}, retrying in {delay}
X200557JOBSLO200job {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}
X400010INVJOB400invalid job definition with {detail}
X400011JOBMNG400job {job_name} is a {source} job and cannot be run directly
X400015JOBPRS400job template parse failed, {reason}{token}
X400027JOBREQ400{field} field is required for {context} context
X400028JOBSNS400job {job_name} declares sensitive_output and runs in {context} context, where its stdout is a container log; run it in service context
X400029HKSENS400job {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
X400065JRNTSK400job run {job_run_id} has no task yet with status {status}, nothing to cancel
X404001JOBNFD404job {job_name} not found in stack {stack_name}
X404004JOBSTK404deployment {stack_name} is not on this node, job {job_name} cannot be loaded
X404077JOBREP404this node holds no replica of deployment {deployment}, so job {job_name} has no project to run in
X404904JRNFND404job run {job_run_id} not found
X409066JRNTRM409job run {job_run_id} already {status}, nothing to cancel
X409067JRNRUN409job run {job_run_id} is executing, cannot cancel
X409068JRNCLM409job run {job_run_id} was claimed for execution before the cancel landed
X409077JOBENT409job {job_name} cannot run as compose service {service} in replica project {project}, that name is one of the replica’s entries
X499075JOBCAN499{command} was killed after {elapsed}s because the caller cancelled the run, not because the job’s timeout expired
X500900JOBOPF500job {operation} failed{error}
X500901JOBNET500job network inspect failed for {network}{error}
X503078JOBREM503job {job_name} in project {project} was interrupted, the replica it ran in was removed from this node, retry the job
X503919JOBSEL503job {job_name} declares sensitive_output and the vault on this node can’t seal its output; unlock the vault and run it again
X504075JOBTMO504{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
X504319JOBUPT504job {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}
X504556JOBSTL504job {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

CodeHTTPMessage template
X400400KVINPT400kv invalid input {reason} {error}
X404400KVNOFD404kv entry {namespace}/{key} not found
X500401KVOPFL500kv {operation} failed

Source: modules/labelcheck
Count: 3

CodeHTTPMessage template
X400452LBLCHK400service {service} live label {key} is refused: {reason}
X400454ALSDCL400service selector {service_selector} is refused: {reason}
X403453LBLNOD403live labels for node {node} are reported only by that node itself, the caller presented {caller}

Source: modules/leader
Count: 5

CodeHTTPMessage template
X200923LDRCBK200leader {callback} callback failed {error}
X503017LDRNOB503no node-health observer is wired on this node
X503019LDRNOL503node health is observed by the cluster leader only; this node is not currently the observing leader
X503021LDRSTL503the node-health walk has no observation newer than {window} for {count} of {expected} known nodes: {nodes}
X503044LDRNRG503the cluster registry lists no nodes for the node-health walk to observe

Source: modules/license
Count: 39

CodeHTTPMessage template
X200937LICCHP200could not publish the estate licence-challenge key, {reason}, automatic licence checks stay node-local until it lands
X200938LICCHM200could not materialise the estate licence-challenge key, {reason}, this node loses its offline copy until the state dir is writable
X200961LICGOK200join-time capacity gate enforced for node {node}, {nodes} nodes and {cores} cores measured against {caps}
X200997LICDRP200the 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
X200998LICOFF200no broker ask was made, network license checks are disabled by the license.offline policy, install a vendor-signed file with shc license install <file>
X400152LICWKR400workshop 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
X400750LICFORM400{form} is gone, use {replacement}
X400968LICMAL400license file malformed, {reason}
X400969LICSIG400license signature is invalid, it is not signed by the vendor key this binary trusts
X400970LICKEY400minting requires the vendor Ed25519 signing key via --key or SHC_LICENSE_SIGNING_KEY. Mint is vendor-only
X400971LICNAF400license file not found at {path}
X400972LICREQ400vendor record request rejected, {reason}, fix the invoice and re-sync, this request will never succeed as sent
X400973LICCAP400purchased capacity {cores} cores exceeds the {ceiling}-core ceiling for tier {tier}. Quote this as Enterprise, or raise the broker’s ceiling
X403029LICENT403{feature} is not included in this estate’s SHC license. Activate or renew a license that includes it, see shc license status
X403030LICDOM403license is bound to domain {expected} but this estate serves {actual}
X403031LICLIM403license 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
X403032LICDNS403activation callback for {domain} failed the public-DNS leg, {reason}
X403034LICNCE403activation callback for {domain} failed the challenge-nonce leg, {reason}
X403035LICGRT403no license grant on record for domain {domain}. Complete a purchase for this domain, then re-run activation
X403036LICOPT403{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
X403037LICOFF403{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 , the current license expires {expires}
X403039LICCAP403this 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
X403040LICENC403cluster enrollment refused, missing or invalid enrollment code, POST /register requires the code the vendor issued as a bearer token
X403041LICENR403cluster enrollment refused for {domain}, {reason}
X403042LICZON403a licence record was found at {record} but does not apply to this estate, {reason}, check the _shc-license TXT value for this domain
X403043LICUNB403the 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
X403044LICCRT403a 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
X403045LICPTL403portal request refused, missing or invalid portal credential, the portal’s routes require the broker’s LB_PORTAL_TOKEN as a bearer token
X403048LICVND403vendor mint refused, missing or invalid vendor token, POST /mint is vendor-only and requires the broker’s LB_VENDOR_TOKEN as a bearer token
X403150LICWKS403workshop request refused, missing or invalid workshop credential, POST /workshop requires the broker’s LB_WORKSHOP_TOKEN as a bearer token
X409941LICSUP409the 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
X500158LICWKA500workshop route not armed, {reason}, POST /workshop stays disabled until the broker’s workshop settings are corrected
X500960LICSGN500license signing failed, {reason}
X500961LICSTO500license store operation failed, {reason}
X502960LICBRK502online license activation failed, {reason}, use the offline signed-file path for airgapped estates
X502961LICMNT502license mint failed after a verified activation callback, {reason}, retry activation, and contact the vendor if it persists
X502962LICRFR502license re-fetch from the broker failed, {reason}, entitlements continue resolving from the locally held file
X502963LICREC502writing 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
X503964LICGSK503join-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

CodeHTTPMessage template
X400133LOGRTM400logs runtime {runtime} is not supported
X400940LOGREQ400logs requires a stack name: pass --stack, rely on ctx fallback, or use --all
X400941LOGDUR400invalid since value {since}
X400942LOGTAL400invalid tail value {tail}
X403944LOGSCM403permission denied, missing stack {stack} read
X404940LOGNOF404no log target for project {project} service {service}
X500940LOGRUN500log retrieval failed {op}{error}
X500941LOGSTM500log stream failed {op}{error}

Source: modules/mcp
Count: 4

CodeHTTPMessage template
X400381MCPHDR400the mcp endpoint needs the token in the Authorization header, a query-string token cannot open a session
X500379MCPCTX500mcp tool call carried no per-call auth context, so SHC refuses to execute without the calling principal
X500380MCPPAN500mcp loopback dispatch panicked, {panic}
X503378MCPNRT503mcp daemon api router not ready, {reason}

Source: modules/mesh
Count: 50

CodeHTTPMessage template
X200591MSHRLY200mesh relay: {a} and {c} on {device} have no reachable relay, {reason}
X400562MSHTRQ400mesh trial request refused, {reason}
X400571MSHKEY400mesh0 key for {holder} is unusable, {reason}
X400572MSHADR400mesh0 address {address} is unusable, {reason}
X400582MSHSNP400the peer table snapshot is malformed, {reason}
X400596MSHPNT400mesh punch instant {at} is outside the allowed window
X400604MSHRLA400mesh 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
X400811MSHROT400key rotation is refused: {reason}
X403563MSHTRC403mesh trial refused, the caller is not node {from}
X403581MSHSIG403the signed peer table is refused, {reason}
X403590MSHAUT403peer table request refused, {detail}
X403592MSHRLC403mesh relay: {caller} may not set the relay of {a} and {c} on {device}
X403594MSHPNC403mesh punch: caller or owner proof is invalid
X403597MSHRCF403a 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
X403812MSHAUT403key rotation requires the caller’s node leaf identity
X404576MSHNOP404node {node} has no mesh0 address recorded
X404579MSHNCL404no operator client {client} is on mesh0
X409561MSHTRY409this node is busy with a trial on {device}, try again in a few seconds
X409564MSHTRB409this node cannot take part in a trial on {device}, {reason}
X409578MSHKND409mesh0 row {id} is a {have}, not a {want}
X409580MSHSTL409the store does not hold what this node’s mesh0 was last built from, {reason}; mesh0 stays as it is
X409583MSHGEN409the offered peer table is {offered}, this node holds {held} and keeps it
X409584MSHEXP409the offered peer table, {pair}, expired at {not_after}
X409585MSHFLT409two peer tables carry {pair} with different rows, held {held}, offered {offered}; this node keeps the one it holds
X409587MSHUNR409this node cannot take up the peer table it has stored, {reason}; it takes no other table until that one reads again or is reset
X409588MSHERA409the peer table’s era moved since the preview, it was {from} and is {held}, so nothing was written
X409593MSHRLO409mesh relay: relay selection is off on {node} for {device}
X409595MSHPNR409mesh punch refused: {reason}
X409603MSHRLG409mesh relay: {a} and {c} on {device} already hold another decision at generation {generation}
X409605MSHRLE409mesh relay: {node} reaches {a} or {c} on {device} through a relay itself, so it cannot relay them
X409607MSHRLH409mesh relay: {node} holds another generation than {generation} for {a} and {c} on {device}
X409810MSHBUS409a key rotation is already open for node {node}
X409813MSHHOF409node {node} must hand raft leadership to another voter before rotating mesh0
X409815MSHLAG409no shc0 key rotation starts while a member is on a release that takes no part in one: {nodes}
X500560MSHTRN500the trial rule on {device} could not be deleted, {reason}
X500573MSHFUL500mesh0 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
X500574MSHREP500mesh0 peer repository error {op}{error}
X500575MSHCAC500mesh0 local state error {op}{error}
X500586MSHSGN500the peer table could not be signed, {op}{error}
X500608MSHRLW500mesh relay: {node} cannot sign a decision for {a} and {c} on {device}, it is not their owner or its owner signer is not wired
X503577MSHOFF503this node is not on mesh0, so it cannot admit a node to it; enrol against a Linux member whose mesh0 is up
X503588MSHGWY503this gateway holds no operator client, the rules that keep a client to the public API listener did not converge{error}
X503589MSHLDR503no leader can be reached to confirm the restored peer table, {reason}
X503591MSHSRV503peer table unavailable, {detail}
X503592MSHGET503peer table recovery failed, {detail}
X503601MSHRLS503mesh relay: node {node} has no relay session
X503602MSHRLD503mesh relay: {node} has no direct path to {a} and {c} on {device}
X503606MSHRLP503mesh relay: {node} has no handshake source for {device}
X503814MSHROT503key rotation is waiting: {reason}
X504816MSHACK504key rotation did not switch: node {peer} has not installed the pending key

Source: modules/metrics
Count: 7

CodeHTTPMessage template
X404920METNOF404metrics no definition for {name}{want}{error}
X500920METREG500metrics duplicate registration for {name}
X500921METINI500metrics failed to create {kind} instrument {name} {error}
X500922METCAR500metrics cardinality cap exceeded for {name}, {observed} > {cap}
X500923METNEG500metrics withheld impossible gauge {name}={value} for node {node_id}: this quantity cannot be negative
X500924METATT500metrics withheld node {node_id} commitment: {axis} {observed} is not the {expected} attributed to that node
X503120METTSK503metrics 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

Source: modules/network
Count: 1

CodeHTTPMessage template
X500900NOTWRD500network service is not wired with a database

Source: modules/node/commands, modules/node
Count: 24

CodeHTTPMessage template
X400061NODHDA400node health dial address empty
X400307NODPRN400usage shc node prune … | --all [--dry-run]
X400899NODARG400usage shc node {cmd} <{arg}>
X400911NODNOA400node {name} has no address configured
X400915NAMVAL400{field_name} validation failed {reason} {error}
X400932NODTTL400invalid ttl {value} {error}
X400933NODTTP400invalid ttl {value}, must be positive
X400934NODPRGS400node leave --purge is self-only, run it on the node you want to wipe without a [node] argument
X400935NODPRGF400node leave --purge permanently destroys all local SHC state and data, re-run with --force to confirm
X403459NODIFU403the running operations answer on this node’s unix socket only
X403936NODUNA403node {node} is removed only at the word of the leader or a live voter, the caller presented {caller}
X403938NODPSU403the pre-stop hook answers on this node’s unix socket only
X404003NODNOF404node {name} not found
X500019NODINI500local node not initialized, {path} missing, run shc init or shc node join first
X500899NODREPO500node repository error {op}{error}
X500923HTTPST500http {status} {body}
X500924UNMRSH500unmarshal response {error}
X503072NODHPF503node {addr} health probe failed {error}
X503073NODHCN503node health client not configured
X503074NODMIPF503mesh ip pool {cidr} is full
X503075NODMIPC503mesh ip allocation contended for node {name}
X503934TKNDMN503cannot 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
X503937NODUNU503node {node} removal cannot check its caller, {reason}
X503998CMDNYI503not yet wired in Go port {operation}

Source: modules/nodeagent
Count: 24

CodeHTTPMessage template
X200695NAGRST200the node agent restarted {container} of {project} by its restart policy {policy}
X200711NAGROM200pass over {deployment} on node {node} waits for room: passes over {running} run
X200773NAGTKN200the node agent could {what} after it failed {tries} since {since}
X200774NAGTKG200the node agent no longer owes the takedown to {what}, which failed {tries} since {since}: the copy is gone or placed here again
X200826NAGKEP200the node agent could not keep the completed services of this node on disk, {error}; after shcd restarts each runs once more
X409689NAGSTP409{tenant}/{environment}/{stack} was stopped by its operator, so its containers are not started until it is started again
X409696NAGNAS409{tenant}/{environment}/{stack} is not assigned to this node, so its containers are not started here
X409699NAGLLS409a 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
X409700NAGSPC409{replica} of {tenant}/{environment}/{stack} was rendered as {got} and the stored spec renders it as {want}, so this node does not start it
X409708NAGREP409{replica} of {tenant}/{environment}/{stack} is not bound to this node, so it is not started here
X409710NAGSPL409{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
X409712NAGMOV409{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
X409796NAGHLD409a stopped backup of {tenant}/{environment}/{stack} holds its starts
X500694NAGSTA500the node agent could not start containers of {project}: {error}
X500766NAGPRJ500the node agent could not converge this node’s replica projects: {error}; it tries again on its next apply
X500771NAGTKD500the node agent could not {what}: {error}; it has failed {tries} since {since} and the boot gate stays closed on it until it is quarantined
X503693NAGGAT503the node agent’s boot gate is closed, it is waiting for {waiting} and starts nothing until then
X503697NAGLSE503this node’s lease for this boot is not live, so a writer of {tenant}/{environment}/{stack} is not restarted here
X503698NAGUNB503{tenant}/{environment}/{stack} is not bound to any node yet, so its containers are not started until the scheduler binds it
X503709NAGSTU503the runtime’s record of whether {container} of {project} was stopped on request could not be read, so it is not started until it can
X503765NAGWAI503the node agent left replicas of this node unstarted, each waiting: {waits}; it tries again on its next apply
X503767NAGOWN503{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
X503770NAGRET503the node agent could not return against the stored assignments: {error}, so the boot gate stays closed
X503772NAGQRN503the 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

Source: modules/nodelease
Count: 19

CodeHTTPMessage template
X200746NLSMIS200node {node} lease renewal was not acknowledged, retrying in {retry}: {error}
X200747NLSPRS200node {node} could not record its pressure level {level}: {error}
X200756NLSVLT200node {node} could not record that its vault is {state}: {error}
X200844NLSMEM200node {node} could not record its measured memory: {error}
X200852NLSPOL200node {node} could not record its pool’s free space: {error}
X403758NLSIDN403node {node} lease is renewed only by that node itself, the caller presented {caller}
X409743NLSEPC409node {node} has seen liveness epoch {seen}, newer than the answering leader’s {epoch}
X409745NLSDEP409the liveness term moved past epoch {epoch}, this node no longer leads node liveness
X500678NLSRED500node leases could not be read: {error}
X500744NLSTRM500the liveness term could not be {op}: {error}
X500755NLSEXP500the 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}
X500757NLSVRD500node vault states could not be read: {error}
X500845NLSMRD500node measured memory could not be read: {error}
X500851NLSPRD500the nodes’ pools could not be read: {error}
X503676NLSSTO503node lease {op} has no store yet, the daemon has not opened the control plane
X503727NLSVRC503node {node} could not record that its vault is {state} before placement read it, so nothing was placed: {error}
X503741NLSLDR503node {node} renewed its lease with a node that does not lead node liveness
X503742NLSQRM503the liveness leader last proved its quorum {age} ago, so it acknowledges no renewal
X503748NLSHLD503node {node} renewal is held, {why}

Source: modules/notification/channels, modules/notification
Count: 14

CodeHTTPMessage template
X400115NTFPTN400at least one pattern is required
X400700NTFPTN400invalid pattern {pattern} {error}
X400701NTFCFG400invalid notification rule {context} {error}
X400703NTFCHC400notification channel field {field} is empty
X400711NTFTMP400notification template is invalid {issue} {detail}
X429707NTFTST429notification rule {rule} was tested less than {interval} ago, test it again in {retry}
X500701NTFSND500notification send failed {label} {error}
X500702NTFDRP500notification dropped for rule {rule}, dispatcher not running {events}
X500704NTFTPL500notification template {stage} failed {error}
X500705NTFHTP500notification webhook returned HTTP {status}
X500706NTFSND500unknown notification send failure
X503011QUEFUL503notification queue full, dropping rule {rule} {events}
X503012NTFRSK503notification rule {rule} skipped at dispatch {reason}
X503013NTFDSF503notification dispatch send for rule {rule} failed {error}

Source: modules/otelrelay
Count: 12

CodeHTTPMessage template
X400108OTRSIG400{signal} is not a signal the telemetry relay carries, which are metrics, traces and logs
X400111OTRBDY400the relayed export has no usable body, {detail}
X400113OTRORG400the telemetry relay sends only exports for its own origin, and {request} is not one
X409115OTRMOV409{node} does not hold openobserve, {holder} does, and the sender reads the holder again
X502109OTRFWD502the relayed {signal} export did not reach openobserve, {detail}
X503107OTRNOH503no node holds {deployment}, so this node’s telemetry has nowhere to be relayed
X503110OTRDST503this node holds openobserve but has no address for its replica, {detail}
X503112OTRCRD503this node holds openobserve but its vault gives no openobserve credential yet, it is locked or the credential is not minted, so relayed exports wait
X503114OTRNWR503the telemetry relay is not wired yet, the daemon has not opened its control plane
X503118OTRDOR503the node collector’s relay door did not open on {addr}, {detail}, so this node’s container logs and host metrics reach no store
X504116OTREXP504the relayed {signal} export waited five minutes without reaching openobserve and was dropped
X507117OTRFUL507the telemetry relay queue was full, so its oldest {signal} export was dropped

Source: modules/pods
Count: 50

CodeHTTPMessage template
X200729PODEHL200early 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
X200729PODPAS200pass 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
X200749PODLFT200replica project {project} was taken down on this node, {why}
X200760PODHCW200replica project {project}‘s healthcheck could not be read, the replicas that wait for it to be healthy wait {wait}: {error}
X200769PODOFF200replica projects are off on node {node}: {why}
X200772PODONN200node {node} runs every deployment as replica projects
X200777PODBRK200deployment {deployment} cannot be projected, its previous projection is kept if present: {reason}
X200778PODHLD200replica {replica} has no vault document, its containers and previous materialised state are kept
X200779PODPKF200the app files of archive digest {digest} were not placed on this node: {why}
X200793PODLKR200the 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}
X200797PODKEP200replica project {project} is kept running on this node, its replica is bound to node {node} where it reads {state}, not ready
X400755PODRUN400replica projects cannot run on this node, {what}
X400760PODSPC400replica project {project} is not started, this node cannot make what it names: {error}
X400766PODRFS400replica {replica} of deployment {deployment} cannot start on node {node}, its runtime refuses it at every start: {refusal}
X400775PODAMB400the argument {service} is ambiguous between service {service} and replica {ordinal} of service {member}
X404757PODUNK404this node holds no replica project {project}
X404762PODSVC404service {service} of deployment {deployment} is in no replica project on node {node}, so there is no pod to act on
X404763PODNON404deployment {deployment} has no replica project on node {node}, so nothing was acted on
X404781PODNSV404service {service} is in no replica project of deployment {deployment}, so there is no pod to act on. Services in its replica projects: {services}
X409751PODREP409the replica project at {dir} is refused, {why}
X409752PODDIG409replica project {project} is refused, its compose document is not the one its replica record’s digest {want} seals: {error}
X409754PODVOL409replica project {project} is not started, its durable volume {volume} is missing on this node and only the replica’s first bind creates it
X409758PODUNB409replica project {project} is not started, the assignment store does not bind it to node {node}
X409761PODWHL409{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
X409767PODDIR409{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
X409773PODSTP409replica project {project} is stopped by the operator, shc start runs it again
X409776PODNOD409replica project {project} is bound to node {bound}, not this node {node}
X409778PODMOV409replica project {project} refuses volume {volume}: row moved marker {row} differs from volume moved label {label}
X409780PODOLD409deployment {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.
X409783PODCRS409replica {replica} of deployment {deployment} on node {node} failed {times} in {window} without reading ready once: {entry} exited {exit}{last}
X409784PODEND409{entry} exited {exit}, and its restart policy no never starts it again
X409785PODFIN409replica {replica} of deployment {deployment} failed on node {node} and nothing starts it again: {reason}
X409792PODJNR409replica 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
X500756PODSEC500the stored replica {replica} cannot be written to clusterfs, {why}
X500759PODIOE500replica projects {op} failed: {error}
X500765PODRAM500replica projects are not materialised at {dir}, nothing was written: {why}
X500770PODRES500replica {replica} was not materialised, its entry was not resolved: {error}
X500774PODWRT500replica {replica} was not materialised, {op} failed: {error}
X501782PODFRZ501deployment {deployment} cannot be paused or thawed on node {node}: its runtime has no freeze
X503750PODDIR503the node’s replica projects could not be read at {dir}, nothing was started or taken down: {error}
X503753PODAFT503replica project {project} waits, {waits}
X503764PODWAI503replica projects of deployment {deployment} on node {node} are not started yet, they wait: {waits}
X503768PODPND503{op} of {target} waits: this node has not decided yet whether it runs every deployment as replica projects ({why}); retry once it has
X503771PODCFS503replica {replica} of deployment {deployment} is not started on node {node}, the node’s clusterfs does not build and the replica never reaches it: {why}
X503786PODSED503replica {replica} of deployment {deployment} is not started on node {node}, its volume cannot be seeded from its image: {seed}
X503787PODPUL503replica {replica} of deployment {deployment} is not started on node {node}, the pull of its images failed there: {pull}
X503790PODBSY503{op} gave up after waiting {waited} for this node’s replica runner, busy with {holder}
X504720PODPNW504{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
X504798PODSET504deployment {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}
X504799PODPLS504the images of deployment {deployment} are still being pulled and no pull of them ended in {stall}: {pulls}

Source: modules/portal
Count: 45

CodeHTTPMessage template
X400141PTLCOD400invalid portal registration code, {reason}
X400142PTLURL400invalid portal.url {value}, it must be an absolute http or https url
X400148PTLDOM400this 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
X400477PRTRNG400invalid portal.federation {value}, it is federated, registrant or sealed
X400478PRTREQ400the portal exchange is malformed, {reason}, nothing was executed
X400488PRTCOD400the registration exchange was refused, {reason}, mint a fresh code in the portal because codes are single-use and short-lived by design
X400497PRTGRT400invalid store grant {entry}, each entry is <tenant>/<environment> in lowercase and the master tenant is never a store target
X401479PRTSIG401portal directive signature did not verify, {reason}, refusing to execute anything the vendor cannot be proven to have sent
X401514PRTBRR401the portal userinfo relay takes one bearer token in the Authorization header and this request carried none it could use
X401516PRTUIA401the portal did not accept this sign-in’s token, so start the sign-in again
X403140PTLOFF403the portal registration agent is disabled, portal.enabled is off by default
X403146PTLUDS403portal registration runs only over the daemon host’s own socket, run shc portal register as root on a node
X403147PTLROO403run as root on the daemon host
X403480PRTVRB403portal 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
X403487PRTAUD403portal directive {dispatch} is addressed to cluster {addressed}, and this cluster is {actual}, so SHC refuses it
X403491PRTUNR403portal 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
X403492PRTREQM403portal directive {dispatch} claims install request {request} but does not match it, {reason}, SHC refuses it
X403494PRTEDG403{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
X403496PRTGNT403store installs into {target} are not granted on this cluster, an operator allows them by adding that target to portal.store_grants
X403510PRTLIM403{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
X403515PRTSLD403portal.federation is sealed on this cluster, so the portal userinfo relay refuses every sign-in
X403517PRTUID403the portal refused this person a sign-in here, only a registrant, owner or admin of the org that owns this cluster signs in
X404484PRTNRG404this 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
X409481PRTDUP409portal 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
X409483PRTREG409this estate is already registered with {portal} as cluster {cluster}. Deregister first with shc portal deregister if you mean to move it
X409498PRTEXS409store install of {app} into {target} would replace the deployment {deployment} that already runs there, and a store install only creates
X409507PRTSEQ409portal limits {dispatch} carry seq {seq}, and this estate already applied seq {applied}, so SHC keeps the newer caps and changes nothing
X409511PRTLNK409store 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
X409513PRTGON409installer {email}, subject {subject}, is no longer a user of tenant {tenant} with that email, so nobody was granted the deployment its held install made
X409519PRTKCO409this 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}
X410482PRTEXP410portal 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
X410493PRTOPG410portal install {dispatch} lost operation {operation} before it reported an end, {finding}
X500489PRTKEY500the estate’s portal agent key could not be {action}, {reason}
X500540PRTFLT500portal directive {dispatch} failed on this estate and the portal was told only that it failed, {cause}
X502143PTLHTT502portal request failed, the portal answered http {status}, {body}
X502144PTLTRN502portal request failed in transport, {error}
X502486PRTCHN502the portal channel round trip failed, {reason}, the estate is unaffected and the agent will retry with backoff
X502518PRTUIF502the portal userinfo relay got no usable answer, {reason}, so this sign-in stops here
X503145PTLNYI503the portal outbound channel is not wired in this build yet, {piece}
X503149PTLINI503this node has no shc daemon yet, run shc init first, or shc node join <token> to join a cluster, then run this again
X503476PRTKCD503the 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
X503485PRTNRT503this 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
X503490PRTVLT503the 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
X503499PRTDPL503could not read this estate’s deployments to confirm {target} gets a new install, {reason}
X503512PRTUSR503could not read the users of tenant {tenant} from this estate’s user service, {reason}

Source: modules/portforward
Count: 7

CodeHTTPMessage template
X403924FWDTGT403port-forward target {service}:{port} is not a port stack {stack_name} publishes or exposes
X403926FWDOWN403the container answering for {stack_name}/{service} is not owned by that deployment
X403927FWDADR403the container answering for {stack_name}/{service} has no container network address to forward to
X404921FWDCNT404port-forward target {container} not found or unreachable from host
X429923FWDLIM429too many open port-forwards for {scope}, past the limit of {limit}; close one and retry
X503922FWDSCT503socat is required to port-forward containers without a host-reachable address but is not installed, run apt-get install -y socat on this node
X503929FWDENG503the container engine on this node could not list the containers of {stack_name}, {detail}

Source: modules/privilege
Count: 2

CodeHTTPMessage template
X403983PRVGNT403tenant {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
X403990HSTGNT403deployment {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

CodeHTTPMessage template
X200940PRXNBK200no live backend nodes while {intents} deployments ride external load balancers, leaving every lb target set unchanged this tick
X200979PRXDUP200shared-vip proxy connection {conn} port {port} claimed by both {first} and {second} in tenant {tenant}, first claim wins this sweep
X200983PRXHOL200proxy 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
X200984PRXSTL200load balancer {conn} VIPs for {tenant}/{stack} served stale as {vips}, the leader cannot be asked: {error}
X400972PRXUNK400unknown proxy implementation {impl} for tenant {tenant}
X400973PRXCFG400proxy backend {impl} misconfigured, missing connection cred {field}, {remedy}
X400974PRXLBZ400load 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}
X400975PRXADR400connection {conn} does not hold address {address}, it holds {addresses}
X400978PRXNET400network {network} of connection {conn} is of type {type}, a publish needs a bridge
X400981PRXPPU400proxy.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
X409976PRXHLD409address {address} of connection {conn} is held by {holder}
X409977PRXFUL409all {count} addresses of connection {conn} are held
X500970PRXRCN500failed to reconcile proxy for tenant {tenant} connection {conn} {op} {error}
X503971PRXNWR503proxy backend not available for tenant {tenant} connection {conn}
X503984PRXLDR503load balancer {conn} VIPs for {tenant}/{stack} not read from the leader, {reason}{error}

Source: modules/purge
Count: 3

CodeHTTPMessage template
X400940DBPRGB400invalid --before value {value}, expected a relative interval like 30d or a date like 2026-08-01
X403940DBPRGA403purging audit records requires the explicit audit opt-in
X500940DBPURG500control-plane purge failed {op} {error}

Source: modules/quota
Count: 20

CodeHTTPMessage template
X400915QTAINP400invalid quota input {reason} {error}
X403001CPUEXC403cpu quota of {scope} exceeded, requested {requested} millicores but only {available} of {limit} available
X403002MEMEXC403memory quota of {scope} exceeded, requested {requested} bytes but only {available} of {limit} available
X403003DSKEXC403disk quota of {scope} exceeded, using {used} bytes of {limit} bytes limit
X403004DEPEXC403deployment quota of {scope} exceeded, {current} of {limit} deployments
X403005ENVEXC403environment quota of {scope} exceeded, {current} of {limit} environments
X403006APPEXC403app quota of {scope} exceeded, {current} of {limit} apps
X403007VDPEXC403vdeployment quota of {scope} exceeded, {current} of {limit} vdeployments
X403008DSKASK403disk quota of {scope} exceeded, {used} in use, {asked} asked, {limit} limit
X403010NODCPU403node cpu capacity exceeded, requested {requested} millicores but node {node} has only {available} millicores free after committed reservations
X403011NODMEM403node memory capacity exceeded, requested {requested} bytes but node {node} has only {available} bytes free after committed reservations
X403013SWMREP403no 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
X403508ESTAPP403app 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
X403509ESTSRV403server 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
X404909USGNOF404usage record not found for scope {key} {value}
X500909DSKSCA500disk usage scan failed with {error}
X500913USGREC500usage reconciliation failed with {error}
X500914USGOPF500usage {operation} failed
X500936QTACMT500node commitment {operation} failed {error}
X503096DSKNMS503disk usage of {scope} is unmeasured, no sweep has measured it

Source: modules/rebalance
Count: 1

CodeHTTPMessage template
X409214RBLSTL409the move of {deployment} from {from} to {to} was not made, the estate changed after the plan, {detail}

Source: modules/replicadoc
Count: 10

CodeHTTPMessage template
X400660RDCREF400replica document refused, {why}
X400661RDCENT400replica document entry refused, {why}
X400665RDCKEY400the vault key is not a document of replica {replica}
X403663RDCASN403node {node} may not read replica {replica}
X404662RDCMKY404replica {replica} cannot be checked, the cluster mac key is not in the vault
X404669RDCNOF404replica {replica} has no document at the named version
X409666RDCMAC409the document stored for replica {replica} does not match the digest in its entry
X409667RDCCOL409replica {replica} already holds a different document at this version, it was not overwritten
X500668RDCVLT500the vault could not {op} {what}: {code}
X503664RDCASG503the assignment of replica {replica} could not be read: {error}

Source: modules/repo
Count: 26

CodeHTTPMessage template
X200906REPHDM200repository {name} synced without {missed} of {total} head archives from {origins}; they kept their previous browse facts: {apps}
X400013INVURL400invalid repository url
X400702REPCFF400repository {name} cannot take its credential from {value}
X400762REPIDX400repository index {reason}; publish a v2 index with api_version: v2 and a nonempty versions list per app, without parent_app or vapp
X400927REPFIL400file-path repositories are no longer supported
X400928REPRSV400repository name {name} is reserved
X400943REPADP400unsupported adapter {adapter}
X400944REPNDL400repository url {url} is node-local and this estate has {nodes} nodes
X400946REPCST400adapter {adapter} has no public catalog to sync
X400947REPAGT400adapter {adapter} catalogs sync only from a git repository, not {url}
X400967REPSSR400repository url host {host} is not an allowed remote target
X403901REPSYS403cannot delete the system repository
X403902REPBLT403cannot remove the shipped repository
X403907REPSYW403repository {name} belongs to the system scope and only a platform admin can change it
X404901REPNOF404repository {name} not found
X404917REPLGN404repository {name} reads the pull login of connection {connection} in tenant {tenant}, and there is none
X409901REPOEX409repository {name} already exists
X409918REPREV409repository {name} is at {have} on this node but its last sync read {want}, and syncing it here failed {error}
X409987REPAMB409repository {name} exists in more than one scope ({scopes}); name one with ?tenant_name= and ?environment=
X500902REPMAT500failed to materialize source for repository {name} {error}
X500903REPSYN500failed to sync repository {name} with {reason} {error}
X500904REPOPF500repository operation {operation} failed
X500905REPGIT500git {args} failed {error} {output}
X502908REPCRD502repository {name} needs a credential and its index answered HTTP {status}
X502909REPDEN502repository {name} refused this cluster’s credential with HTTP {status}
X503917REPVLT503vault refused the credential of repository {name}

Source: modules/resolver
Count: 5

CodeHTTPMessage template
X200279RSVRCV200the 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
X500271RSVHST500could not route the private domains to the node resolver on {link}, the host keeps its own nameservers: {error}
X503272RSVBND503could not listen for DNS on {addr}, retrying: {error}
X503273RSVNAM503the node’s DNS could not take up the fabric addresses and provider names this render wrote, nothing was started: {error}
X503274RSVLOD503the node’s DNS could not load {revision} and keeps answering from the last one it loaded: {error}

Source: modules/retention
Count: 8

CodeHTTPMessage template
X400916RETINP400invalid retention input, {context}{error}
X500916RETOPF500retention {operation} failed
X500918RETARC500retention kept backup {backup_id}: its archive at {location} could not be deleted, {detail}
X500919RETRCL500retention space reclaim did not complete, {detail}
X500920RETKPT500retention for tenant {tenant_name} deleted {deleted} and kept {kept} it could not delete; what it kept stays listed and is retried next sweep
X500921RETNRS500retention cannot delete {location}: it addresses a restic repository and no restic-aware archive deleter is wired
X500922RETCAC500retention deleted backup {backup_id} but its backup_cache row remains, it will keep appearing in shc backup ls, {detail}
X500923RETBKG500retention could not remove expired group bundle {path}, {detail}

Source: modules/rollout
Count: 15

CodeHTTPMessage template
X200716RLTCNV200{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
X404139RLTNRO404{deployment} has no rollout
X409139RLTACT409the rollout of {deployment} is unfinished, so the update waits for it
X409140RLTUNS409the replicas of {deployment} run more than one spec or incarnation, so the update waits for them to settle
X409141RLTSTF409the rollback that settles the replicas of {deployment} finished with them still on more than one spec, so the update waits for an operator
X409143RLTOVR409the rollout of {deployment} is over, so there is nothing to roll back
X409144RLTSPU409the newest spec of {deployment} is staged by an operation that has not committed
X409145RLTNON409every replica of {deployment} already runs the current spec
X409724ROLVER409the rollout of {deployment} is no longer at version {version}, so the save changed nothing
X409726ROLDEP409the rollout of {deployment} was not saved: this engine was deposed, its epoch is {epoch} and the current one is {current}
X500389RLTSTP500rollout could not {step}, {error}
X500722ROLRED500rollouts could not be read: {error}
X500723ROLWRT500the rollout of {deployment} could not be written: {error}
X503132RLTNST503rollout has no store
X503721ROLSTO503rollout {op} has no store yet, the daemon has not opened the control plane

Source: modules/scan
Count: 4

CodeHTTPMessage template
X400671SCNARG400invalid scan request {reason}
X400672SCNOUT400invalid scan output {reason}
X500607SCNWRITE500scan output could not be written {reason}
X500673SCNTGT500scan target resolution failed {reason}

Source: modules/schedule
Count: 14

CodeHTTPMessage template
X400001CRNINV400invalid cron expression {cron}
X400932SCHSTK400--stack is required
X400934CRNEMT400empty cron expression
X400935CRNFMT400invalid cron {cron}
X400936CRNHMS400expected HH MM
X400937CRNCNN400non-numeric clock parts
X400938CRNOOR400out-of-range hour or minute
X404902SCHNFD404schedule not found {job}
X409900SCHDPL409schedule already exists for job {job}
X500617SCHLAT500schedule {job} of {tenant}/{stack} ({environment}) was due {due}, more than its {interval} interval ago, and has not fired
X500954SCHCAC500count active schedules failed {error}
X500955SCHCPS500count paused schedules failed {error}
X500956SCHNRT500next-run lookup failed {error}
X503125SCHGON503schedule {schedule_id} waits: node {node_id} holding {stack_name} is gone

Source: modules/scheduler
Count: 31

CodeHTTPMessage template
X400689SCHSTA400{state} is not an assignment state: assigned, starting, ready, unready, failed, completed or stopped
X400690SCHDUP400assignment {op} names replica {replica} twice, one batch binds a replica once
X400693SCHUNB400intend names replica {replica}, which is not bound, so there is nothing to move
X400697SCHREP400replica {replica} names no pod, no node or an ordinal below 0, so it has no assignment row to keep
X400946NODRES400--reserve {item} {problem}
X400949NODHYP400--hypervisor {value} {problem}; write or /
X404692SCHDNF404deployment {deployment} does not exist, so none of its replicas can be bound
X404950NODHYC404--hypervisor names connection {connection}, which {problem}; nothing was written
X409676SCHUNC409global deployment {deployment} has an uncommitted staged spec, so the binding pass waits to create replicas
X409678SCHREF409global service {service} of {deployment} has an empty eligible set ({detail}), so no node receives a replica
X409679SCHGLB409global service {service} of {deployment} has no room on node {node} ({detail}), so that node runs no replica of it
X409683SCHDEP409this engine was deposed: its epoch is {epoch} and the current one is {current}, so the bind changed nothing
X409684SCHGEN409replica {replica} is at generation {got}, not the {want} this bind read, so the bind changed nothing
X409685SCHTGT409replica {replica} is being moved to {got}, not {want}, so the bind changed nothing
X409686SCHREN409node {node} renewed its lease since this bind read it, so it is back and the bind changed nothing
X409687SCHFIT409node {node} has no room for this bind’s {resource} requests any more, so the bind changed nothing
X409688SCHGRD409assignment {op} was refused by its guard and a re-read shows no cause, another write raced it
X409695SCHSTP409{deployment} is stopped, so nothing delivers its project anywhere
X409698SCHSPC409replica {replica} already has an incarnation at {spec}, so the start changed nothing
X409699SCHMVG409the move of {deployment} to {target} holds no live copy of {replica} there, so the copy it left was not retired
X409701SCHNXT409{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
X409702SCHUND409{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
X409947SCHRSV409node {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
X409948SCHOUT409node {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
X413677SCHBIG413assignment {op} names {rows} replicas, more than one statement can guard: it would bind {parameters} parameters and the store takes {limit}
X500681SCHWRT500assignment {op} could not be written: {error}
X500682SCHRED500{what} could not be read: {error}
X500696SCHPRT500{deployment} is installed on {node} but its delivery did not finish: {error}; it is not tried again on its own, shc update finishes it
X503680SCHSTO503assignment {op} has no store yet, the daemon has not opened the control plane
X503691SCHNOE503no scheduler has taken an epoch yet, the leader’s scheduler subsystem has not started
X503694SCHDLV503nothing can deliver {deployment}‘s project to {node}: the daemon has not wired the deployment dispatch

Source: modules/search
Count: 3

CodeHTTPMessage template
X400400SRINPT400search invalid input {reason}
X404400SRAPNF404app {name} not found
X500401SROPFL500search {operation} failed

Source: modules/selfclean
Count: 2

CodeHTTPMessage template
X200326SLFSWP200self-clean {trigger} sweep on node {node} removed {what}, giving back {freed}; {disks}
X507326SLFFUL507{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

CodeHTTPMessage template
X400920SHLREQ400shell requires a stack name
X400922SHLCMD400exec requires a command
X404920SHLCNT404no running container for deployment {deployment} service {service}
X500920SHLWSF500shell websocket exec failed {op}{error}
X500921SHLEXC500shell exec failed {op}{error}
X500922SHLPTY500shell pty operation failed {reason}
X500923SHLRDR500shell reader done
X503153SHLUPG503the shc daemon {target} has no streamed exec, upgrade it to this CLI’s release and run the command again

Source: modules/stack
Count: 16

CodeHTTPMessage template
X400060STKREQ400stack name required
X400062CMDRQD400command required for exec
X400210STKARG400stack dispatch {what} is malformed {error}
X400957STKRUN400stack runtime {runtime} is not supported on the new line; use docker, podman, incus or apple
X400958STKVRB400stack verb {verb} is not run on the {runtime} runtime
X400959SVCRQD400service name required for exec
X400962STKTTY400an exec with a terminal is not run on the {runtime} runtime
X404908STKNFD404stack {stack_name} not found
X409069STKAMB409stack {stack_name} exists in more than one scope, found in {scopes}
X409231CTRAMB409container {container} names more than one container ({ids}); restart one by its full id
X409880STKRIN409start 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
X409881STKVLT409{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}
X409882STKDEP409{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}
X502070EXCRPL502exec reply from node {node} is invalid {reason}
X502071EXCHTT502node {node} answered the compose call with HTTP {status}
X503010NDUNRC503cannot connect to node {node} {error}

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

CodeHTTPMessage template
X200036LNKSKP200storage link-table write failed for node {node} on {provider} after its share was proven reachable, the node is not recorded as a client {error}
X200037MNTSKP200share 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}
X200038ATTSKP200store attestation write failed for node {node} on store {store}, the node is not read as reaching it {error}
X200088FSTTRN200{path} held a torn line, NUL bytes from an interrupted write, and the rewrite took it out: {line}
X200089FSTRGN200volume {volume_id} of {deployment} had lost its fstab line on {node}, written again from its attach: {line}
X200310VOLSRD200volume {volume} size could not be recorded from {provider}: {reason}
X200318VOLLRC200reconciled {count} stranded volume backup leases
X200319VOLFIN200automatic volume failover is inert on this estate, {reason}
X200333VOLCHL200volume {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
X200342VOLRST200volume {volume_id} is back on {node} after the partition healed, remounting it and starting the writers its lease loss stopped
X200354VOLRFS200volume {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
X200368VOLRMD200volume {volume_id} of {deployment} is mounted again on {node} at {mountpoint}
X200425VOLRWM200{step} of {device} on {node} opened DRBD resource {resource} read-write after {attempts} attempts in {waited}
X202347VOLRNU202volume {volume_id} lease renewal committed, the read of its holder failed {error}
X400040EXTNAM400shc-managed providers must use reserved names local, nfs, cephfs
X400053RSVTYP400provider type {provider_type} is reserved for the singleton {reserved_name}, custom name {name} not allowed
X400058MNGDEL400managed provider {name} cannot be removed via storage remove, use shc storage {provider_type} disable
X400060STGWRF400path {path} is not on a {expected} filesystem
X400081NFSBND400nfs server cannot listen on {bind}, it is neither an IP address nor an interface with an IPv4 address on this node
X400283VOLICT400incus volume provider misconfigured, {reason}
X400291LNSCFG400linstor volume provider misconfigured, {reason}
X400320VOLDOC400digitalocean volume provider misconfigured, {reason}
X400323VOLHCT400hetzner volume provider misconfigured, {reason}
X400324VOLCFM400volume {volume_id} rebind requires -y/--yes old node detached without waiting for ack
X400325VOLCFG400no volume backend configured {reason}
X400326VOLCSU400volume connection {conn} for tenant {tenant} not resolvable to a volume provider
X400327VOLAMB400storage.volumes.provider is unset and multiple volume-capable connections exist, {candidates}, set storage.volumes.provider to the one to use
X400329VOLSNP400volume {volume_id} snapshot request incomplete, {reason}
X400330VOLSRC400volume {volume_id} restore-snapshot requires -y/--yes, its current contents are discarded
X400334AZDCFG400azure disk provider misconfigured, {reason}
X400336VOLCSC400cloudstack volume provider misconfigured {reason}
X400340LNKEVD400refusing 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
X400343EBSCFG400aws ebs volume provider misconfigured, {reason}
X400344GPDCFG400gce persistent disk volume provider misconfigured, {reason}
X400347VOLRCH400volume connection {conn} names no provisioning location, so its reach is unknown, set the connection’s region or zone
X400352VOLOVT400operator lease assertion refused for target {target}, {reason}
X400362VOLLCT400linode volume provider misconfigured, {reason}
X400855VOLPROV400volume provider hetzner is gone, use hcloud or a volume connection name
X400929NODLNK400node {node} is not linked to storage provider {provider}
X400931INVCFG400invalid storage configuration {reason}
X400937QNOSUP400quotas not supported by storage provider {name}, filesystem {filesystem}
X400942SNOSUP400snapshots not supported by storage provider {name}, filesystem {filesystem}
X400944PRVTYP400unknown storage provider type {provider_type}
X400945SNPMTH400unknown snapshot method {method}
X400946QTAMTH400unknown quota method {method}
X400947RSVNAM400reserved name {name} can only be used for shc-managed providers
X403056CFSCBN403cephfs node handler refused, caller identity does not match target node {reason} caller={caller} target={target}
X403080NFSCBN403nfs node handler refused, caller identity does not match target node {reason} caller={caller} target={target}
X403081VOLCBN403volume node handler refused, {reason}, caller {caller} target {target}
X403324VOLEEO403volume {volume_id} rebind requires SHC EE, cross-node failover needs the multi-node failover plane
X403333VOLOVA403operator lease assertion refused, it could not be attributed to an authenticated operator and an unattributable force-detach authorization is not acceptable, {meaning}
X403992VOLEEO403automatic 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
X404031STFNOF404state folder {path} not found on storage provider {provider}
X404032SNPNOF404snapshot {snapshot_id} not found for {path}
X404033SRCNOF404source path does not exist {path}
X404103STGNFD404shared storage provider {name} not configured, run shc storage {name} enable first
X404283VOLINF404incus resource not found by {selector} {value}
X404291LNSNOF404linstor resource definition {volume} does not exist
X404320VOLNOF404volume not found by {selector} {value}
X404322VOLHNF404hetzner resource not found by {selector} {value}
X404324AZDNOF404azure resource not found by {selector} {value}
X404336VOLCSN404cloudstack resource not found by {selector} {value}
X404341VLTVNF404vultr resource not found by {selector} {value}
X404343EBSNOF404aws ebs resource not found by {selector} {value}
X404344GPDNOF404gce persistent disk resource not found by {selector} {value}
X404346VOLHSV404no hetzner server matches node {node}, tried {tried}
X404349VOLNPL404no machine this volume provider can see is node {node}, {why}
X404362VOLLNF404linode resource not found by {selector} {value}
X404383ALIVNF404alibaba disk resource not ready: {resource}
X404385UPCVNF404upcloud {resource} not found
X404914STGNOF404storage provider {name} not found
X409030STGEXS409storage provider {name} already exists
X409031STFEXS409state folder {path} already exists on storage provider {provider}
X409032VOLXTN409volume belongs to tenant {got} not {want}
X409033STGUSE409storage provider {name} is in use by {stacks} {stack_names} and {volumes} volume rows, pass --force to delete anyway
X409034VOLREB409volume {volume_id} rebind refused current node {current_node} not expected {expected_node}
X409035VOLLSE409volume {volume_id} lease refused, request generation {req_gen} row generation {row_gen} {detail}
X409036VOLATT409volume {volume_id} still attached to {node} pass force to detach first
X409037VOLFRB409volume {volume_id} auto failover refused, {reason}
X409038CEPFID409ceph cluster identity conflict, /etc/ceph carries fsid {found} but the pinned cluster fsid is {pinned}, run shc storage cephfs disable before enabling again
X409040VOLREL409volume {volume_id} provider {provider} cannot relocate from {prev_node}, its Attach does not self-detach a previous holder
X409041VOLWKL409volume {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
X409042VOLSNA409volume {volume_id} is attached to {node}, detach it before restoring a snapshot
X409043VOLRNM409refusing to lay out block volume root {root} on {node}, {reason}
X409044VOLRLW409volume {volume_id} relocate refused, deployment {stack} still runs a writer on {node} after the relocation stopped it, stop it there and retry
X409050VOLNKP409volume {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
X409055CEPMGR409cephfs join refused, the ceph cluster has no active mgr, check ceph -s on the leader
X409056CEPFSD409refusing 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
X409057CEPNET409cephfs 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
X409058CEPNEN409cephfs join refused, no ceph cluster answers on the leader, run shc storage cephfs enable first
X409283VOLIMB409incus 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
X409283VOLIOW409incus volume {volume} belongs to another deployment
X409283VOLIPD409incus instance {instance} device {device} for volume {volume} comes from a profile and must be removed from the profile by hand
X409283VOLIRH409incus volume {volume} is held by instance {instance}, detach it before relocating
X409283VOLIRP409incus volume {volume} on member {member} is not this relocation’s copy and must be inspected by hand
X409291LNSDEV409linstor resource {volume} on node {node} has no device yet
X409291LNSOWN409linstor resource definition {volume} belongs to another deployment
X409306VOLRSZ409volume {volume} is on {provider}, which cannot grow a volume
X409307VOLNPV409volume {volume} was never provisioned, so it has nothing to grow
X409308VOLDET409volume {volume} is attached to no node, so its filesystem cannot grow
X409309VOLNSZ409volume {volume} has no recorded size and {provider} cannot report one, so it cannot grow
X409320VOLDOD409digitalocean volume {handle} cannot be confirmed detached from {node}, {reason}
X409324AZDREL409azure disk {handle} not freed from holder {holder} within detach-settle bound, last http {last}
X409342VOLCLM409volume {volume_id} is claimed by another operation, {reason}
X409343EBSDEV409aws ebs no free device slot on instance {instance}, /dev/sd[f-p] exhausted
X409346VOLCST409cloudstack volume {id} has shc-volume tag {actual} instead of {expected}
X409351VLTLIV409vultr 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}
X409352VOLLFT409mount {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
X409356VOLCSM409multiple cloudstack volumes match {name} with ids {ids}
X409440VOLKPL409mount {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}
X409448VOLNAM409{name} names more than one volume: {volumes}. Name the deployment with -s and -e, or give the volume’s ID
X409864VOLLSE409volume {volume_id} already leased by {owner} until {until}
X409866VOLSFN409volume {volume_id} lease loss in progress on {node}, not yet provably stopped
X409868VOLPPD409volume {volume_id} auto failover stalled on {node} for {stalled}, lease path {lease}, stonith path {stonith}, operator override {override}
X409869VOLOVH409operator lease assertion refused for node {node} in state {state}, {reason}
X500032CMDFLR500command failed {command} {error}
X500035STGCMD500{tool} failed {stderr} {error}
X500050CEPMON500ceph mon bring-up via cephadm failed, check the daemon log and ceph -s on the leader
X500051CEPMDS500ceph mds placement via the orchestrator failed, check ceph orch ls and the daemon log
X500052CEPFSC500cephfs volume creation via ceph fs volume create failed, check ceph -s and the daemon log
X500053CEPENB500shc storage cephfs enable failed during the cephadm bring-up, check ceph -s/ceph orch host ls on the leader and the daemon log
X500054CEPENR500ceph enroll {op} {error}
X500054CFSCLI500cephfs client mount setup failed {op}{error}
X500055CEPHKY500cephadm host-key install on {host} failed {op} {error}
X500056CEPAUT500cephx client authorization failed {op} {error}
X500076NFSSRV500nfs server setup failed {op}{error}
X500077NFSCLI500nfs client setup failed {op}{error}
X500078NFSDIS500nfs disable failed {op}{error}
X500081NFSEXP500nfs export {path} is not usable, {reason}
X500082NFSREL500nfs exportfs reload refused the exports files so nothing is published, {reason}
X500129NFSHID500nfs storage not enabled, the local node id is unresolved so no node can be recorded as the export host {error}
X500315VOLREP500volume repository error {op}{error}
X500317VOLNDP500node volume provisioner {op} on {node} failed {error}
X500318VOLSFU500node lease-loss {op} on {node} failed {error}
X500327VOLCMD500node volume command failed {reason}
X500328VOLWKU500volume {volume_id} rebind refused, could not determine whether the workload still runs on the old node, {reason}
X500329VOLRLU500volume {volume_id} relocate refused, could not tell whether deployment {stack} still runs on {node}, {reason}
X500331VOLNPR500volume {volume_id} has been stranded on {node} for {stalled} with NO force-detach proof path making progress, {blocked}, {action}
X500333VOLCHB500volume {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}
X500917QTAERR500quota operation failed for {path} {error}
X500919SNPERR500snapshot operation failed for {path} {op} {error}
X501330VOLSTN501no stonith provider configured, cannot confirm the power-off of node {node}
X501331VOLSNU501volume provider {provider} cannot snapshot block volumes, {reason}
X501393NFSPLT501nfs {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
X501394CEPPLT501ceph {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
X502111LDRFWD502shared-storage operation {op} could not be relayed to the raft leader, {reason} {error}
X502283VOLIAP502incus volume api call {op} failed, http {status} {error}
X502283VOLRLF502volume {volume_id} rebind relocation to {node} failed, {error}
X502291LNSAPI502linstor api call {op} failed, http {status} {error}
X502320VOLDOA502digitalocean volume api call {op} failed, http {status} {error}
X502321VOLHAP502hetzner volume api call {op} failed, http {status} {error}
X502322VOLNDA502node volume dispatch to {node} {path} failed, {reason} {error}
X502324AZDAPI502azure disk api call {op} failed, http {status} {error}
X502326VOLCSA502cloudstack volume api call {op} failed http {status} {error}
X502329VOLDTF502volume {volume_id} rebind refused, the cloud detach from {node} failed and the volume is left attached where it was, {reason}
X502331VLTVAP502vultr block storage api {op} failed http {status} {error}
X502343EBSAPI502aws ebs ec2 api call {op} failed {error}
X502344GPDAPI502gce persistent disk compute api call {op} failed {error}
X502362VOLLAP502linode volume api call {op} failed, http {status} {error}
X502383ALIVAP502alibaba disk api {op} failed: {error}
X502385UPCVAP502upcloud storage api {op} failed http {status}
X503110NOTLDR503shared-storage operation requires the raft leader, {reason} {error}
X503345VOLRLQ503volume {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
X503366THNPOL503lvm thin pool {pool} on node {node} holds {volumes} and is not active, {check}, every volume on it is down until the pool is activated
X503368VOLRMT503volume {volume_id} of {deployment} is attached to {node} and not mounted at {mountpoint}, {reason}
X503425DRBWAT503{step} of {device} on {node} waits for DRBD resource {resource} to promote this node, {reason}, trying again in {delay}
X503425VOLRWF503volume device {device} on {node} was not opened read-write for {step}, {reason}
X504332VOLSTL504volume binder {step} on node {node} via provider {provider} made no progress within {budget} and was abandoned, the volume is not bound{detail}

Source: modules/storerpc
Count: 5

CodeHTTPMessage template
X400135STRVAL400a store statement cannot carry a value of type {type}
X501082STRNTX501a store client runs no interactive transaction ({call}), a multi-statement write goes through db.Pool.Batch
X503128STRNOL503this node is a store client and its store list names no member
X503134STRSTL503this node’s replica is more than {bound} behind the leader, so it answers no local read
X503136STRUNR503no member of this node’s store list answered {function}, {count} tried, the last {error}

Source: subsystems/impl, subsystems/lifecycle, subsystems
Count: 121

CodeHTTPMessage template
X200202BKPANC200deployment {stack_name}/{environment} records node {node} but its deployment directory is on {holder}, backing up on {holder} and re-anchoring the row
X200203BKPARF200deployment {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
X200863SWKILL200node {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
X200864SWFRGN200node {node} lost its lease and left single writer {container} of {deployment} running, it is not this node’s: {reason}
X200963INGGAT200ingress reconcile traefik host check failed {error}
X200964INGSWP200ingress route materialize sweep failed {error}
X200965LEAFSW200certificate leaf renewal sweep failed {error}
X200966CAEXPS200certificate intermediate expiry scan failed {error}
X200968KCBRCN200keycloak base path reconcile failed {error}
X200969OOBRCN200openobserve base path reconcile failed {error}
X200971NETRCN200shared network reconcile failed {error}
X200973CTRSTL200container reconcile stale container list failed {error}
X200974CTRSRM200container reconcile stale container {container_id} remove failed {error}
X200975CTRDRL200container reconcile status drift list failed {error}
X200976CTRDRF200container reconcile status drift fix failed for deployment {deployment_id} {error}
X200978INTTLS200internal api tls server error {detail}
X200985PRXRAT200proxy reconcile stopped {provider} for this pass after an API rate refusal, retry after {wait}
X200986PRXREF200proxy reconcile parked {tenant}/{stack} on {connection} after {provider} refused HTTP {status}, retry in 1h or when inputs change
X400728EDGPRT400{source} puts the public api at {address}, the edge serves 443 on every node and nodes join through it, bind the api elsewhere
X400975VLTRFE400SHC_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
X401014VLTPRM401vault auto-unlock credential file {path} {reason}
X403044INTNMB403internal api peer certificate rejected, identity {identity} is not in the live node registry, node removed from the cluster or never enrolled
X409132RQDJND409a member joined while the store was copied, so this node stays on rqlite
X409133RPLRCN409this node’s replica was rebuilt less than an hour ago
X409134RPLNJM409this node holds no cluster_join.json to rejoin from
X500384RFTSNP500no rqlite snapshot with a readable meta.json
X500385RFTTRM500raft’s current term cannot be read from raft.db, {reason}
X500386RPLJSN500cluster_join.json is not readable JSON
X500387COLTRE500podman info named no container tree, it answered {answer}
X500390COLILS500the {runtime} executor on this node lists no instance
X500391COLATR500container system status named no app root, it answered {answer}
X500394COLEPR500the collector printed no probe result, it printed {output}
X500990INTAPCA500failed to parse internal-api CA {path} no PEM blocks
X500991INTAPKP500failed to load internal-api node cert and key {error}
X500992LCSTFL500lifecycle subsystem {subsystem} start failed {error}
X500993LCDPBL500lifecycle deps builder for {name} panicked {detail}
X501002DBREOP501failed to reopen rqlite pool {error}
X501003INTAPRD501failed to read internal-api CA {path} {error}
X501017RQDSTP501rqlited manager stop returned error {error}
X501018RQDDEM501scale-to-one demote failed, staying on the raft engine {error}
X503015LDRPOL503leader_hub poll-driven FlipLeader returned error {error}
X503022EVBNPL503event_bus no db pool wired, running without events.Service
X503023EVBSTR503event_bus events.Service.Start failed {error}
X503024EVBREC503event_bus pending-broadcast recovery sweep failed {error}
X503025EVBNOJ503event_bus job.Service not wired, V200900JOBRUN handler is a no-op
X503026QUENPL503queue no db pool wired, running without task.Service
X503027QUESTR503queue task.Worker.Start failed {error}
X503028HTPNAS503http subsystem no api.Server available, skipping TCP listener
X503029STKRWR503stack_reconcile reconcile.Wire returned error {error}
X503034VLTSKP503vault subsystem started without config, skipping
X503035DKRDWN503docker daemon unreachable, continuing {error}
X503036SSEBSK503sse_broker subsystem started without pool, skipping
X503037COLSKP503collectors subsystem started without config, skipping
X503038COLTKE503tick collector error {error}
X503039CFGSKP503config_loader subsystem started without pool, skipping
X503040DKEVEX503docker_events Subscribe exited {error}
X503041RTRWLK503router walk failed for module {module} {error}
X503042INTRWK503internal router walk failed for module {module} {error}
X503043INTAEX503internal_api listener exited {error}
X503046BKMRCN503backup_mount reconcile failed {error}
X503046LCSTRB503lifecycle start failed in group {group}, rolling back {error}
X503047LCSTPE503lifecycle subsystem {subsystem} stop returned error {error}
X503048LCRBKE503lifecycle rollback Stop for {subsystem} returned error {error}
X503048USKVNS503unix_socket filesystem entry vanished, rebinding {path}
X503049LCFAHL503lifecycle subsystem {subsystem} reported fatal health error {error}
X503049USKRBD503unix_socket rebind failed {path} {error}
X503051LCSTDG503lifecycle subsystem {subsystem} started degraded, daemon staying up {error}
X503052LCDGRD503lifecycle subsystem {subsystem} degraded {error}
X503053LCONLD503lifecycle OnLeader callback failed for {subsystem} is_leader={is_leader} {error}
X503055NSRWRN503node_self_register {step} failed {error}
X503056COLPRT503collectors per-tenant alloc failed for {tenant} {error}
X503075SCHFRR503schedule_dispatcher per-row dispatch failed {schedule_id} {error}
X503076SCHSWP503schedule_dispatcher sweep returned error {error}
X503077SCHDQE503schedule_dispatcher enqueue to task queue failed at {op}{error}
X503078BKSCEX503backup_scheduler scope execute failed {scope_key} {error}
X503079MNTMKD503backup_mount default repo {repo} mkdir failed {error}
X503080MNTRIN503backup_mount restic init failed for {repo}, backup ops fail until configured {error}
X503081VLTAUF503vault auto-unlock from the credential file failed {error}
X503082VLTENV503vault auto-unlock credential could not be cleared from the daemon environment {error}
X503083CFGRLD503config_loader DB-layer reload failed after {changed} changed paths {error}
X503084CCAGEN503cluster_ca_genesis provision returned error {error}
X503085CCAGSL503cluster_ca_genesis row committed but sealed vault key unreadable {error}
X503086CCAGLF503cluster_ca_genesis first-node local port 4003 leaf sign failed {error}
X503087CRNSKP503cron_runner skipped {module}.{cron}, previous run still in flight
X503088CRNBAD503cron_runner unparseable schedule for {module}.{cron} spec={spec} {error}
X503089CRNRUN503cron_runner {module}.{cron} Run returned error {error}
X503091COLTKI503collectors tick interval {reason}, running at {interval}
X503091GCAGEN503global_ca_genesis provision returned error {error}
X503093OPRREAP503operation_registry stale-operation reaper sweep returned error {error}
X503094OPRLST503operation_registry reaped lost operation {task_id}, its worker’s node held no lease for {lease}s
X503095CCAGVL503cluster_ca_genesis deferred the sealed cluster CA key check, this node vault is locked {error}
X503099LCONWD503lifecycle 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
X503100LCONWL503lifecycle OnLeader for {subsystem} is_leader={is_leader} returned late after {elapsed} {detail}
X503105INTMBR503internal api membership gate registry refresh failed {error}
X503106BKSLOD503backup_scheduler schedule load failed {error}
X503107BKPNOK503backup_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>
X503108BKPNOP503backup_mount SHC_BACKUP_REPO={repo} set without SHC_BACKUP_PASSWORD, repo not adopted
X503109SCHPLC503schedule_dispatcher cannot dispatch {schedule_id}, deployment {stack_name} has no app directory on this node and the deployment table places it on {node}
X503112SCHDIS503schedule_dispatcher disabled {schedule_id}, {reason}
X503114EVBRGU503event_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}
X503115BKPPLC503backup_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
X503116BKPDSP503backup_scheduler could not capture {stack_name}/{environment}, the deployment table places it on {node} and the capture could not be run there, {detail}
X503119RCLTMO503periodic tick for {loop} exceeded its {budget} budget and was cancelled, the sweep did not finish and the next tick will retry
X503120RCLDRN503reconcile loop {loop} did not drain within {budget} of being stopped, abandoning the goroutine, a sweep is wedged somewhere its cancellation cannot reach
X503121PUMPSTL503{subsystem} has completed no sweep in {silence}, past its {budget} budget, its pump is running but producing nothing
X503122LDRSTL503control-plane loop {loop} has completed no sweep in {silence}, past its budget
X503123LDRSDF503leader loop {loops} is wedged and the rqlite leadership could not be stepped down {error}
X503124LDRSDN503leader loop {loops} is wedged, stepped the rqlite leadership down so another node leads
X503130RFTNLD503raft has no leader now
X503131RPLNSC503no store client to read the nodes’ rows from
X503133RFTNUP503this node’s raft engine has not come up yet, so no node can be removed from here and nothing was changed
X503135COLNRN503no {service} container of project {project} is running
X503136RFTSTD503cannot tell node {node} to stand down, {why}
X503147SCHHLD503global 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
X503149LDRWRK503could not record this leader’s leader-only work for the other nodes to read: {cause}
X503150CRNDUP503cron_runner did not fire {module}.{cron}, this tick already fired at {at} on {node}
X503151CRNCAT503cron_runner fires {module}.{cron} once now, its tick at {tick} passed with no node firing it, last fire {last}
X503152CRNRSV503cron ledger could not record {module}.{cron}‘s fire in the cluster store {error}
X503938VLTSOP503vault auto-unlock credential {path} did not open, so the vault stays locked until shc vault unlock, which seals a new one {error}
X504208BKSCDB504backup of {deployment} in the fire of {scope_key} ran past its own {budget} budget and was cancelled, the fire went on without it, {error}
X507831BKSCSP507backup 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}

Source: modules/supportbundle
Count: 14

CodeHTTPMessage template
X200373SPBSEC200support bundle section {section} degraded, {reason}
X200376SPBOMT200section {section} omitted, estate-scoped sections ride only a platform-admin bundle
X400374SPBREQ400invalid support bundle request, {reason}
X400379SBFORM400not a loadable support bundle, {reason}
X400380SBVERS400support bundle format version {version} is newer than the {supported} this shcsb reads
X403378SBRDON403support bundle replay is read-only, {method} {path} would change the cluster
X403382SPBCFG403read access to stack {stack} configuration is not granted
X404381SBNOID404no support bundle {id} is loaded
X404396SBNONE404not in this support bundle, {what}
X500371SPBSTR500support bundle download failed at {step}, {error}
X500372SPBHTT500support bundle request failed, the daemon answered http {status}, {body}
X500395SBLOAD500support bundle load failed at {step}, {error}
X502377SPBSTQ502support bundle store query failed, http {status}, {body}
X503375SPBNWR503support bundle source {source} is not wired on this daemon

Source: modules/task
Count: 13

CodeHTTPMessage template
X200914TSKRTY200task {task_id} scheduled for retry {attempt}/{max_attempts} in {delay}s
X400916TSKAFF400affinity {node_id} names no node
X404404TSKNFD404task {task_id} not found
X409404TSKAMB409ambiguous task id {task_id} matches {count} tasks, pass a longer prefix
X500004HDLNFD500handler not found for task {task_name}
X500904TSKFAL500task {task_id} failed with {error}
X500905TSKINT500task {task_id} interrupted, server restarted while running
X500909TSKOPF500task {operation} failed
X500912TSKTMO500task {task_id} timed out after {max_runtime_seconds}s
X500913TSKWRK500task worker {stage} failed {error}
X500914TSKPNC500task {task_id} {name} handler panicked {panic}
X500915TSKLST500task lost-operation reaper {stage} failed
X503010QUEFUL503queue at capacity {depth}/{max_depth}, task {name} rejected

Source: modules/telemetry
Count: 5

CodeHTTPMessage template
X200393TELNSL200no stack label in this metrics stream
X400390TELREQ400invalid stack metrics request, {reason}
X403391TELREJ403read access to stack {stack} telemetry is not granted
X502392TELSTQ502OpenObserve metrics query failed, http {status}, {body}
X502394TELUNR502telemetry store {host} could not be reached, {reason}

Source: modules/tenant
Count: 13

CodeHTTPMessage template
X400059TNTHAS400tenant {name} has {count}, use force to remove
X400062TNTREQ400tenant name is required
X400958TNTREQ400tenant {name} has {count} to uninstall first
X400974TNTNAM400tenant name {name}, {reason}
X403975TNTEEO403tenant {name} not created, creating additional tenants requires SHC EE
X404973TNTNXS404tenant {name} does not exist, {hint}
X409059TNTUNK409tenant {name} deployment count could not be determined, {reason}, refusing to delete a tenant whose deployments cannot be counted
X409974TNTTMB409tenant {name} was deleted and is not re-adopted automatically, {hint}
X500460TNTSQL500tenant sql operation {operation} failed {error}
X500461TNTFSO500tenant fs operation {operation} failed {error}
X500462TNTVLT500tenant admin credential vault store failed {reason}
X500463TNTKCP500detached keycloak provisioning failed {tenant} {op} {error}
X503973TNTIND503tenant {name} existence could not be determined, {reason}

Source: modules/test
Count: 10

CodeHTTPMessage template
X400026TSTBND400the 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 _
X404010APPNFD404app {app} not found
X404026TSTNON404no test run {run} was started on this node
X404910TSTNFD404app {app} has no tests directory
X409026TSTHLD409test run {run} is still running on this node, so it is not cleaned up
X500010BATSNF500bats is not installed
X500011TSTNIL500apptest Runner has nil receiver
X500012TSTCMD500apptest bats command is empty
X500017TSTCLP500test run cleanup failed {reason}
X500026TSTRUN500test run stage {stage} failed {error}

Source: modules/underlay
Count: 16

CodeHTTPMessage template
X400566UDPREQ400UDP probe request refused, {reason}
X404568UDPPRB404no UDP probe {id} is held on this node for this caller, it was read already or ran out
X404580UDPRLY404this node cannot relay a joiner’s UDP probe to {node}, {reason}
X409571UDPPAR409this 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
X409572UDPNON409this node at {address} proved no path to any member on the underlay, {reasons}
X409576UDPARM409this 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
X409598UDPOUT409UDP {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
X409599UDPBCK409UDP {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
X500574UDPPRD500the underlay.pairs row cannot read {source}{error}
X501569UDPTKN501this node cannot check a bootstrap token, so it hosts no joiner’s UDP probe
X501570UDPHST501node {node} cannot host a UDP probe on {device}, {reason}
X502575UDPSIG502the answer from {host} is not signed by the cluster, {reason}
X502581UDPRLF502this node could not relay a joiner’s UDP probe to {node}: {reason}
X502583UDPRLR502this 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
X503567UDPBSY503this node holds {held} UDP probes already, try again in a few seconds
X503573UDPMBR503this node cannot list the cluster’s members, {reason}

Source: modules/user
Count: 33

CodeHTTPMessage template
X400913USRPWM400passwords do not match
X400924USRNAM400{name} is not a full name: give the person’s given and family names, like “Ada Lovelace”
X400930USRREQ400user request missing {field}
X400932USRTNB400caller has no tenant binding
X400933USRROL400{role} is not a role tenant {tenant} grants, the roles are {roles}
X400934USRGNM400group name {name} is not valid, use lowercase letters, digits, dot, underscore and hyphen, starting with a letter or digit, at most 64 characters
X400935USRMAP400{role} needs auth.trusted_realms to map realm {realm} to tenant {target}, add {realm}={target} to auth.trusted_realms
X400937USRRNM400realm 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
X400939USRRST400{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)
X400941USRRML400realm mail setting {setting} {reason}
X400943USRRDN400realm setting display-name {reason}
X403930USRPRM403requires tenant manage permission
X403931USRXTN403cannot operate on tenant {requested}, caller bound to {own}
X403935USRLMT403tenant {tenant} has {count} user accounts, the community edition seat limit is {limit}, more requires SHC EE
X403939USRPLT403only a platform admin grants platform:manage in tenant {tenant}
X403988RBCEEO403granting {role} in tenant {tenant} is organizational RBAC and requires SHC EE with the rbac entitlement, the community edition grants the baseline roles stack:, tenant:manage, tenant:use and tenant:deny inside the caller’s own tenant, and revoking any role is always free, see shc license status to activate a license that includes rbac
X404930USRNOF404user {username} does not exist in tenant {tenant}, list the tenant’s users with shc user ls
X404934USRGNF404group {group} does not exist in tenant {tenant}, list the tenant’s groups with shc user group ls
X404936USRSTK404{role} names deployment {stack}, which tenant {tenant} does not have
X404937USRRNF404realm role {name} does not exist in tenant {tenant}, list the tenant’s realm roles with shc tenant role ls {tenant}
X409930USRLMG409user {username} is the last manager of tenant {tenant}, grant tenant:manage to another user first, or a platform admin can pass --force-last-admin
X409931USRLPA409user {username} is the last platform admin, grant platform access to another user first, or a platform admin can pass --force-last-admin
X409932USRGLM409removing 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
X409933USRGOW409group {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
X409937USRROW409realm role {name} is one Keycloak or SHC gives a meaning of its own and is not made, changed or removed here: those are {own}
X409938USRMST409the realm of tenant {tenant} is the platform’s own and its settings and realm roles are not declared here
X409942USRVEM409the realm of tenant {tenant} cannot require a verified email without mail settings; set mail-host and mail-from, in the same call if needed
X413930USRLAY413launcher layout exceeds {max} bytes
X503930USRKCN503system keycloak is not running
X503931USRLAY503launcher layout store unavailable
X503932USRRLM503keycloak realm for tenant {tenant} is not provisioned yet
X503933USRGLK503user management guard lock unavailable: {reason}, retry
X503934USRCTN503console tenant store unavailable

Source: modules/vault
Count: 64

CodeHTTPMessage template
X200052VLTSKP200vault auto-unlock credential {path} was not planted because this host cannot seal it, so the vault needs shc vault unlock after every restart {error}
X200966VLTDRW200vault unlocked but the auto-unlock drop-in {path} could not be repaired so this node will come up locked at its next restart {error}
X200970VLTUBP200vault unlock broadcast peer {node} failed {error}
X200972VLTENA200vault envelope state adoption failed this node has no replicated envelope state until the next unlock retries {error}
X200973VLTCSD200vault cold-start holder declaration failed on {node} {error}
X200997VLTUPD200vault unlock pull peer {node} accepted but no unlock landed within {wait}
X400025PRVAUT400{auth_method} authentication requires {requirement}
X400026PRVKTY400{provider} requires {required_key_type} key, got {got_key_type}
X400381VLTNML400the vault path is longer than the {limit} characters vault provider {provider} can stamp, so use a shorter key
X400382VLTNMG400the vault path encodes to a {length}-character secret id, longer than the {limit} characters vault provider {provider} accepts
X400385VLTNMD400{name} is not a name vault provider {provider} writes for a vault path
X400906INVSCP400invalid scope {scope} requires {required}
X400910VLTEXP400vault export failed with {reason} {error}
X400912VLTIMP400vault import failed with {reason} {error}
X400916PRVUNK400unknown vault provider {provider}
X400917PRVREQ400{config_key} is required for {provider} provider
X400918PRVSCP400{scope_type} required for {operation}
X400919PTHFMT400invalid path format {path} {error}
X400925PRVPIN400pinned vault provider not configured {provider} {path}
X400962VLTHOK400{hook} hook not wired
X400963VLTPWM400passwords do not match
X400964VLTRMS400invalid remap-scope pair {reason} {pair}
X400965VLTDRI400vault operation refused the auto-unlock drop-in {path} {reason} {error}
X400970VLTVAL400invalid secret value source: {reason}
X400978AGNCRT400autogen certificate {key} cannot be signed: {reason}
X400980VLTFMT400vault crypto format failure {reason} {error}
X400981VLTCST400vault cold-start replant has no usable target {node} {reason}
X400983AGNCHS400invalid autogen charset {charset} {reason}
X400984VLTESL400the escrow receipt was refused: {reason}
X400985VLTESK400the escrow label or note contains the {what} itself; record where the copy is kept, never the key
X400986AGNTYP400vault ref {key} has an invalid autogen type {type}: {reason}
X401012VLTINV401invalid vault password
X401013VLTNEW401invalid new vault password {reason} {error}
X401902VLTPWI401vault import password incorrect or data corrupted
X403905CAPRTC403protected ca section is not ref resolvable {key}
X403906CONPRT403protected connection credential is not accessible {key}
X403907MIRPRT403private mirror key custody is not accessible {key}
X403907RDCPRT403replica document keys require the replica document store
X404905SECREQ404required vault secret {key} unresolved for {tenant} {stack} {environment} with {reason}
X404907SECNOF404secret {key} not found
X404986AGNCAM404autogen certificate {key} needs its {param} {ca_key}, which the vault does not hold
X409388VLTNMO409vault provider {provider} holds an item titled {path} that SHC did not write, so it is neither read nor written
X409807VLTRNP409vault secrets did not follow the rename of {source} to {target}, {prefix} still holds {count} of them on vault provider {provider}
X409902SECEXS409secret {key} already exists at scope {scope}
X409904SECAMB409autogen secret {key} for {tenant} {stack} {environment} exists but stores an empty value
X409905SECSHD409secret {key} cannot be written at scope {scope}: a {shadow_scope} row shadows it
X409906VLTCSH409node {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
X409908RDCMKY409replica document MAC key changed while minting
X409986VLTESN409there is no {what} on this estate to escrow: {held}
X409987VLTESV409the escrow is not current for {keys}; escrow the current key and record it with shc vault escrow record --what <key> --where <label>
X500101VLTKEK500vault kek salt failure {reason} {error}
X500102VLTDRP500vault 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}
X500103VLTCSP500vault cold-start plant failed on {target} {reason} {error}
X500141VLTCLK500vault password rotated and this node is locked: the new password is current, unlock with the new password
X500806VLTRNS500vault scope rename failed with {reason} {error}
X500912VLTDBS500database session required for vault {operation}
X500960PRVEXE500vault provider {provider} cli failed {stderr} {error}
X500961VLTCRP500vault crypto failure {op} {error}
X502221VLTPER502peer {node} refused vault {operation}: {reason}
X503902VLTNAV503vault not available with {reason} {error}
X503903VLTPWM503vault is locked
X503904VLTCSL503vault cold-start {operation} needs an unlocked vault on this node; run shc vault unlock first
X503909VLTUNS503vault password was not rotated because this node’s store swap is still ahead or a rebind is in progress
X503950PRVAPI503vault provider {provider} api returned {status} {body}

Source: modules/vip/compile, modules/vip
Count: 26

CodeHTTPMessage template
X200235VIPTIK200service VIP {what} tick failed: {error}
X200240VIPDRT200service vip drain of {deployment} timed out after {waited}, drain needs {revision}, unconfirmed routing nodes {nodes}
X200241VIPDRF200service VIP drain of {deployment} could not reach the store and tries again: {error}
X200242VIPDRL200service VIP drain of {deployment} was not released, its backends stay out of the VIP tables until the drain’s lease lapses: {error}
X200244VIPDRX200service 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
X200245VIPDRO200service 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
X200257VIPOWN200published ports withheld on node {node}: {ports}
X200286VIPLOP200published port {port}/tcp does not answer on [::1], {reason}
X200289VIPLBP200{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
X400230VIPTAB400service VIP table invalid, {reason}
X404238VIPGON404service VIP for {service} not allocated: service {id} no longer exists
X409232VIPFUL409service 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
X409236VIPRAC409service VIP allocation for {service} kept losing to another writer, retry
X409237VIPSTL409service VIP for {service} not allocated: service {holder}, which still exists, holds the VIP, not service {id}
X409239VIPOVL409service VIPs are off: the fabric CIDR {cidr} overlaps the VIP range {range}; move the fabric to a disjoint supernet to turn them on
X409243VIPUNR409replica 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}
X409249VIPNSF409replica 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
X409250VIPOVR409replica 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
X409251VIPNAP409replica 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
X500231VIPSTO500service VIP {op} failed in the store: {error}
X500234VIPAPL500service VIP rules not converged on this node, {reason}
X503233VIPNST503service VIP {op} has no store yet, the daemon has not opened the control plane
X503246VIPDRN503{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
X503247VIPDRS503{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}
X503248VIPDRU503{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
X503289VIPSCP503{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

CodeHTTPMessage template
X400149SCPDIR400containers_dir must not be empty
X400150SCPMAX400max_cached must be positive
X400154SCPTTL400negative_ttl must be positive