Zigcube

Reference

Diagnostic codes

Every failure zcube reports has one of these codes. zcube explain <code> prints the same text offline.

CodeSummaryBlame
ZC-E0101no such resourceuser
ZC-E0102can't reach zcube-serverenvironment
ZC-E0103zcube-server sent a reply the client can't readenvironment
ZC-E0104the request can't be understooduser
ZC-E0105the service changed while it was being applieduser
ZC-E0106the server's configuration can't be useduser
ZC-E0107can't listen on the server's addressenvironment
ZC-E0108the server is at one of its limitsenvironment
ZC-E0109the service file can't be readuser
ZC-E0110the service file isn't validuser
ZC-E0111the command line can't be understooduser
ZC-E0112the server address can't be useduser
ZC-E0113apply needs an answer and there is no terminaluser
ZC-E0114the apply was declineduser
ZC-E0115can't write the outputenvironment
ZC-E0116can't use the state directoryenvironment
ZC-E0117there is no failure to bundleuser
ZC-E0118no such diagnostic codeuser
ZC-W0119--no-redact keeps secrets in the bundleuser
ZC-E0120zcube ran out of memoryenvironment
ZC-E0121the lease settings cannot fence an agent in timeuser
ZC-E0122zcube local can't find or start the server or agentenvironment
ZC-E0123the local server or agent did not come upenvironment
ZC-E0124another zcube local command is runningenvironment
ZC-E0130a job is not validuser
ZC-E0131a different job already has that nameuser
ZC-E0132there are too many jobsuser
ZC-E0133no job by that nameuser
ZC-E0134the time to submit this job has passeduser
ZC-E0201can't reach the store backendexternal
ZC-E0202the store backend failed an operationexternal
ZC-E0203that revision was compacted awayuser
ZC-E0204that revision does not exist yetuser
ZC-E0205the lease has expired or was revokedenvironment
ZC-E0206the request exceeds a store limituser
ZC-E0207the store has no free capacity for thisenvironment
ZC-E0208the store database is busyenvironment
ZC-E0209the store database is damaged or not a storeexternal
ZC-E0210the store database is from a newer zcubeuser
ZC-E0211the store backend refused the credentialsuser
ZC-E0212the store database does not existuser
ZC-E0213the store connection dropped during an operationexternal
ZC-E0214the store has no chain hash for that revisionuser
ZC-E0215the store went backwards or forkedexternal
ZC-E0216the remembered revision file is unusableexternal
ZC-E0301a stored record can't be readexternal
ZC-E0302there is more to reconcile than one pass holdsenvironment
ZC-E0303a stored record is from a newer releaseenvironment
ZC-E0307a job's stored records contradict each otherexternal
ZC-W0307a report for an ended job was droppedenvironment
ZC-W0308a job waits: no node can take it nowuser
ZC-E0401a repair needs confirminguser
ZC-E0402the node has no open allocation findinguser
ZC-E0403the node's accounting changed during the repairuser
ZC-E0404a node's accounting disagrees with its assignmentsuser
ZC-E0501the runtime does not know that containerenvironment
ZC-E0502the runtime failed an operationenvironment
ZC-E0503the agent can't reach zcube-serverenvironment
ZC-E0504zcube-server refused the agent's requestexternal
ZC-E0505the agent's configuration can't be useduser
ZC-E0506the agent's state directory can't be usedenvironment
ZC-E0507the agent can't start a container's supervisorenvironment
ZC-E0508the container's command can't be runuser
ZC-E0509the container's supervisor is goneenvironment
ZC-E0510the agent's tenure on its node has endedenvironment
ZC-E0511the image does not give the tree the service namesuser
ZC-E0512the node can't apply limits: no user systemd busenvironment
ZC-E0513this host can't run Zigbox containersenvironment
ZC-E0514the service does not fit Zigbox's limitsuser
ZC-E0515a swarm fetch outlived its kill, so the image was not pulledenvironment
ZC-E0521the agent could not tell how a run endedenvironment
ZC-E0522a run's start record is missing or damagedenvironment
ZC-W0501the agent fenced itself and registered againenvironment
ZC-W0503a job reached its deadline and was stoppeduser
ZC-E0601a tree could not be fetched from any peer or the registryexternal
ZC-W0601a peer sent a chunk that does not match its hashexternal
ZC-W0602a peer's chunk list does not match its digestexternal
ZC-E0801a peer's credential is not signed by this clusterexternal
ZC-E0802a peer's credential is expired or not yet validexternal
ZC-E0803the peer is not the node that was asked forexternal
ZC-E0804a peer handshake failedexternal
ZC-E0805a peer record was refusedexternal
ZC-E0806a peer key or trust file can't be useduser
ZC-E0807a node was refused a credential: it was removeduser
ZC-E0808a peer's handshake was refused: its address is over a limitexternal
ZC-E0809a certificate is malformed or outside the boundsexternal
ZC-E0810a certificate is not signed by the pinned anchorexternal
ZC-E0811a certificate is expired or not yet validexternal
ZC-E0812a certificate names another server than the one asked forexternal
ZC-E0813a TLS handshake was refusedexternal
ZC-E0814the TLS client certificate was not asked for, or was refusedexternal
ZC-E0815a TLS record failed its checksexternal
ZC-E0816a TLS connection ended without close_notifyexternal
ZC-E0817an identity could not be issueduser
ZC-E0818a TLS peer needs something zcube does not offerexternal
ZC-E0819a certificate is of another kind than this use needsexternal
ZC-E0820the key behind the client certificate did not signenvironment
ZC-B0001zcube hit an internal errorinternal
ZC-B0002zcube failed in a way it should notinternal
ZC-B0003allocation accounting disagrees with assignmentsinternal
ZC-B0004zcube could not map how a job endedinternal
ZC-B0005a job's run record is larger than a run may beinternal