Bug ID 914645: Unable to apply LTM policies to virtual servers after running 'mount -a'

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Opened: Jun 05, 2020

Severity: 3-Major

Symptoms

After attempting to assign an LTM policy to a virtual server, you may get an error in the GUI: 010716d8:3: Compilation of ltm policies for virtual server /Common/VS failed; Couldn't publish shared memory segment. You may also see this logged in /var/log/ltm: err mcpd[6905]: 010716d5:3: Failed to publish LOIPC object for (loipc_VS.1589526000.777142413). Call to (shm_open) failed with errno (13) errstr (Permission denied).

Impact

Having /dev/shm mounted twice affects every process on the BIG-IP system that use that directory for shared memory. The duplicated mount can result an inability to apply LTM policies, but the impact is not limited to that issue.

Conditions

-- Run the command: mount -a -- Attempt to assign an LTM policy to a virtual server.

Workaround

Run the following command to enable assigning an LTM policy to a virtual server: umount -l /dev/shm Unmounting might not resolve every issue that is result of /dev/shm being mounted more then once. So it's best if mount -a is not run at all.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips