Package sbin scripts#
The CLP package provides shell scripts in the sbin/ directory for managing and operating CLP.
start-clp.sh for starting CLP services.
stop-clp.sh for stopping CLP services.
Admin tools for managing archives and datasets.
start-clp.sh#
Starts all CLP services.
Usage#
sbin/start-clp.sh [OPTIONS]
Options#
Option |
Description |
|---|---|
|
CLP package configuration file. Defaults to |
|
Docker restart policy for containers. See Restart policies below. Defaults to |
|
Validate configuration and prepare directories without starting services. Useful for verifying configuration before deployment. |
|
Enable debug logging. |
Restart policies#
The --restart-policy option accepts the following values:
Policy |
Description |
|---|---|
|
Never restart containers automatically. |
|
Always restart containers regardless of exit status. |
|
Restart containers unless explicitly stopped. |
|
Restart only if the container exits with a non-zero status. |
|
Restart on failure up to |
Note
Restart policies are primarily meant for handling container failures.
Use
stop-clp.shto properly stop CLP.Initialization jobs (
db-table-creator,results-cache-indices-creator) always useon-failure:3regardless of this setting.Docker daemon restart (e.g., system reboot or
systemctl restart docker) may cause some services to restart unexpectedly:If
stop-clp.shwas run beforehand, services stay stopped since containers are removed, not just stopped.With
on-failurepolicies, the daemon records container exit codes on shutdown. On restart, it restarts containers that exited non-zero. Most CLP services exit cleanly (code 0) and won’t restart, but some may restart and eventually fail without their dependencies.If services restart unexpectedly after a Docker daemon restart, run
stop-clp.shto clean up any partially started services before runningstart-clp.sh.
stop-clp.sh#
Stops all running CLP services.
Usage#
sbin/stop-clp.sh [OPTIONS]
Options#
Option |
Description |
|---|---|
|
CLP package configuration file. Defaults to |