Important log files
On the Trilio Nodes
The Trilio Cluster contains multiple log files.
The main log is workloadmgr-workloads.log, which contains all logs about ongoing and past Trilio backup and restore tasks. It can be found at:
/var/log/workloadmgr/workloadmgr-workloads.log
The next important log is the workloadmgr-api.log, which contains all logs about API calls received by the Trilio Cluster. It can be found at:
/var/log/workloadmgr/workloadmgr-api.log
The log for the third service is the workloadmgr-scheduler.log, which contains all logs about the internal job scheduling between Trilio nodes in the Trilio Cluster.
/var/log/workloadmgr/workloadmgr-scheduler.log
The last but not least service running on the Trilio Nodes is the wlm-cron service, which is controlling the scheduled automated backups.
/var/log/workloadmgr/workloadmgr-workloads.log
In the case of using S3 as a backup target is there also a log file that keeps track of the S3-Fuse plugin used to connect with the S3 storage.
/var/log/workloadmgr/s3vaultfuse.py.log
Canonical Openstack is having these logs inside the workloadmgr container.
Trilio Datamover service logs on RHOSP
Datamover API log
The log for the Trilio Datamover API service is located on the nodes, typically controller, where the Trilio Datamover API container is running under:
/var/log/containers/trilio-datamover-api/dmapi.log
Datamover log
The log for the Trilio Datamover service is located on the nodes, typically compute, where the Trilio Datamover container is running under:
/var/log/containers/trilio-datamover/tvault-contego.log
In case of S3 being used in the log for the S3 Fuse plugin located on the same nodes under:
/var/log/containers/trilio-datamover/tvault-object-store.log
Trilio Datamover service logs on Kolla Openstack
Datamover API log
The log for the Trilio Datamover API service is located on the nodes, typically controller, where the Trilio Datamover API container is running under:
/var/log/kolla/trilio-datamover-api/dmapi.log
Datamover log
The log for the Trilio Datamover service is located on the nodes, typically compute, where the Trilio Datamover container is running under:
/var/log/kolla/triliovault-datamover/tvault-contego.log
In case of S3 being used in the log for the S3 Fuse plugin located on the same nodes under:
/var/log/kolla/trilio-datamover/tvault-object-store.log
Trilio Datamover service logs on Ansible Openstack
Datamover API log
The log for the Trilio Datamover API service is located on the nodes, typically controller, where the Trilio Datamover API container is running.
Log into the dmapi container using lxc-attach
command (example below).
lxc-attach -n controller_dmapi_container-a11984bf
The log file is then located under:
/var/log/dmapi/dmapi.log
Datamover log
The log for the Trilio Datamover service is typically located on the compute nodes and the logs can be found here:
/var/log/tvault-contego/tvault-contego.log
In case of S3 being used in the log for the S3 Fuse plugin located on the same nodes under:
/var/log/tvault-object-store/tvault-object-store.log
Last updated