Starting, Stopping, and Checking PCR360
PCR360 runs as a systemd service that manages all Docker containers. All commands below should be run from your installation directory (/opt/pcr360) unless noted otherwise.
Start, Stop, and Restart
Start all services
sudo systemctl start pcr360
Stop all services
sudo systemctl stop pcr360
Restart all services
Use this after making changes to .env or any configuration that affects all containers.
sudo systemctl restart pcr360
Restart a single container
Use this after editing config/prod-custom.ini or other changes that only affect one service.
cd /opt/pcr360
# Restart the production web container only
sudo docker compose restart web-prod
# Restart the test web container only
sudo docker compose restart web-test
Check Status
cd /opt/pcr360
sudo bash scripts/status.sh
This shows all running containers and their health. The web-prod container should show healthy. If it shows starting, wait 30–60 seconds and check again. If it shows unhealthy, check the logs.
View Logs
PCR360 application logs live inside the web container. Use the logs.sh script to access them.
List available log files
sudo bash scripts/logs.sh prod list
sudo bash scripts/logs.sh test list
Tail a log file (live)
# Tail the main application log (Ctrl+C to stop)
sudo bash scripts/logs.sh prod pcr360
# Tail the cron log
sudo bash scripts/logs.sh prod cron
# Tail with more lines shown
sudo bash scripts/logs.sh prod pcr360 200
View the last N lines without following
sudo bash scripts/logs.sh prod pcr360 100
View the auto-update log
sudo bash scripts/logs.sh update
sudo bash scripts/logs.sh update 200
Docker container output (startup errors)
If a container won't start, check its raw Docker output:
cd /opt/pcr360
docker compose logs web-prod --tail 100
docker compose logs web-test --tail 100
Auto-Start on Reboot
The pcr360 systemd service is configured to start automatically when the server boots. To verify this is enabled:
sudo systemctl is-enabled pcr360
If it returns disabled, enable it:
sudo systemctl enable pcr360