Deployment AIO fixed live entered FATAL state

[SloCompTech]

Description

Resolved Docker AIO (All in one) Plane image issues with starting live process.

live process fails to start after few attempts:

2025-10-02 13:56:29,408 INFO Set uid to user 0 succeeded
2025-10-02 13:56:29,412 INFO supervisord started with pid 51
...
2025-10-02 13:56:30,425 INFO spawned: 'live' with pid 59
...
2025-10-02 13:56:30,482 WARN exited: live (exit status 1; not expected)
...
2025-10-02 13:56:32,027 INFO spawned: 'live' with pid 129
...
2025-10-02 13:56:32,082 WARN exited: live (exit status 1; not expected)
2025-10-02 13:56:34,086 INFO spawned: 'live' with pid 136
2025-10-02 13:56:34,141 WARN exited: live (exit status 1; not expected)
2025-10-02 13:56:37,300 INFO spawned: 'live' with pid 146
2025-10-02 13:56:37,354 WARN exited: live (exit status 1; not expected)
2025-10-02 13:56:38,355 INFO gave up: live entered FATAL state, too many start retries too quickly
2025-10-02 14:00:41,202 INFO exited: migrator (exit status 0; expected)

Looked in live.err.log and it clearly shows that there is an issue with starting server (modules not found):

Node.js v22.19.0
node:internal/modules/cjs/loader:1386
  throw err;
  ^

Error: Cannot find module '/app/live/live/server.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)
    at Function._load (node:internal/modules/cjs/loader:1192:37)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

I resolved the issue by updating path and run command for live proces in supervisor.conf.

Type of Change

• [ x] Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

References

• #7516
• #7517

Summary by CodeRabbit

• Chores
  • Updated runtime configuration for the live service to point to the compiled server build and correct working directory.
  • Aligned process manager settings with current build output for smoother deployments and more consistent startup behavior.
  • No changes to features or interface; users should experience the same functionality with improved stability.
  • No impact on other services or programs in the deployment configuration.

[coderabbitai]

Walkthrough

Updated supervisor configuration for the live service to point to a new working directory and Node entrypoint, switching from /app/live and node live/server.js to /app/live/apps/live and node ./dist/server.js. No other program definitions were changed.

Changes

Cohort / File(s)	Summary of changes
Supervisor config update deployments/aio/community/supervisor.conf	For program "live": directory updated to /app/live/apps/live; command updated to sh -c "node ./dist/server.js". No other fields modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix: docker node_modeles symlink path matching with pnpm path in live server #7605 — Adjusts live server startup paths to the apps/live distribution structure, mirroring the updated directory and Node entrypoint.

Suggested reviewers

• Prashant-Surya
• Copilot

Poem

In tunnels of configs, I hop with delight,
Tweaking a path for the server to light.
From live to apps/live, I bounce with a grin,
Dist’s shiny entry lets engines spin.
Thump-thump goes deploy—ship it tonight! 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The description clearly outlines the problem, includes relevant log excerpts, describes the fix applied, and links related issues, but it omits the required “Test Scenarios” section from the repository’s PR template.	Please add a “Test Scenarios” section that details how you verified the fix, including the commands run, expected behavior, and observed results, to fully comply with the PR description template.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title accurately references the main change—fixing the live process entering a FATAL state in the AIO deployment—but its phrasing is awkward and could be clearer without losing specificity.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 794271a and 962b886.

📒 Files selected for processing (1)

• deployments/aio/community/supervisor.conf (1 hunks)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

LGTM! Path correction aligns with other services.

The updated directory and command fix the MODULE_NOT_FOUND error by correcting the path from /app/live/live/server.js (which doesn't exist) to /app/live/apps/live/dist/server.js. This now follows the same structural pattern as the web, space, and admin services.

Please verify that the build process for the live service produces the compiled output at /app/live/apps/live/dist/server.js:

---

🏁 Script executed:

#!/bin/bash
# Description: Verify the live service build output location exists in the Docker image.
# Expected: Find Dockerfile or build scripts that place the live server at the new path.

# Search for Dockerfiles that might set up the live service
fd -e Dockerfile -e dockerfile | xargs rg -l "live"

# Search for build configurations or scripts that reference the live service structure
rg -g '!node_modules' -g '!*.log' "live/apps/live|apps/live" --type-add 'config:*.{json,yml,yaml,conf}' -t config

# Look for package.json or build scripts in the live service directory
fd "package.json" | xargs rg -l "live" | head -5

Length of output: 2212

---

🏁 Script executed:

#!/bin/bash
# Check output directory in tsconfig.json for apps/live
echo "=== tsconfig.json outDir ==="
rg -n '"outDir"' -n apps/live/tsconfig.json

# Check build script in package.json for apps/live
echo "=== package.json build script ==="
rg -C2 '"scripts"' -n apps/live/package.json

# Inspect build steps in Dockerfile.live and Dockerfile.dev
echo "=== apps/live/Dockerfile.live (lines 1-200) ==="
sed -n '1,200p' apps/live/Dockerfile.live
echo "=== apps/live/Dockerfile.dev (lines 1-200) ==="
sed -n '1,200p' apps/live/Dockerfile.dev

Length of output: 2955

---

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	directory=/app/live/apps/live
	command=sh -c "node ./dist/server.js"
	directory=/app/live/apps/live
	command=sh -c "node ./dist/start.js"

🤖 Prompt for AI Agents

In deployments/aio/community/supervisor.conf around lines 99 to 100, the
supervisor command uses node ./dist/server.js but the project’s real runtime
entrypoint is start.js; update the command to run the correct entrypoint (e.g.,
node ./dist/start.js or the package start wrapper as required) so supervisor
launches the actual application entrypoint, and ensure the working directory
remains /app/live/apps/live.