Restart & Operations

This page covers common production operations for Docker Compose deployments, including status checks, logs, restarts, stop/start commands, and custom content changes.

1. Check current status

docker compose ps
./scripts/doctor.sh

doctor.sh first waits for every official long-running service to become running/healthy, then checks PostgreSQL, Redis, Django, custom definitions, and the RustFS/S3 bucket. In production, run it after upgrades, restarts, or custom definition changes.

2. View logs

View container stdout and stderr:

docker compose logs -f asp-frontend
docker compose logs -f asp-web
docker compose logs -f asp-worker-elk-action
docker compose logs -f asp-worker-dashboard-cache

View mounted process logs under the deployment directory:

tail -f logs/django.log
tail -f logs/asgi.log
tail -f logs/agentic-module-worker.log
tail -f logs/agentic-case-analysis-worker.log
tail -f logs/agentic-playbook-worker.log
tail -f logs/elk-action-worker.log
tail -f logs/dashboard-cache-worker.log

3. Restart services

Restart all Compose services:

docker compose restart

Restart only the Web/API entrypoints:

docker compose restart asp-frontend asp-web asp-asgi

Restart only background workers:

docker compose restart asp-worker-module asp-worker-case-analysis asp-worker-playbook asp-worker-elk-action asp-worker-dashboard-cache

After changing .env, compose.yaml, or port mappings, run docker compose up -d to apply the Compose definition. When only replacing certificates or asking processes to reload configuration, use docker compose restart <service>.

4. Stop and start

Stop containers while keeping data volumes:

docker compose stop

Start again:

docker compose up -d

Do not run docker compose down -v in production unless you explicitly want to delete PostgreSQL, Redis, and RustFS Docker volumes.

5. Dashboard cache troubleshooting

If the Dashboard says its cache is preparing, keeps returning 503, or warns that data is stale, check the cache worker first:

docker compose ps asp-worker-dashboard-cache
docker compose logs --tail=100 asp-worker-dashboard-cache

If the service exists but is not refreshing normally, restart it:

docker compose restart asp-worker-dashboard-cache

The worker generates the 24h, 7d, and 30d data in sequence. On first startup or with a large dataset, the Dashboard may not show data until the first refresh finishes.

6. Custom content changes

• If only Module, Playbook, or SIEM YAML files changed, run Refresh / Validate in Custom Console.
• If custom/requirements.txt or shared helper modules changed, reinstall dependencies and restart related backend services.

docker compose run --rm asp-custom-deps --index-url https://pypi.org/simple
docker compose restart asp-web asp-worker-module asp-worker-playbook

Next Steps

• Backup & Restore — Understand the backup scope for PostgreSQL, Redis, RustFS, and the custom directory.
• Upgrade — Review the release package upgrade flow.
• Custom Console — Refresh and validate custom Module, Playbook, and SIEM YAML definitions.