Last Modified: Sep 13, 2023
Known Affected Versions:
14.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.1.2, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.0.0, 15.0.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 15.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.1.1
16.1.0, 126.96.36.199, 15.1.2, 188.8.131.52, 184.108.40.206
Opened: Sep 20, 2019 Severity: 2-Critical
The /var partition might become completely full on the disk due to tmp 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 daemon 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. This issue is happening because a VIPRION process is not available because of a REST timeout.
Manually run the following commands, in sequence: bigstart stop restjavad rm -rf /var/config/rest/*.tmp bigstart start restjavad
Increased the rest socket timeout value and shellexecutor timeout value to 6 min to fix the timeout issue of viprion worker ?The fix also includes automatic removal of unused tmp files.