vRealize Automation 8.4.1 fails to collect a log bundle

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Symptoms:
When attempting to collect a log bundle from vRealize Automation 8.4.1, the collection fails with an error such as the following:

"Exception: subprocess completed with an unexpected exit code: [1}]. Expected: [0]. Stderr: [An exception interrupted the bundle generation: 'LogBundleConfig' object is not subscriptable."

Cause

This issue is caused by a file size filter added in the log collector in 8.4.1. By default, vRealize Automation has a 2GB file size limit. If a log bundle is requested and one of the directories the collector scans has a file larger than 2GB, the collection will fail.

Resolution

This issue is resolved in VMware vRealize Automation 8.4.2.

Workaround:
In the event upgrading is not possible, this issue can be worked around using one of two methods.

• Find the files that are larger than 2GB and move them out of the /services-logs and /var/log/vmware directories
  • Use these commands in an SSH session to find the files that are triggering the error. Once you have found them, move them to a directory outside of /sevices-logs/ and /var/log/vmware
    • find /services-logs/ -size +2G
    • find /metrics -size +2G
    • find /var/log/vmware/ -size +2G

• Increase the file size limit
  • SSH to all of your vRealize Automation appliances
  • Open the file /etc/vmware-prelude/logging.conf using a text editor such as VI
  • Modify the setting logging.bundle.contents.max-file-size to use the size you need
    • This setting normally appears as logging.bundle.contents.max-file-size=2g