It is recommended to install all ClusterCockpit components in a common directory, e.g. /opt/monitoring
, var/monitoring
or var/clustercockpit
.
In the following we use /opt/monitoring
.
Two systemd services run on the central monitoring server:
/opt/monitoring/cc-backend
./opt/monitoring/cc-metric-store
.ClusterCockpit is deployed as a single binary that embeds all static assets.
We recommend keeping all cc-backend
binary versions in a folder archive
and
linking the currently active one from the cc-backend
root.
This allows for easy roll-back in case something doesn’t work.
cc-backend
is started with root rights to open the privileged ports (80 and
443). It is recommended to set the configuration options user
and group
, in
which case cc-backend
will drop root permissions once the ports are taken.
You have to take care, that the ownership of the ./var
folder and
its contents are set accordingly.This example assumes the DB and job archive versions did not change. In case the new binary requires a newer database or job archive version read here how to migrate to newer versions.
sudo systemctl stop clustercockpit.service
cc-backend
binary to /opt/monitoring/cc-backend/archive
(Tip: Use a
date tag like YYYYMMDD-cc-backend
). Here is an example:cp ~/cc-backend /opt/monitoring/cc-backend/archive/20231124-cc-backend
cc-backend
root to current versionln -s /opt/monitoring/cc-backend/archive/20231124-cc-backend /opt/monitoring/cc-backend/cc-backend
sudo systemctl start clustercockpit.service
sudo systemctl status clustercockpit.service
sudo journalctl -u clustercockpit.service
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.