SARION

Troubleshooting the command line

The error messages and exit codes of the SARION command line, with the fix for each, and what to send support.

Where to find it Terminal, sarion

Exit codes

A command that works exits with 0. Other codes:

  • 1: the command failed. Read the message.
  • 2: the request is invalid, for example an unknown command or a project that is too large to share.
  • 3: you are not signed in, the secure storage is unavailable, or the account does not match.
  • 4: approval is required, or a permission or policy denied it.
  • 5: the result is uncertain, or a sign-out is still pending. Use sarion recover.
  • 7: something this machine or release needs is missing, or verification failed.
  • 130: you stopped it (Ctrl+C).

Messages and fixes

  • KEYCHAIN_UNAVAILABLE: OS credential storage unavailable; explicitly select encrypted storage: this machine has no usable secure storage. Add --encrypted-store to the command (see Sign in from the command line).
  • UNAUTHENTICATED: Run sarion login first: sign in with sarion login, or check that you used the same --encrypted-store and profile as when you signed in.
  • APPROVAL_REQUIRED: Project init requires --permission-mode workspace-write in scripts: a script cannot answer a question. Give the permission mode named in the message, or run the command in a terminal.
  • INVALID_REQUEST: Unknown command ...: a typing mistake. Run sarion --help.
  • Sign-in, credit or model refused: run sarion whoami and sarion endpoint doctor. Renew an expired credential with sarion login. A plan that is not active or a balance that is empty is fixed in the web app (see Billing and credits). Reinstalling does not remove a revocation.
  • Installation check fails (signature or checksum): stop. Do not install. Compare the fingerprint with the one on the Terminal (CLI) page in SARION, then download a clean release. Never turn the checks off.
  • sarion opens the older tool: run ~/.local/share/sarion-cli-v2/bin/sarion --version, or put that folder first in your PATH.
  • Installation fails with EEXIST: something already uses that folder. Install into a new folder; do not force it, delete your files or use administrator rights.
  • The sandbox is not available: run sarion sandbox doctor. On Linux install bubblewrap and make sure prlimit (util-linux) exists. A program is never run without its sandbox.
  • Windows refuses a program or a Git change: native Windows does this on purpose. Use WSL2.
  • A run says the effect is uncertain: see Permissions, recovery and credits.

Still stuck

Write to support@sarion.dev or support@volta.quest with the output of sarion --version, the exact message, the exit code and what you ran. Do not send passphrases, access tokens or file contents. See Contact.

Common questions

Why does every command say KEYCHAIN_UNAVAILABLE?

Your machine has no secure storage session. Use --encrypted-store on every command that needs your login.

Why is a Git change refused on Windows?

Native Windows does not run programs or change Git in this release. Use WSL2.