Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP CGN, LTM
Known Affected Versions:
11.3.0, 11.4.0, 11.5.0, 11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 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, 11.5.10
Fixed In:
11.6.0
Opened: May 20, 2014 Severity: 2-Critical
A log publisher configured with multiple destinations fails to publish logs if any of the destinations fail.
Logging destination failures is by design, even if multiple destinations are configured. But it can be confusing when logging stops and unexpected errors are reported.
This can occur if multiple destinations are configured and a destination fails.
Although this feature is working as designed. However, the built-out infrastructure might be based on an expectation of different behavior.
This release adds a db variable (logpublisher.atomic) that defaults to 'true', where logging stops whenever any configured log publisher destination is not ready. When set to 'false', publishers continue to accept and deliver logs as long as at least one of their remote destinations is working.
This release adds a db variable (logpublisher.atomic) that defaults to 'true'. When set to 'false', publishers continue to accept and deliver logs as long as at least one of their remote log publisher destinations is working.