Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP MA-VE
Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Mar 21, 2016 Severity: 3-Major Related Article:
K55138704
Virtual Edition (VE) OVA logrotate max-file-size is too big for the /var/log partition size.
The BIG-IP VE system runs out of disk space due to increased logging. In this instance, logrotate should run and potentially free up space by rotating and compressing the actively written logs. With the current setting for max-file-size, however, that cannot happen, thus leading to increased likelihood of running out of space in /var/log.
This occurs on 11.5.0 and later, where the partition size was reduced from 6 GB to 500 MB, to better manage disk space. This can also happen on Micro instance on a fixed version
You can extend the disk space for logs by performing the following procedure. (From K14952: Extending disk space on BIG-IP Virtual Edition, available here: https://support.f5.com/csp/article/K14952#proc3.) Impact of procedure: You need to shut down the BIG-IP VE system during the disk provisioning steps, and the system will not be available for traffic processing. You should perform this procedure during a suitable maintenance window. Increasing the disk size on the VE system is irreversible, since F5 does not support disk shrinking. 1. Log in to the command line on the BIG-IP VE system. 2. Shut down the system by typing the following command: shutdown -h now 3. Provision the desired disk space for the VE system on the hypervisor. For information about disk provisioning on the hypervisor, refer to the documentation from your hypervisor vendor. 4. Start up the BIG-IP VE guest instance on your hypervisor. For information about starting a guest instance on the hypervisor, refer to the documentation from your hypervisor vendor. 5. When the BIG-IP VE system is up, log in to the command line on the VE system. 6. Extend the /var/log directory by using the following command syntax: tmsh modify /sys disk directory /var/log new-size <desired value in KB>. --For example you would type the following command to extend the /var/log directory to 10 GB: tmsh modify /sys disk directory /var/log new-size 10485760. 7. Save the configuration by typing the following command: tmsh save /sys config. 8. Reboot the VE system by typing the following command: reboot. 9. When the BIG-IP VE system is up, log in to the command line on the VE system. 10. Verify that the /var/log directory is successfully extended to the size you have specified in step 6 by typing the following command: tmsh show /sys disk directory.
In this release, there is an increased default /var/log partition size to prevent the issue that occurred because the log-rotate max-file-size was too big in VE. New /var/log/sizes are: 900MB - for Good 3GB - for Better/Best Micro - 500MB as before.