Search…
TVO-4.2
Deployment Guide
TrilioVault Appliance Administration Guide
Admin Guide
Troubleshooting
Important log files
On the TrilioVault Nodes
The TrilioVault Cluster contains multiple log files.
The main log is workloadmgr-workloads.log, which contains all logs about ongoing and past TrilioVault backup and restore tasks. It can be found at:
/var/log/workloadmgr/workloadmgr-workloads.logThe next important log is the workloadmgr-api.log, which contains all logs about API calls received by the TrilioVault Cluster. It can be found at:
/var/log/workloadmgr/workloadmgr-api.logThe log for the third service is the workloadmgr-scheduler.log, which contains all logs about the internal job scheduling between TrilioVault nodes in the TrilioVault Cluster.
/var/log/workloadmgr/workloadmgr-scheduler.logThe last but not least service running on the TrilioVault Nodes is the wlm-cron service, which is controlling the scheduled automated backups.
/var/log/workloadmgr/workloadmgr-workloads.logIn 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.logCanonical Openstack is having these logs inside the workloadmgr container.
TrilioVault Datamover service logs on RHOSP
Datamover API log
The log for the TrilioVault Datamover API service is located on the nodes, typically controller, where the TrilioVault Datamover API container is running under:
/var/log/containers/trilio-datamover-api/dmapi.logDatamover log
The log for the TrilioVault Datamover service is located on the nodes, typically compute, where the TrilioVault Datamover container is running under:
/var/log/containers/trilio-datamover/tvault-contego.logIn 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.logTrilioVault Datamover service logs on Kolla Openstack
Datamover API log
The log for the TrilioVault Datamover API service is located on the nodes, typically controller, where the TrilioVault Datamover API container is running under:
/var/log/kolla/trilio-datamover-api/dmapi.logDatamover log
The log for the TrilioVault Datamover service is located on the nodes, typically compute, where the TrilioVault Datamover container is running under:
/var/log/kolla/triliovault-datamover/tvault-contego.logIn 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.logTrilioVault Datamover service logs on Ansible Openstack
Datamover API log
The log for the TrilioVault Datamover API service is located on the nodes, typically controller, where the TrilioVault Datamover API container is running.
Log into the dmapi container using
lxc-attach command (example below).lxc-attach -n controller_dmapi_container-a11984bfThe log file is then located under:
/var/log/dmapi/dmapi.logDatamover log
The log for the TrilioVault Datamover service is typically located on the compute nodes and the logs can be found here:
/var/log/tvault-contego/tvault-contego.logIn 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.logLast modified 8mo ago