Last Modified: Mar 05, 2020
See more info
Known Affected Versions:
14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.0.1, 220.127.116.11, 14.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.1.2, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Mar 19, 2019
After an upgrade to v14.1.0 or higher, swap memory may not be mounted. TMM or other host processes may restart due to lack of memory.
May lead to low or out of memory condition. The Linux oom killer may terminate processes possibly affecting service. Typically management activities may be impacted eg sluggish GUI (config utility) or tmsh sessions.
System is upgraded to v14.1.0 or above System has RAID storage.
Mount the swap volume with correct ID representing the swap device. Perform the following steps on the system after booting into the affected software version: 1. Get the correct ID (RAID device number (/dev/md<number>)): blkid | grep swap Note: If there is no RAID device number, perform the procedure detailed in the following section. 2. Check the device or UUID representing swap in /etc/fstab. 3. If swap is not represented with the correct ID, modify the /etc/fstab swap entry to point to the correct device. 4. Enable the swap: swapon -a 5. Check swap volume size: swapon -s If the blkid command shows there is no UUID associated with the swap RAID device, use the following procedure: 1. Generate a random UUID: uuidgen 2. Make sure swap is turned off: swapoff -a 3. Recreate the swap partition with UUID generated in step 1: mkswap -U <uuid_from_step_1> <raid_device_from_step_1> 4. Run blkid again to make sure that you now have a UUID associated with the raid device: blkid | grep swap 5. edit fstab and find the line <old_value> swap swap defaults 0 0 6. Replace the old value, whether it was an incorrect UUID or a device name, with the UUID generated in step 1. For example: UUID=8b35b30b-1076-42bb-8d3f-02acd494f2c8 swap swap defaults 0 0