Bug ID 542218: Logging Services may not work

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Aug 27, 2015

Severity: 3-Major


Sometimes some logging services, particularly to local databases, may not be operational.


Logging, particularly to local databases, will not be available.


There is a rare conflict between the process id of the last instance of a logging service and any new process that can rarely prevent logging services from starting.


If local database logging does not work, the only workaround is to try to restart the unit. If possible, deleting /var/run/fslog.pid and /var/run/logmysqld.pid will solve the problem for the next restart.

Fix Information

A rare condition preventing logging services from starting has been fixed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips