Last Modified: May 29, 2024
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4
Fixed In:
16.0.0, 15.1.0.5, 14.1.2.7
Opened: Jul 04, 2019 Severity: 2-Critical
The /var partition might become completely full on the disk due to files being written to /var/config/rest. This condition may be accompanied by console error messages similar to the following: 011d0004:3: Disk partition /var (slot #) has only 0% free on secondary blade. Additionally, there may be periodic restjavad and bigd daemons restarts related to disk space exhaustion.
The partition housing /var/config/rest may become 100% full, impacting future disk IO to the partition.
Process traffic while DoS Dashboard is open
Important: This workaround is temporary, and may need to be periodically performed either manually or from a script. Impact of Workaround: While these steps are performed, the BIG-IP REST API will be temporarily inaccessible, and higher disk IO may be seen. Run the following commands, in sequence: bigstart stop restjavad rm -rf /var/config/rest/storage*.zip rm -rf /var/config/rest/*.tmp bigstart start restjavad Manual application of these workaround steps clears the 100% utilized space condition and allows the partition to resume normal operation.
None