Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Recover an interrupted update
Operations and updates

Recover an interrupted update

Bring an update that stopped partway to a known state before you try another one.

Finish or reverse an update

  1. Run elowen update to start an update.
  2. If a run was interrupted, run elowen update --recover before trying again.

The recovery command removes staged files that were never swapped in, rolls back a swap that was interrupted before it was proven, or finishes publishing a commit that was proven.

The updater fetches the newest release the licence covers, verifies the download, and installs it while Chetty keeps running; the services stop only briefly to switch packages and restart. There is no npm-based release channel, and a source checkout is never replaced by a licensed release.

Automatic updates are opt-in under Settings → System.

When a refused update names the licence

A refused update reports the licence server's reason instead of "up to date". A revoked licence is the usual one.

Renew an expired licence and run the update again. Licence and activation covers renewal and activation.

When a new version will not start

  1. Keep the logs and read the service journal.
  2. Restore the backup you took before the update, database and instance folder together.
  3. Do not delete migration or lock files as a workaround.

A database migration runs when a newer version starts, so make a recoverable backup before a version jump. A rollback restores the previous executable and plugin set but does not reverse a migration.