Bug ID 463481: Log publishers fail to log if any publishing destination is not ready

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP CGN, LTM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 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

Symptoms

A log publisher configured with multiple destinations fails to publish logs if any of the destinations fail.

Impact

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.

Conditions

This can occur if multiple destinations are configured and a destination fails.

Workaround

Although this feature is working as designed. However, the built-out infrastructure might be based on an expectation of different behavior.

Fix Information

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.

Behavior Change

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.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips