Bug ID 693582: Monitor node log not rotated for certain monitor types

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1

Fixed In:
14.0.0, 13.1.3.2, 12.1.4

Opened: Nov 08, 2017

Severity: 3-Major

Symptoms

When Monitor Logging is enabled for an LTM node or pool member using certain monitor types, the monitor node log under /var/log/monitors/ is not rotated or compressed when log rotation occurs.

Impact

Depending on the affected BIG-IP software version in use, effects may include the following symptoms: 1. The active monitor node log is not rotated (not renamed from *.log to *.log.1). 2. The active monitor node log is rotated (renamed from *.log to *.log.1), but subsequent messages are logged to the rotated log file (*.log.1) instead of to the 'current' log file name (*.log). 3. The active monitor node log is not compressed (*.log.2.gz) when log rotation occurs.

Conditions

-- This occurs if Monitor Logging is enabled for an LTM node or pool member, and the LTM node or pool member uses any of the following monitor types: - icmp - gateway-icmp - external -- This also can happen with tcp-half-open if the monitor is down.

Workaround

To allow logging to the correct monitor node log file to occur, and for rotated monitor node log files to be compressed, disable Monitor Logging for the affected node or pool members. -- If symptom #1 occurs, Monitor Logging can be re-enabled after log rotation has occurred. -- To address symptoms #2 or #3, Monitor Logging can be re-enabled immediately. For more information on Monitor Logging, see: K12531: Troubleshooting health monitors :: https://support.f5.com/csp/article/K12531.

Fix Information

Monitor node logs are now rotated/compressed as expected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips