Atomic Deployment Messages
See Errors & Warnings Catalog for the full index, and Errors & Warnings Guide for a narrative explanation of message categories, exit codes, and common fixes.
Messages from the ssi atomic command, which manages atomic deployments using a directory-and-symlink pattern.
| Message | Exit Code | Hint |
|---|---|---|
| Bootstrap complete: Created [destination] and symlink [link] | ||
| ⚛️ Atomic deployment completed successfully to [path] | ||
| ❌ Parent directory '[parent path]' does not exist. Create it first before using --init. | 4 | 💡 Create the parent directory with `mkdir -p` before running `ssi atomic --init` |
| ❌ --init requires the symlink to be absent, but '[path]' already exists. | 1 | 💡 Remove the existing symlink first, or run without --init to use the existing atomic deployment setup |
| Atomic deploy requires symlink at [path] | ||
| 🔗 Updating symlink [link] -> [target] | ||
| --suffix-length [length] ignored for blue-green deployments | 💡 Blue-green deployments use fixed .blue/.green suffixes — --suffix-length has no effect | |
| ❌ Cannot extract deployment directory name from: [path] | 4 | 💡 The deployment directory path must have a valid filename component — paths ending in `..` or containing non-UTF-8 components are not valid deployment directories |
| ❌ Cannot resolve symlink: [path] (💬io_kind) | 1 | 💡 The symlink may be broken or pointing to a non-existent target — check with `ls -la` |
| ❌ System clock is before the Unix epoch — cannot generate timestamp-based suffix (clock is [error message] before epoch) | 1 | |
| 🟦 blue | ||
| 🟩 green | ||
| Create symlink at [path] pointing to deployment directory | ||
| 🔧 Creating atomic deployment config with symlink: [link] | ||
| ❌ The deploy command was invoked with no deploy_dir — the deploy path must be resolved to an absolute path before reaching this branch (programming error in router.rs) | 1 | |
| 🪂 Deployed to: [path] | ||
| 🪂 Deploying to initial directory: [path] | ||
| Deploying to opposite color: [deployment color] | ||
| ❌ Deployment directory already exists: [path] | 1 | 💡 A generated deployment suffix collided with an existing directory. Use --suffix-timestamp, remove the directory if it is a stale artifact, or run again for a new random suffix. |
| Current deployment color: [deployment color] | ||
| ❌ A directory-deploy operation was attempted with no deploy_dir — the deploy path must be resolved to an absolute path before reaching this branch (programming error in router.rs) | 1 | |
| Filesystem init for blue-green cleanup failed ([path]): [error message] | ||
| ❌ Filesystem initialization failed for [path] (💬io_kind) | 4 | 💡 Check that the path exists, the parent directory is accessible, and you have write permission |
| 🎲 Generated [type] suffix: [deployment suffix] | 💡 This value is part of the deployment directory name — keep it unique per release so runs do not collide | |
| ❌ getrandom::fill() failed — the system entropy source is unavailable, which prevents atomic-suffix generation. Error: [error message] | 1 | |
| ❌ Deployment base name is empty or a path component: [name] | 1 | 💡 The deployment directory name must have a non-empty base before the suffix (e.g., 'site' in 'site.blue') — names like '.blue' or '..green' have no valid base |
| ❌ Invalid deployment directory name: [name] | 1 | 💡 Name must end with .blue or .green, or with a 6–40 character alphanumeric hash after '-' or '.' (e.g., site.abc123def456 or site-abc123def456) |
| 🪧 New deployment directory: [path] | ||
| ❌ Not a symlink: [path] | 1 | 💡 Atomic deployment expects a symlink at this path — use `ssi atomic --init` to set up the symlink |
| 🧹 Old deployment already cleaned up: [path] | ||
| OS error during cleanup of [path]: [error message] — checking whether cleanup succeeded | 💡 The directory may still exist or may have been partially removed — check file permissions and whether any process has files open | |
| ❌ Failed to remove old deployment: [path] (directory still exists, nothing removed) | 10 | 💡 Check file permissions and whether any process has files open in the old deployment directory |
| ❌ **CRITICAL:** Partial removal failure: [path] (directory partially removed — **manual cleanup required**) | 11 | 💡 Manually inspect and remove the partially deleted directory — some files may still remain |
| ✔️ Old deployment [path] removed successfully | ||
| 🧹 Removing old deployment: [path] | ||
| ❌ Deployment-suffix padding in generate_unified_suffix (helpers.rs) could not grow the base suffix to length 6 within the attempt cap — each iteration should append a random character; this loop should be unreachable (programming error in ssi-atomic). | 1 | |
| ❌ --suffix-length requested [current] but the maximum for random suffixes is [max] | 1 | 💡 Use a shorter --suffix-length value, or use --suffix-timestamp instead |
| 🔗 Created symlink: [link] -> [target] | ||
| ❌ Failed to read symlink metadata: [path] (💬io_kind) | 1 | 💡 The symlink may be broken, or you may lack permission — verify with `ls -la` on the link and its target |
| ❌ Symlink not found: [path] | 1 | 💡 Create the deployment symlink first with `ssi atomic --init`, or check the path for typos |
| ❌ Symlink [path] resolves to [target], which is not a directory | 1 | 💡 The deployment symlink must point to a directory — fix the symlink target or recreate it with `ssi atomic --init` |
| 🔗 Successfully updated symlink: [link] -> [target] | ||
| Failed to remove temporary symlink: [path] ([error message]) | 💡 This is best-effort cleanup — the main operation may still succeed, but stale temp files may remain | |
| ✔️ Validated symlink: [link] -> [target] | ||
| Validated symlink: [link] -> [target] |