Process Management

Danger

There is no PM2 anywhere, and none of the process names below exist. This page describes the host that was destroyed on 2026-08-03. The <service>-<branch> convention it documents came from running two branches on one machine; prod and dev are now separate VMs running one container each, which is also why the analyzer is 9000 on prod and 9001 on dev.

Kept for reading old runbooks and commit messages. For anything you intend to run, see the in-house deploy platform or use docker ps / docker logs — and note that the per-service cli/*.cjs scripts and cli/logrite-manager.js manage nothing any more either.

PM2 Process Names

All services follow the naming convention: <service>-<branch>

PM2 Name	Service	Port
frontend-main	Frontend (main)	3000
frontend-dev	Frontend (dev)	3001
backend-main	Backend (main)	8080
backend-dev	Backend (dev)	8081
analyzer-main	Analyzer (main)	9000
analyzer-dev	Analyzer (dev)	9001
semantic-search-main	Semantic Search	9100
ai-service-main	AI Service	9300
agent-runner-main	Agent Runner (proposed)	9400
mcp-server-main	MCP Server	9500
webhook-server	Webhook Server	9999
deployment-notifier	Deployment Notifier	—

Essential PM2 Commands

# List all processes
pm2 list

# Show detailed status
pm2 show frontend-main

# View logs (last 100 lines)
pm2 logs frontend-main

# Follow logs
pm2 logs frontend-main --lines 200 --raw

# Restart a service
pm2 restart frontend-main

# Stop a service
pm2 stop frontend-main

# Delete from PM2 (remove process)
pm2 delete frontend-main

# Restart all
pm2 restart all

# Stop all
pm2 stop all

# Save current process list (persist across reboots)
pm2 save

# Resurrect saved process list
pm2 resurrect

Master CLI (Preferred)

Use logrite-manager.js instead of PM2 directly when possible:

cd /root/logrite

# Status of all Logrite services
./cli/logrite-manager.js status

# Start/stop/restart specific service
./cli/logrite-manager.js start frontend main
./cli/logrite-manager.js stop backend dev
./cli/logrite-manager.js restart analyzer main

# View logs
./cli/logrite-manager.js logs ai-service main

# Start all (with OpenSearch health check)
./cli/logrite-manager.js start-all

# Stop all
./cli/logrite-manager.js stop-all

PM2 Startup on Reboot

# Generate startup script
pm2 startup
# This outputs a command like:
# sudo env PATH=... pm2 startup systemd -u root --hp /root

# Run the output command, then save state
pm2 save

Deployment Notifier

The deployment notifier listens for PM2 events and sends Discord notifications:

# Start as daemon
pm2 start /root/logrite/cli/deployment-notifier.js --name deployment-notifier

# Include in save
pm2 save