Bug ID 542218: Logging Services may not work

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: Aug 27, 2015
Severity: 3-Major

Symptoms

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

Impact

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

Conditions

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.

Workaround

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