Bug ID 500639: Setting log level for ZoneRunner has no effect.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 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.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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Jan 12, 2015
Severity: 3-Major
Related AskF5 Article:
K17211

Symptoms

Modifying the log level for ZoneRunner does not change the log level. This is a bug in the handling of the log level change message within ZoneRunner

Impact

BIND queries go unanswered until the zone is loaded into BIND.

Conditions

If a GTM config sync is also occurring, the GTM can get into a state where all queries go unanswered until the GTM config loads and/or the BIND zones load.

Workaround

Assuming that the desired log level is "DEBUG", the following steps will force zonerunner to log debug messages to /var/tmp/zrd.out On the BIG-IP system: touch /service/zrd/debug bigstart restart zrd

Fix Information

Modifying the log level for ZoneRunner now changes the log level as expected.

Behavior Change