Bug ID 506110: Log flood within datasyncd.log in clustered environment

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM, FPS(all modules)

Known Affected Versions:
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 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5

Opened: Feb 11, 2015

Severity: 3-Major

Related Article: K25430927

Symptoms

Log flooding occurs within datasyncd.log every few seconds: rsync: failed to connect to 127.3.0.3: No route to host (113).

Impact

No impact to traffic. Messages are added to datasyncd.log every few seconds.

Conditions

Within clustered environment, and one or more of the blades are either down, powered off, disabled, or not populated. This may happen in a blade that is powered on, or when the cluster is added to a trust-domain. The logged messages continue for a duration from a few minutes to a few hours.

Workaround

None.

Fix Information

datasyncd.log no longer causes a log flood in clustered environments where one or more of the blades are either down, powered off, disabled, or not populated.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips