Title

VMware Postgres must be configured to overwrite older logs when necessary. (Cat II impact)

Discussion

Without proper configuration, log files for VMware Postgres can grow without bound, filling the partition and potentially affecting the availability of the vCenter Server Appliance (VCSA). One part of this configuration is to ensure the logging subsystem overwrites, rather than appends to, any previous logs that would share the same name. This is avoided in other configuration steps, but this best practice should be followed for good measure.

Check Content

At the command prompt, run the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -A -t -c "SHOW log_truncate_on_rotation;" Expected result: on If the output does not match the expected result, this is a finding.

Fix Text

At the command prompt, run the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_truncate_on_rotation TO 'on';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

Additional Identifiers

Rule ID: SV-256594r887568_rule

Vulnerability ID: V-256594

Group Title: SRG-APP-000109-DB-000321

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.