Restart & Operations

Run all commands on this page from the asp-compose/ deployment directory. After starting, recreating, or restarting services, or after applying configuration changes, run a complete deployment check:

./scripts/doctor.sh

1. Check service status

View all containers:

docker compose ps

STATUS should be running, and services with health checks should be healthy.

doctor.sh waits for every official long-running service to become running/healthy, then checks PostgreSQL, Redis, Django, custom definitions, and the RustFS/S3 bucket.

Admins can also open System Settings > Workers to view heartbeat, runtime state, and the latest polling result for all five background Workers. This page does not replace container status, business records, or log investigation.

2. View logs

List available service names:

docker compose config --services

Follow a service:

docker compose logs -f <service>

View the most recent 100 lines:

docker compose logs --tail=100 <service>

For example:

docker compose logs -f asp-frontend
docker compose logs --tail=100 asp-web

Nginx and backend process logs are also written under logs/.

3. Choose the correct operation

Scenario	Command
Restart processes in existing containers	docker compose restart
Apply .env or compose.override.yaml changes	docker compose up -d
Reload replaced certs/asp.crt and certs/asp.key	docker compose restart asp-frontend
Stop all services while preserving containers and data	docker compose stop
Start stopped services	docker compose up -d

Restart services

Restart all services:

docker compose restart

Restart Web/API services:

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

Restart background workers:

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

Apply configuration changes

After changing .env or compose.override.yaml:

docker compose up -d

Stop and start

docker compose stop
docker compose up -d

stop stops containers. down removes containers and the Compose network while preserving named volumes by default. down -v also deletes named volumes.

Do not delete volumes

Do not run docker compose down -v unless you explicitly intend to delete all persistent PostgreSQL, Redis, RustFS, and custom Python dependency data.

4. General troubleshooting

1. Check service status:

   docker compose ps

2. Find services that are not running/healthy.

3. Inspect the recent service logs:

   docker compose logs --tail=100 <service>

4. Fix the configuration or runtime problem, choose restart or up -d, then run:

   ./scripts/doctor.sh

Next Steps

• Environment Variables — Review .env settings and how to apply them.
• Backup & Restore — Create or restore a stopped full backup.
• Upgrade — Download the latest release and update ASP.
• Custom Content Deployment — Deploy custom content and dependencies.
• Service Management UIs — Access Redis Stack UI and RustFS Console.