Skip to content

Deployment AIO fixed live entered FATAL state #7893

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sriramveeraghanta merged 1 commit into from
Oct 6, 2025
Merged

Deployment AIO fixed live entered FATAL state #7893

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions deployments/aio/community/supervisor.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,8 +96,8 @@ priority=20


[program:live]
directory=/app/live
command=sh -c "node live/server.js"
directory=/app/live/apps/live
command=sh -c "node ./dist/server.js"
Comment on lines +99 to +100
Copy link
Contributor

@coderabbitai coderabbitai bot Oct 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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.

autostart=true
autorestart=true
stdout_logfile=/app/logs/access/live.log
Expand Down