Cause

This issue occurs if logs consume a lot of space in NFS storage.

Solution

Follow these steps to fix this issue:

1. Run the following command to identify the logging persistent volume name:

   kubectl get pvc -n $CDF_NAMESPACE itom-logging-vol -o json|jq -r .spec.volumeName

2. Run the following commands to identify the NFS server and NFS path that the logging persistent volume is mounted to. Replace <logging PV name> with the persistent volume name that you identified in the previous step.

   kubectl get pv <logging PV name> -o json|$CDF_HOME/bin/jq -r '.spec.nfs.server'
   kubectl get pv <logging PV name> -o json|$CDF_HOME/bin/jq -r '.spec.nfs.path'

3. Log in to the NFS server that you identified in the previous step and go to /var/vosls/itom/<log file directory path>. The <log file directory path> depends on whether logging volumes are created manually or by using the storage provisioner.

4. Identify and delete the old log files (generated by OMT and Operations Bridge capabilities) that are no longer required.

5. Configure log rotation or deletion to avoid encountering this issue again. For detailed steps, see Change the log rotation or delete configuration.

Please ref;

https://docs.microfocus.com/doc/Containerized_Operations_Bridge/24.3/NFSLogsIssue