Last Modified: Oct 16, 2019
See more info
Known Affected Versions:
13.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.1, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.3, 126.96.36.199, 14.0.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.0.1, 14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.2, 126.96.36.199, 15.0.0, 15.0.1
Opened: Jul 04, 2019
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.