Bug ID 704546: Symlinks may be corrupted by upgrade

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Opened: Jan 31, 2018

Severity: 3-Major


In rare cases after a software version upgrade, a corrupted symbolic link that points to a nonexistent file may exist. Processes that try to use the file will fail, often generating the message 'No such file or directory'.


A symlink is broken, but it depends on whether the symlink is necessary to BIG-IP operation as to whether a problem will be immediately apparent.


Happens after an upgrade. This rarely encountered issue occurs when the symlink points to an absolute path (/a/b/c/d) rather than a relative one (if you are in /a/b, then the target would be c/d).


If creating a symlink is necessary, use a relative path rather than an absolute one. If this condition is found, use the following command to rebuild the symlink: ln -fs <target> <symlink_name>

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips